Automating Accessibility with Playwright
summary
Demonstrates automating accessibility scans using Playwright with Axe Core and the axe‑html‑reporter, sets up via npx playwright (choose TypeScript, install browsers), runs tests on Chromium only to save time, and attaches a human‑readable HTML report. Axe finds eight violations on the demo page and after fixes the suite reports eight issues → zero. Notes Axe automates roughly 30% of WCAG’s 87 success criteria and advises failing CI merges but not blocking test deployments.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:05Accessibility is a universal right
- 4:54Disabilities and curb cut effect
- 5:57European Accessibility Act and WCAG
- 8:42Introducing Playwright
- 11:08Lighthouse limitations for accessibility
- 12:33First accessibility test with Axe and Playwright
- 14:40Better test reports with attachments
- 18:30Configuring Axe rules and exclusions
- 20:35Fixing common accessibility issues
- 25:33Automating audits in CI
- 27:18Accessibility must be built early
related talks
32mWeb Accessibility testing with playwright.js & axe-core
13mHow to Use Playwright for Automating Accessibility Testing
35mAutomated Accessibility Testing
24mAutomated Visual Regression & Accessibility Testing
33mAutomated Accessibility Testing
33mAutomated accessibility testing
30mTesting for Accessibility with aXe
30mTesting Web Accessibility