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.
链接到某一部分无障碍功能
Landmark elements (<main>, <nav>, etc.) aren't very new or exciting but they remain a foundation of web accessibility.
通过...分组：
根据此项排序:
经验
- <span aria-hidden="true">🤓</span> 用过: 使用过此项目的受访者。
- <span aria-hidden="true">👀</span> 有听说过: 听说过此项目，但没有使用过此项目的受访者。
- <span aria-hidden="true">🤷</span> 没听说过: 从未听说过此项目的受访者。
情绪（态度）
- 积极: 有兴趣了解此技术，或者愿意再次使用它的受访者
- 中立: 未对此技术发表看法的受访者
- 消极: 对此技术不感兴趣，或者使用此技术有糟糕体验的受访者
链接到某一部分其他无障碍技术
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.
链接到某一部分用户残疾情况
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.
链接到某一部分屏幕阅读器
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).
链接到某一部分无障碍工具
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.
链接到某一部分无障碍痛点
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.
链接到某一部分资源推荐
