Testing Web Accessibility
summary
Claims that only 20% to 50% of accessibility issues are auto-detectable, cites 2.2 billion visually impaired people, and demonstrates concrete tools and workflows: using axe and eslint-plugin-jsx-a11y while developing, running pa11y and Lighthouse from the CLI, and gating checks with GitHub Actions. Shows browser DevTools accessibility tree, contrast and tab-order checks, Storybook and unit tests, and emphasizes manual checks with VoiceOver/Narrator/Orca/TalkBack and keyboard navigation to validate real-world behavior.
AI-written summary · about
chapters (11)
- 0:00Web accessibility intro
- 3:44Why accessibility matters
- 6:13Testing during development
- 14:32CLI tools for accessibility
- 17:25Lighthouse accessibility audits
- 22:50Manual testing and screen readers
- 27:12Simulating vision deficiencies
- 30:45Accessibility as priority
- 33:34Q&A keyboard navigation
- 37:12Q&A tool reliability
- 40:02Q&A hiring disabled testers
related talks
30mTesting Web Accessibility
56mAccessibility Testing 101
33mAutomated Accessibility Testing
45mTips from the Trenches: Accessibility Testing
31mDecoding web accessibility through testing
21mTesting A11y: Validating Web App Accessibility
01h 05mAccessibility Testing 101
43mLucky Nkosi: A11y Beyond the Theory: Integrating Accessibility Testing into Your Workflow