Building Accessibility Testing into Your Workflow
summary
Argues for shifting accessibility left by embedding automated checks that catch issues before commit, noting automated tools only find about 25% of real problems. Recommends specific tools and integrations: axe, eslint-plugin-jsx-a11y, jest-axe, plus Lighthouse, WAVE and pa11y for CI; demonstrates a React starter repo, a manual-testing VM image, and an intentionally inaccessible demo site. Shows a custom lint rule (tabindex=-1 for skip links), console warnings during dev, and failing CI/pre-commit hooks to block bad commits.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:55What is accessibility
- 2:59How accessibility gets broken
- 4:38How to solve accessibility issues
- 5:41Automated accessibility testing
- 6:41AppScore
- 7:08Workflow
- 10:10Advancement Team
- 11:25User Package
- 13:20Unit Tests
- 14:10Storybook Addon
- 16:05Manual Testing
- 19:45Accessibility Components
- 20:42QA Tools
- 21:19Final Recommendations
- 23:56Resources
- 25:06Questions
related talks
56mAccessibility Testing 101
53mAutomating Accessibility Assurance
25mHow to do good without doing anything
30mTesting Web Accessibility
33mAutomated Accessibility Testing
44mTesting Web Accessibility
43mLucky Nkosi: A11y Beyond the Theory: Integrating Accessibility Testing into Your Workflow
45mTips from the Trenches: Accessibility Testing