Warm-Up Talk: ARIA Serious?
summary
Claim: ARIA fixes gaps but breaks more sites when misused, and there are five practical rules to follow. Concrete failures include role=button on headings, aria-hidden on body that hides dialogs, sliders built from links instead of buttons, sortable table headers turned into nonheaders, and tabindex misuse. Recommended tools are the WAI-ARIA Authoring Practices and using native HTML5 elements and states (aria-pressed, aria-selected) plus keyboard patterns. Real-world surprise: common frameworks and patterns often ship broken unless ARIA rules and keyboard behavior are implemented exactly.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:14Rules for Aria
- 3:50Third Rule Is all Interactive Aria Controls Must Be Usable with the Keyboard
- 6:45Aria Examples
- 7:40Slide Navigation
- 10:52Body with Aria Hidden True
- 11:30Aria Authoring Practices Guide from W3c
- 11:58Using Aria in Html5
- 12:24Use Aria Landmarks
- 17:36Using Html Instead of Aria
related talks
38mHow To Make Your Website More Accessible with WAI-ARIA
34mIntroduction to ARIA: A Developer's Guide
49mARIA A Grande Method Of Accessible Markup
31mAn aria of ARIA
58mA Tangled Web of ARIA
25mARIA: A Grande Method Of Accessible Markup with Chris DeMars
50mARIA: the good parts
26mLet’s Keep Our Promises: ARIA, Styles and Keyboard Navigation