The intentions were good
summary
Walks through concrete failed attempts at accessibility, naming lessons and tools: keyboard navigation first, use of screen readers and Lighthouse and Axe, and pitfalls of ARIA labels misuse and redundant alt text. Claims five practical lessons: prioritize contrast semantics outlines skip links, test user stories manually with keyboard and a screen reader, add automated checks to CI. Cites surprising numbers (4.1% of sites pass automated checks; an “info” site scores 98/100 yet is unusable), shows what was built, why it broke, and what fixes actually work.
AI-written summary · about
chapters (11)
- 0:00Accessibility introduction
- 2:29Disabilities and assistive tech
- 7:48The most important assisted technology for developers
- 9:13Simple fixes with big impact
- 12:44Prioritizing fixes in codebases
- 14:29Lesson two: People mean well but sometimes fail
- 17:21Alt text rules and mistakes
- 19:50Testing beyond automated tools
- 24:05Common issues and easy fixes
- 25:12Accessibility ownership
- 27:41Learning from mistakes
related talks
41mTales of Accessibility Failures
56mAccessibility Testing 101
31mDecoding web accessibility through testing
01h 05mAccessibility Testing 101
35mBuilding an accessibility testing habit
31mHow to Program with Accessibility in Mind
01h 01mA web for anyone, anywhere, anytime
01h 07mA web for anyone, anywhere, anytime