Continuous Accessibility

In this session, I will demonstrate how to move accessibility with low effort from an "afterthought" to a systematic verification process using fast unit checks (jasmine-axe, jest-axe, vitest-axe) and realistic E2E scans (Cypress, Playwright). Instead of manually checking accessibility shortly before release, we shift feedback to the left: components are validated in isolation during testing, and critical user flows are scanned in real browsers. This is not just about tools, but about robust routines: ensuring stable UI states before scanning, maintaining consistent WCAG tags/severity levels, generating actionable reporting in CI, and establishing clear gate rules ("build fails on serious/critical"). Furthermore, I will shed light on the practical side: how teams handle exceptions (with justification and expiration dates), how to choose the right scopes (e.g., scanning a dialog instead of the entire page), and why uniform guardrails across unit and E2E tests are crucial for making accessibility sustainable, scalable, and genuinely integrated into daily development.