Get It Right the 1st Time: Stop 80%+ of A11Y Bugs During Development
summary
Claim: shift accessibility left to stop the bulk of bugs during dev by combining axe-core automation, an Axe DevTools extension, a VS Code/IntelliJ linter and GitHub Action checks. Demo shows a single page averages ~30 issues, manual recording costs ~5 minutes per issue (2–3+ hours per page) and documenting one bug takes 2m45s to document. Automation finds 57% by automation and guided tests add ~23% for 80.39% total coverage; linters and CI blocks prevent bad code from reaching QA.
AI-written summary · about
chapters (8)
- 0:00The importance of shift left
- 1:32The true cost of reactive QA
- 6:36Manual assessment challenges
- 14:23Automating with axe dev tools
- 20:06Linting and CI/CD integration
- 25:46Intelligent guided testing
- 32:56Efficiency and ROI data
- 37:36Q&A session
related talks
11mA11y Broke My Build
30mTesting Web Accessibility
43mHow to Use AI to Build Accessible Products
29mBuilding Accessibility Testing into Your Workflow
28mEnterprise Grade Accessibility for Everyone
44mTesting Web Accessibility
56mAccessibility Testing 101
45mAccessibility feedback loop: Continuous a11y improvement in your development life cycle