> Markdown version of [/videos/100170-continuous-accessibility?t=893](https://www.wearedevelopers.com/videos/100170-continuous-accessibility?t=893). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Continuous Accessibility

Stop treating accessibility as an afterthought. Shift left with automated, scoped tests. You will catch fifty percent of violations early and block regressions right in your pipeline.

- **Speakers:** [Jörg Jakoby](https://www.wearedevelopers.com/@jorg-jakoby)
- **Event:** World Congress 2026 Europe
- **Published:** July 9, 2026
- **Duration:** 24:43
- **URL:** https://www.wearedevelopers.com/videos/100170-continuous-accessibility

## Summary

Accessibility testing is often treated as a costly, subjective afterthought appended late in the software release cycle, leading to regressions, legal risks, and poor user experiences. By adopting a "shift-left" philosophy, organizations can transform accessibility from a manual verification bottleneck into a continuous, automated process. This proactive approach ensures accessibility thresholds become a strictly enforced part of a team's Definition of Done, shifting the focus toward preventing issues during active development rather than merely remediating them post-launch.

Implementing layered, automated testing pipelines effectively anchors this strategy. Developers can capture up to 50 percent of routine violations—such as missing ARIA tags, improper contrast ratios, or absent labels—through highly efficient unit checks using tools like vitest-axe and jest-axe. As application complexity scales, these granular checks are reinforced by comprehensive E2E integration using test runners like Cypress or Playwright. Rather than subjecting test environments to noisy, slow full-page accessibility scans, adopting "scoped scans" that isolate specific interactive scenarios (such as analyzing a dialog only after it is dynamically opened) drastically reduces execution time and dramatically improves test stability.

Successfully scaling continuous accessibility ultimately relies on rigorous CI/CD guardrails and pragmatic governance. Both unit and E2E testing layers must share a centralized rule configuration, definitively enforcing explicit standards like WCAG 2.2 AA so that pipelines automatically halt upon detecting serious or critical violations. Recognizing that legacy codebases and third-party dependencies will inevitably trigger violations, engineering teams must deploy responsible exception management routines. Instead of adopting messy legacy hacks, exceptions should be tightly tracked using dedicated issues that demand formal justification, clear ownership, and strict expiration dates, ensuring overall UI sustainability and highly inclusive workflows.

**Keywords:** shift-left accessibility, continuous accessibility testing, axe-core test integration, vitest-axe component checks, playwright E2E scanning, automated UI verifications, CI/CD pipeline guardrails, scoped accessibility scans, WCAG compliance configurations, ARIA tag validation, definition of done criteria, legacy code exception management, test-driven inclusive design, accessible dynamic states, automated screen reader validations

## Chapters

1. **Defining the goals of continuous accessibility testing** (01:07) — The core objectives of integrating accessibility checks early into the development lifecycle.
1. **Root causes and costs of late accessibility testing** (01:57) — How manual testing and lacking definitions of done lead to expensive retrofits and delays.
1. **Implementing a shift-left accessibility testing strategy** (04:18) — Expanding layered testing from automated unit configurations to comprehensive cross-functional team responsibilities.
1. **Exploring the fundamentals of unit-based accessibility scans** (06:06) — Using component-level checks to catch missing labels, contrast issues, and structural flaws immediately.
1. **Configuring axe-core in unit testing frameworks** (08:46) — Formatting component states and filtering execution violations within frameworks like Vitest and Angular.
1. **Validating complex workflows with end-to-end scans** (10:45) — The advantages of scoping accessibility scans to specific interactions rather than validating full pages simultaneously.
1. **Setting up Playwright and axe-core for testing** (13:47) — Required dependency installations needed to merge Playwright test suites with detailed axe-core analysis plugins.
1. **Automating scoped accessibility tests with Playwright** (14:53) — Running structural analysis on interactive sub-components and exporting findings to viewable HTML testing reports.
1. **Synchronizing configurations and severity levels across layers** (17:07) — Defining constant WCAG targets to maintain standardized evaluation metrics across all code testing boundaries.
1. **Managing exceptions and enforcing CI/CD guardrails** (20:12) — Approaching legacy component failures through documented exceptions while aggressively failing pipelines on critical accessibility errors.
1. **Reviewing key learnings for continuous accessibility integration** (22:12) — Reinforcing integrated accessibility approaches via layered checks, uniform targets, and strictly documented exception deadlines.
1. **Handling screen reader simulations using AI agents** (23:21) — Exploring automated AI testers and potential future strategies for covering realistic acoustic screen reader scenarios.

## Related Moments

- [Integrating robust accessibility practices into agile development workflows](https://www.wearedevelopers.com/videos/1340-wearedevelopers-live-performance-and-ai-social-media-decline-developer-events-and-more) (from "WeAreDevelopers LIVE - Performance and AI?, Social Media decline, Developer Events and more")
- [Escaping the continuous accessibility audit and fix cycle](https://www.wearedevelopers.com/videos/802-data-mining-accessibility) (from "Data Mining Accessibility")
- [Addressing web accessibility challenges in development teams](https://www.wearedevelopers.com/videos/649-making-interactions-accessible-to-all-users) (from "Making Interactions Accessible to All Users")
- [Integrating accessibility checks into automated software testing workflows](https://www.wearedevelopers.com/videos/1671-oh-s-there-s-a-new-accessibility-law-and-i-m-not-ready) (from "Oh S***! There's a New Accessibility Law and I'm Not Ready!")
- [Utilizing testing tools to audit web platform compliance](https://www.wearedevelopers.com/videos/403-the-what-why-who-and-how-of-accessibility-on-the-web) (from "The What, Why, Who and How of accessibility on the web")
- [Testing accessibility with manual checks and automated tooling](https://www.wearedevelopers.com/videos/1239-accessibility-in-react-application) (from "Accessibility in React Application")

## Related Articles

- [How Developers Can Focus on Maintaining Satisfaction With Accessibility](https://www.wearedevelopers.com/magazine/109-how-developers-can-focus-on-maintaining-satisfaction-with-accessibility)
- [The State of Accessibility on the Web in 2025: WebAIM Million Report Findings](https://www.wearedevelopers.com/magazine/570-the-state-of-accessibility-on-the-web-in-2025-webaim-million-report-findings)
- [12 ways to fix an inaccessible web site  - the CODE100 Accessibility Scavenger Hunt results](https://www.wearedevelopers.com/magazine/511-12-ways-to-fix-an-inaccessible-web-site-the-code100-accessibility-scavenger-hunt-results)
- [Find all accessibility problems in a page to take part in the CODE100 final!](https://www.wearedevelopers.com/magazine/507-find-all-accessibility-problems-in-a-page-to-take-part-in-the-code100-final)

## Related Jobs

- [Engineer, Offensive Security Organization](https://www.wearedevelopers.com/jobs/ext/1992296-engineer-offensive-security-organization) at **Twilio**
- [Software Engineer Frontend (all genders welcome) in the field of Water Line Integrity Solutions](https://www.wearedevelopers.com/jobs/ext/127888-software-engineer-frontend-all-genders-welcome-in-the-field-of-water-line-integrity-solutions) at **Rosenxt Group**
- [Senior Web Designer, Growth](https://www.wearedevelopers.com/jobs/ext/102722-senior-web-designer-growth) at **Intercom, Inc.**
- [Working Student Frontend Development](https://www.wearedevelopers.com/jobs/ext/1185791-working-student-frontend-development) at **ZEISS Group**
- [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub**
- [Staff Frontend Engineer](https://www.wearedevelopers.com/jobs/48313-staff-frontend-engineer) at **SMG Swiss Marketplace Group**