Accessibility audit and what's after it
summary
Explains how audits map to measurable outcomes: the WCAG 3.0 draft (dated June 8) moves to scored methodologies with thresholds where 80% becomes the common legal safety mark, >90 and 98+ denote higher effort, and any critical error blocks core functionality and invites litigation. Recommends shifting from principle checklists to component patterns and design-system docs so most behaviors can be automated and unit-tested, notes automated scanners only find a minority (one study shows 37% detection of 157 injected errors), and describes automating the remaining checks with targeted tests.
AI-written summary · about
chapters (11)
- 0:00Introduction to accessibility
- 2:29Why accessibility matters
- 3:55What is an accessibility audit
- 5:21Accessibility metrics and standards
- 8:07WCAG principles evaluation
- 10:12Pattern-based evaluation
- 13:23Automated testing
- 15:34Automated test limitations
- 17:23Manual testing tools
- 18:08Summary and next steps
- 18:51Q&A
related talks
26mThe Ultimate Practical Guide to Accessibility Testing
01h 35mAccessibility audit: why, how, what to do next?
26mAuditing design systems for accessibility
25mBeyond Compliance: Testing for a more Accessible Web
01h 05mAccessibility Testing 101
45mAccessibility: Why You Should Learn About WCAG
38mHow to set up an accessibility program in an imperfect world
50mShift Left on Accessibility: Beyond the Audit