Making a Strong Case for Accessibility
summary
Web accessibility is failing at scale: the WebAIM Million finds 51+ million errors across a million home pages, and common fixes are ignored. Start projects with semantic HTML, color contrast that meets WCAG (not the 2.57:1 examples, aim for 4.5:1 AA), add one accessibility liaison per team, and run 40% automated 60% manual audits. Use real-user testing with firms like Applause or Fable, avoid accessibility overlays (they don’t work), and validate with tools like axe, WAVE, Lighthouse.
AI-written summary · about
chapters (18)
- 0:00Introduction and thanks
- 1:28Why accessibility matters
- 3:33Accessibility challenges today
- 5:39Color contrast and visual disabilities
- 8:53Keyboard navigation and assistive tech
- 10:23Situational disabilities
- 14:20Common pushback on accessibility
- 16:53Countering stakeholder objections
- 19:53Gaining stakeholder buy-in
- 21:15Practical steps to advocate
- 24:05Assessing accessibility maturity
- 27:16Implementing accessibility practices
- 30:02Legal standards and compliance
- 31:13Testing with assistive tech
- 33:24Long-term accessibility strategy
- 36:13Accessibility as a right
- 39:47Avoiding accessibility overlays
- 43:41Q&A and tools discussion
related talks
37mMaking A Strong Case For Accessibility
50mAccessibility by Everyone (and for Everyone)
24mWeb Accessibility Strategies for Non-Accessible Projects
41mAccessibility is a Requirement
33mWeb accessibility in practice, more than just WCAG
54mAccessibility by everyone (and for everyone)
40mAccessibility, what, why and how?
26mHow (Not) to Fail at Accessibility