メインコンテンツにスキップ

アクセシビリティ

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,951
2

87.3%
8.7%
3,954
3

24.8%
31.5%
43.3%
3,946
4

12.2%
20.5%
66.8%
3,939

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.

ユーザーの障害

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

Webサイト制作時に、どのようなユーザーの障害を考慮していますか?
Multiple
0%
20%
40%
60%
80%
100%
1

弱視

2,659
2

非定型色覚

2,014
3

運動障害

1,244
4

前庭障害

882
5

聴覚障害

758
6

学習障害

569
7

その他の認知障害

497
8

🚫 該当なし

692
9

Other Answers

50
0%
20%
40%
60%
80%
100%
回答数に占める割合(%)

その他のアクセシビリティテクニック

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.

通常のアクセシビリティ戦略に含まれるその他のテクニックは何ですか?
Multiple
0%
20%
40%
60%
80%
100%
1

説明的なaltテキスト

3,370
2

情報階層

3,164
3

フォームコントロールラベル

3,115
4

直感的なキーボードナビゲーション

+2
2,716
5

意味のあるリンクテキスト

-1
2,686
6

十分なコントラスト

-1
2,524
7

視覚的なフォーカスリング

2,447
8

色のみに依存しない

2,096
9

ポインターのみに依存しない

2,009
10

<fieldset> and <legend>

1,999
0%
20%
40%
60%
80%
100%
回答数に占める割合(%)

スクリーンリーダー

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

アクセシビリティテストにどのスクリーンリーダーを使用していますか?
Multiple
0%
20%
40%
60%
80%
100%
1

Chrome DevTools

+6
1,240
-1
1,094
-1
568
-1
319
+4
300
-2
153
-2
147
-2
108
-1
101
10

Firefox Accessibility Inspector

11

🚫 該当なし

-1
1,361
12

Other Answers

-1
34
0%
20%
40%
60%
80%
100%
回答数に占める割合(%)

アクセシビリティツール

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

アクセシビリティテストにどのようなツールを使用していますか?
Multiple
0%
20%
40%
60%
80%
100%
1,798
2

Browser Devtools

915
-1
887
4

Firefox Accessibility Inspector

+3
830
5

+8
574
-3
496
+6
163
+3
159
0%
20%
40%
60%
80%
100%
回答数に占める割合(%)

アクセシビリティの問題点

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.

Webアクセシビリティに関する最大の問題点は何ですか?
Freeform
Multiple
0%
20%
40%
60%
80%
100%
1

Testing

2

Low priority

3

+1
4

Lack of knowledge

+1
5

Lack of best practices

-2
6

Browser support

+1
7

Lack of documentation

-1
8

Excessive complexity

+7
9

Screen readers inconsistencies

+2
10

Company issues

0%
20%
40%
60%
80%
100%
回答数に占める割合(%)

おすすめのリソース

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.
パートナーのサポートに感謝しています! 詳細をみる。