Tips from the Trenches: Accessibility Testing
summary
Estimating one billion people with disabilities, the talk argues that accessible products reduce legal risk and improve UX while catching roughly 40–50% of issues with automated tools; practical steps include using axe/axe-core (DevTools, CI), Accessibility Insights and Lighthouse, screen readers (VoiceOver, JAWS), eslint-plugin-jsx-a11y linting, and keyboard and unit/integration/end-to-end checks. WCAG levels A/AA/AAA guide targets, six common failures (low contrast, missing alt, labels, empty links/buttons, document language) get most fixes, and brownfield remediation often runs tens of thousands of dollars.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:34About Manoj Kumar
- 3:52Accessibility Primer
- 6:51Takeaway
- 9:55Digital Accessibility
- 12:10Levels of Accessibility
- 13:58Triple A
- 15:18Accessibility in Software Development
- 16:26Planning for Accessibility
- 19:04Design Phase
- 21:06Development Phase
- 22:43Testing Phase
- 24:58Accessibility Testing
- 26:01What can we test
- 27:12Demos
- 27:58Voiceover
- 31:38Use plugins
- 34:55Lighthouse
- 40:59Accessibility Test Pyramid
