Přejít na obsah

Accessibility

Making sites and apps accessible by all.

Accessibility Experience & Sentiment

The accessibility features mentioned in this year's survey proved to be straightforward enough to use, which translated into a very low negative sentiment overall.

Group by:

Sort by:

1

96.3%
3,952
2

87.3%
8.7%
3,955
3

24.8%
31.5%
43.3%
3,947
4

8.1%
20.5%
66.8%
3,940

Experience

  • Used it: Respondents who have used an item.
  • Heard of it: Respondents who have heard about an item, but haven't used it.
  • Never heard of it: Respondents who have never heard about an item.

Sentiment

  • Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
  • Neutral: Responents who did not indicate any sentiment about a technology.
  • Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.

User Disabilities

It was comforting to see developers account for a wide range of disabilities while making websites, with visual disabilities taking the top ranks.

0%
15%
29%
44%
58%
73%
1

Low vision

2,659
2

Atypical color vision

2,014
3

Mobility impairments

1,244
4

Vestibular disorders

882
5

Hearing impairments

758
6

Learning disabilities

569
7

Other cognitive impairments

497
8

🚫 None

693
9

Other Answers

50
0%
15%
29%
44%
58%
73%
% of question respondents
What kind of user disabilities do you account for when making websites?

Other Accessibility Techniques

It's nice to see that alt text is widely implemented, and if nothing else this chart can serve as a handy shortlist of accessibility patterns to implement in your own projects.

0%
18%
36%
53%
71%
89%
1

Descriptive alt text

3,371
2

Information Hierarchy

3,165
3

Form Control Labels

3,116
4

Intuitive keyboard navigation

2,717
5

Meaningful Link Text

2,687
6

Sufficient Contrast

2,524
7

Visible Focus Ring

2,447
8

Not Relying on Color Only

2,097
9

Not Relying on Pointer Only

2,009
10

<fieldset> and <legend>

1,999
0%
18%
36%
53%
71%
89%
% of question respondents
What other techniques are part of your regular accessibility strategy?

Screen Readers

It should come as no surprise that developers are more likely to use screenreaders if they come bundled with their browser or OS.

0%
8%
15%
23%
31%
39%
1

Chrome DevTools

1,240
1,094
568
319
300
108
10

Firefox Accessibility Inspector

11

🚫 None

1,362
12

Other Answers

34
0%
8%
15%
23%
31%
39%
% of question respondents
Which screen readers do you use for accessibility testing?

Accessibility Tools

Lighthouse and browser devtools in general topped the rankings, overtaking more specialized tools such as Axe or WAVE.

0%
10%
21%
31%
42%
52%
1,798
2

browser_devtools

915
887
4

Firefox Accessibility Inspector

830
5

574
496
163
159
0%
10%
21%
31%
42%
52%
% of question respondents
What tools do you use for accessibility testing?

Accessibility Pain Points

Accessibility presents a unique challenge in that developers must not only overcome technical issues such as testing difficulties, but also organizational obstacles such as low prioritization or lack of client demand.

0%
11%
21%
32%
43%
54%
1

Technical issues

Answers matching “Technical issues” 148
2

Company issues

Answers matching “Company issues” 108
3

Screen reader issues

Answers matching “Screen reader issues” 62
4

Implementation issues

Answers matching “Implementation issues” 55
5

Lack of knowledge

6

Lack of best practices

7

Browser support

8

Lack of tools

Answers matching “Lack of tools” 31
9

Lack of documentation

10

WCAG issues

Answers matching “WCAG issues” 16
11

too_time_consuming

12

Discoverability

13

Other Answers

Answers matching “Other Answers” 353
0%
11%
21%
32%
43%
54%
% of question respondents
What are your biggest pain points around web accessibility?
Freeform

Recommended Resources

Web App Accessibility (feat. React)
Marcy Sutton Todd
Principle Studios

Web App Accessibility (feat. React)

Solve the most common accessibility issues in React apps using testing tools, semantic HTML, and ARIA attributes to make interactive elements accessible.
Thanks to our partners for supporting us! Learn more.