How (and why) to 'shift-left' your accessibility testing
summary
Argues that moving accessibility earlier cuts cost and risk using concrete moves: add disabilities to personas, recruit users with lived experience, require accessibility definition of done on tickets, and run integrated WAVE into CI/CD so regressions fail fast. Gives numbers: the rule of ten cost multipliers (1→10→100→1,000→10,000), ~22% population with disabilities, ~6.5% colorblind in IT. Shares tooling and code: Crest open source harness tied to WAVE, accessible component libraries, and proven reduction of late-stage fixes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:47Accessibility QA as regulation
- 4:25Shift-left myth debunked
- 5:41Shift-left cost savings
- 7:18Rule of ten in costs
- 9:13From audits to investments
- 10:28Accessibility myths debunked
- 13:05Requirements accessibility
- 17:26Feasibility with disability
- 21:23Design accessibility
- 23:51Design systems
- 26:56CI/CD accessibility
- 29:39Testing strategies
- 33:19Deployment checks
- 36:03Q&A
related talks
28mBuilding in accessibility for broader value to all
29mHow to bring accessibility into your teams
45mTips from the Trenches: Accessibility Testing
45mAccessibility at all stages
12mAccessibility-First Development: Making Applications Inclusive from Day One
56mAccessibility Testing 101
19mAccessibility isn't hard; getting people to see it's easy can be with Sarrah Vesselov
50mShift Left on Accessibility: Beyond the Audit