Tales of Accessibility Failures
summary
15% of people have permanent disabilities and many more benefit situationally, so start with high‑impact, low‑code fixes: keyboard navigation and visible focus outlines, and add a one‑line HTML skip links with seven lines of CSS (no JS) to skip repetitive tabs. Watch out for aria-label misuse — replacing link text broke a live news nav for screen readers. Run automated checks (Lighthouse, axe, WAVE, Storybook addon) but always do keyboard and screen‑reader manual user‑story tests.
AI-written summary · about
chapters (7)
- 0:00Introduction and accessibility myths
- 1:02Accessibility personas and disabilities
- 8:26Simple accessibility fixes with big impact
- 14:10Good intentions gone wrong
- 19:55Manual testing beyond Lighthouse
- 23:29Team effort and accessibility ownership
- 27:17Q&A on accessibility priorities and tools
related talks
20mImpactful Accessibility: The Changes that Mean the Most
31mHow to Program with Accessibility in Mind
26mMake the internet a better place - with coding for accessibility
25mHello Accessibility, my old friend
45mTips from the Trenches: Accessibility Testing
41mAccessibility is a Requirement
48mCoding For Accessibility Best Practices from the Front Lines
36mThe Human Side of Accessibility