Automated Accessibility Testing
summary
Automated scanners like axe or Lighthouse catch the easy problems but only cover about 20–30% of WCAG issues (vendors quote 57% by issue count; experts measure 0–13.5% of criteria). The demo repository shows unit-level axe checks, Playwright/Cypress integration, and semantic selectors via testing-library/getByRole. Custom end-to-end tests verify keyboard tab order and a 200% text-resize layout check using clientHeight vs scrollHeight. AI image alt generators help but fail without contextual prompts; the example app and scripts are in the provided GitHub repo.
AI-written summary · about
chapters (7)
- 0:00Introduction and agenda
- 1:36Defining accessibility and WCAG
- 5:13Automated accessibility tools
- 10:31Implementing automated tests
- 15:14Writing manual accessibility tests
- 27:58AI and accessibility hype
- 34:42Closing and Q&A
related talks
33mAutomated Accessibility Testing
30mTesting Web Accessibility
56mAccessibility Testing 101
21mTesting A11y: Validating Web App Accessibility
53mAutomating Accessibility Assurance
44mTesting Web Accessibility
31mDecoding web accessibility through testing
29mBuilding Accessibility Testing into Your Workflow