Gå til innhold

State of HTML 2025

Accessibility

Making sites and apps accessible by all.

We're highlighting up-and-coming features or libraries we think you should know about.

Feature Highlight: <search>

The <search> element is one of those easy wins that take very little effort to add to your list of best practices. Step 1: use it to denote any search field in your apps. Step 2: well that's it really!

And now that it's supported in all four major browsers, there's really no reason not to be using it.

Baseline: Newly Available

Learn more

Useful Resources

Tilgjengelighet Erfaring & Følelser

Landmark elements (<main>, <nav>, etc.) aren't very new or exciting but they remain a foundation of web accessibility.

Gruppér etter:

Sorter etter:

1
Accessibility
96.7%
4,383
2
Accessibility
88.2%
8%
4,381
3
Accessibility
29.3%
29.1%
41.2%
4,377
4
Accessibility
13%
22.5%
64.3%
4,378

Erfaring

  • Brukt det: Respondents who have used an item.
  • Hørt om det: Respondents who have heard about an item, but haven't used it.
  • Aldri hørt om det: Respondents who have never heard about an item.

Oppfatning

  • Positiv: Respondenter som er interessert i å lære mer om en teknologi; eller er villige til å bruke den igjen.
  • Nøytral: Respondenter som hadde en nøytral oppfatning av en teknologi.
  • Negativ: Respondenter som ikke er interessert i å lære mer om en teknologi; eller har brukt den og hatt en negativ opplevelse.
“Used” average:57%
“Positive” average:37%
“Negative” average:2%

Other Accessibility Techniques

While things like alt text or proper heading hierarchy have become second nature to most front-end developers, newer tools like the prefers- set of media queries have yet to truly become mainstream.

What other techniques are part of your regular accessibility strategy?
Multiple
0%
20%
40%
60%
80%
100%
1
Descriptive alt text
3,647
2
Information Hierarchy
3,452
3
Form Control Labels
3,331
4
Meaningful Link Text
+1
2,827
5
Sufficient Contrast
+1
2,778
6
Visible Focus Ring
+1
2,725
7
Intuitive keyboard navigation
-3
2,454
8
<fieldset> and <legend>
+2
2,250
9
Not Relying on Pointer Only
2,194
10
Not Relying on Color Only
-2
2,192
0%
20%
40%
60%
80%
100%
% besvarelser på spørsmål
4,124
66%
10

User Disabilities

It's nice to see that beyond accounting for users with vision impairments, more developers are also taking atypical color vision and mobility impairments into account compared to last year.

What kind of user disabilities do you account for when making websites?
Multiple
0%
20%
40%
60%
80%
100%
1
Low vision
2,724
2
Atypical color vision
2,163
3
Mobility impairments
1,387
4
Vestibular disorders
920
5
Hearing impairments
687
6
Learning disabilities
677
7
🚫 Ingen
665
8
Other cognitive impairments
600
9
Andre svar
52
0%
20%
40%
60%
80%
100%
% besvarelser på spørsmål
3,727
60%
10

Screen Readers

Once again, easily accessible tools like VoiceOver or the Chrome DevTools win over more specialized options. Although many developers still don't use screen readers of any kind (also note that 39% of survey respondents skipped the question altogether).

Which screen readers do you use for accessibility testing?
Multiple
0%
20%
40%
60%
80%
100%
1
VoiceOver
+1
1,376
2
🚫 Ingen
1,358
3
Chrome DevTools
-1
1,306
4
NVDA
742
5
JAWS
414
6
WAVE
366
7
TalkBack
216
8
Narrator
199
9
Orca
137
10
Chromevox
88
11
Firefox Accessibility Inspector
12
Andre svar
51
0%
20%
40%
60%
80%
100%
% besvarelser på spørsmål
3,784
61%
10

Accessibility Tools

Browser devtools have seen a huge jump in usage compared to last year's results, seeing them overtake Lighthouse to become the lead accessibility testing tool.

What tools do you use for accessibility testing?
Multiple
0%
20%
40%
60%
80%
100%
1
Browser Devtools
+1
2,259
2
Lighthouse
-1
1,983
3
Axe
1,145
4
Firefox Accessibility Inspector
1,033
5
🚫 Ingen
-1
717
6
WAVE
+1
648
7
-1
544
8
Accessibility Insights
523
9
Pa11y
+1
188
10
Arc
-1
167
0%
20%
40%
60%
80%
100%
% besvarelser på spørsmål
3,860
62%
10

Accessibility Pain Points

While there are technical gaps when it comes to accessibility (e.g. cross-root ARIA), a recurring theme whenever we ask about it is that the main pain points are around the humans involved with issues around workplace priorities, education, and cognitive overhead topping the list.

What are your biggest pain points around web accessibility?
Multiple
Top pain point topics overall.

View:

Items that are not one of “limitations”
0%
20%
40%
60%
80%
100%
1
Education
3
2
workplace
1
3
Cognitive overload
2
4
Debugging
1
5
Environments & Consumers
6
Screen reader issues
2
7
ARIA
1
8
Browser support
1
9
Low priority
-7
10
Tooling
2
11
Excessive complexity
-2
12
Keyboard navigation
13
Standards & Specs
1
14
Focus management
-3
15
16
Missing elements
17
Ecosystem issues
18
Content
1
19
Accessible visual design
20
Reliance on JavaScript
21
Access to screen readers
+3
22
Component-Based Architecture
23
Invalid/Spam
24
CSS Integration
25
26
Andre svar
0%
20%
40%
60%
80%
100%
% besvarelser på spørsmål
606
10%
25
5

Anbefalte ressurser

Website Accessibility, v3
Jon Kuperman
Bloomberg

Website Accessibility, v3

Build content for everyone and become your company's accessibility expert! Learn the importance of semantic HTML and alt text for ensuring screen readers can navigate your site.
Takk til våre partnere for deres bidrag! Lær mer.