Shift Left on Accessibility: Beyond the Audit
summary
European law now requires accessible new releases and forces legacy fixes by 2030, so accessibility becomes continuous rather than a one‑off audit. Practical steps include adding an accessibility checklist to the definition of done, running axe + Playwright or Lighthouse and WAVE in CI, using Polypane and screen‑reader/manual keyboard checks, and involving users. Expect surprising stats: 67% start in design, automated scans catch roughly 20–60% of issues, fixes cost 3 hours in dev versus a week from production, and some jurisdictions levy up to 200000 in fines.
AI-written summary · about
chapters (17)
- 0:00Accessibility introduction
- 1:15Beyond disabilities
- 7:34Speaker Ramona
- 8:16Fixing late accessibility
- 9:42European Accessibility Act
- 14:18Why prioritize accessibility
- 16:26Cost of fixing accessibility
- 19:53Designing accessible
- 21:20Accessibility in development
- 24:11Accessibility testing types
- 27:05Automated testing tools
- 29:37Manual testing tools
- 33:57Screen readers best practices
- 36:00Manual accessibility checks
- 38:36GitHub Actions accessibility
- 42:12Sustainable accessibility
- 43:17Q&A
related talks
48mFind and Fix Your Accessibility Problems
29mHow to bring accessibility into your teams
14mAccessible Accessibility
45mTips from the Trenches: Accessibility Testing
41mArchitecting for Accessibility
38mAccessibility 101-102: What every tester should know about digital accessibility
33mAccessibility needs to be the future of better technology
38mHow to set up an accessibility program in an imperfect world