A Tangled Web of ARIA
summary
Claim: ARIA is widely misused as a replacement for HTML rather than a supplement, producing div soup and brittle components; a simple product card example swells from ~72 lines to tangled ARIA markup and then shrinks to ~30 lines with native H4/OL/LI and a real button. Recommended fixes are concrete: ARIA-first development is wrong, enforce accessible coding standards, require accessible code reviews, and add automated checks (Axe DevTools, WAVE, linters, a11ysupport.io, Playwright/Cypress examples) to catch regressions.
AI-written summary · about
chapters (5)
- 0:00Accessibility and ARIA misuse
- 6:30ARIA-first development problems
- 11:45ARIA misuse example
- 28:48Building accessibility culture
- 37:03Key takeaways and Q&A
related talks
31mAn aria of ARIA
18mWarm-Up Talk: ARIA Serious?
49mARIA A Grande Method Of Accessible Markup
34mIntroduction to ARIA: A Developer's Guide
25mARIA: A Grande Method Of Accessible Markup with Chris DeMars
38mHow To Make Your Website More Accessible with WAI-ARIA
50mARIA: the good parts
31mARIA Was Made For This Accessiblility of JavaScript MVCs