ARIA: the good parts
summary
Explains that ARIA is an ontology for accessibility metadata and that a few attributes reliably help users: landmarks for page regions, aria-expanded and aria-pressed for toggle state, and aria-label/aria-labelledby/aria-describedby for names and error text; browsers expose this via the accessibility tree in Chrome DevTools and screen readers consume it. Warns about pitfalls: DOM/UI state mismatches, disappearing focus after closing popovers, overuse of role=application, and untranslated labels (6% of users relied on Google Translate in one government test). Tools: W3C HTML validator, NVDA, high-contrast mode.
AI-written summary · about
chapters (12)
- 0:00ARIA and accessibility intro
- 3:36What ARIA is and why
- 6:01ARIA user impact
- 10:14ARIA ontology
- 14:47Why not all ARIA parts are good
- 15:09Safe ARIA properties
- 29:39Complex ARIA widgets
- 32:46ARIA pitfalls
- 38:40Overused ARIA roles
- 42:07ARIA controls and owns
- 43:31ARIA key takeaways
- 44:36Q&A on ARIA labels
related talks
25mARIA: A Grande Method Of Accessible Markup with Chris DeMars
49mARIA A Grande Method Of Accessible Markup
34mIntroduction to ARIA: A Developer's Guide
38mHow To Make Your Website More Accessible with WAI-ARIA
31mAn aria of ARIA
18mWarm-Up Talk: ARIA Serious?
33mAccessibility Done Right
31mARIA Was Made For This Accessiblility of JavaScript MVCs