> Markdown version of [/videos/1578-accessibility-test-driven-development](https://www.wearedevelopers.com/videos/1578-accessibility-test-driven-development). 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).

---

# Accessibility Test Driven Development

Adding accessibility to finished software is like stuffing blueberries into a baked pie. It causes bugs and technical debt. Shift left using test-driven development instead.

- **Speakers:** [Maria Korneeva](https://www.wearedevelopers.com/@maria-korneeva)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 23:33
- **URL:** https://www.wearedevelopers.com/videos/1578-accessibility-test-driven-development

## Summary

Treating software accessibility as an afterthought often results in the "blueberry pie problem"—trying to bake in essential components when the product is already finished, leading to production bugs and technical debt. Because accessibility remains largely absent from foundational computer science curricula, it operates as an unknown block for many engineering teams. To combat this, adopting an accessibility test driven development mindset helps teams shift left, treating inclusive design as a fundamental code quality requirement rather than a post-release compliance checklist. By defining accessible names, error state announcements, and keyboard focus routing before writing the actual code, teams can minimize late-stage regressions and build more robust applications.

Implementing this shift requires layering automated tooling across the entire software development life cycle. During the design and pre-commit phases, teams can leverage plugins for Figma and static analysis tools like axe-linter alongside ESLint to catch early contrast or missing semantic HTML attributes. As component features are readied for deployment, integrating jest-axe into unit tests or establishing clear queries via Testing Library creates essential guardrails against breaking changes. Further down the pipeline, CI CD implementations using Lighthouse CI, Cypress, or Playwright automatically intercept larger violations. However, the timing of testing introduces a core tradeoff: earlier pre-merge testing prevents deep architectural issues but can only evaluate static attributes, whereas end-to-end stages accurately capture complex interactive states at the cost of being heavier and slower.

Successfully scaling these automated accessibility pipelines requires pragmatic configuration to preserve development velocity. Instead of chasing a purely hypothetical hundred percent test coverage, engineering teams should evaluate high-traffic, transactional workflows and establish non-blocking cron jobs to monitor baseline metric drift without freezing releases. Furthermore, engineers must remain vigilant regarding the limitations of automated auditing. Unlike traditional test driven development where a passing unit test guarantees specific behavioral execution, automated accessibility checks are notoriously prone to false negatives. Scanners inherently struggle to interpret the nuances of shadow DOM architectures, opaque custom web components, or usability failures where critical context is conveyed exclusively via interface color, underscoring that human validation remains irreplaceable.

**Keywords:** accessibility test driven development, shift left testing strategy, web accessibility auditing, lighthouse CI configuration, jest-axe component testing, cypress end-to-end testing, playwright accessibility checks, keyboard focus management, screen reader compatibility, automated accessibility pipelines, automated testing false negatives, shadow DOM testing challenges, semantic HTML validation, CI CD pipeline optimization, european accessibility act compliance

## Chapters

1. **The blueberry pie problem and shifting left** (00:05) — Treating accessibility as a fundamental code quality from the beginning prevents the difficulty of retrofitting it later.
1. **Risks of testing accessibility late in production** (04:51) — Relying on users to discover edge cases in a live application risks customer dissatisfaction and silent churn.
1. **Manual and assisted checking in test environments** (05:45) — Browser extensions and AI tools can catch unlabelled headings or contrast issues visually in staging deployments.
1. **Blocking inaccessible code in deployment pipelines** (07:38) — Running automated checks via Lighthouse CI and Cypress ensures accessibility regressions prevent code from reaching staging environments.
1. **Writing accessible unit tests before merging code** (11:20) — Anticipating focus states and error announcements during component testing guarantees expected guardrails are firmly in place.
1. **Static code analysis and design phase checks** (15:12) — Implementing frontend linters and mockup tools stops structural accessibility problems before complete logic is written.
1. **Balancing pipeline performance with accessibility coverage metrics** (17:00) — Selectively skipping redundant contrast rules and avoiding arbitrary coverage metrics prevents slow commit publishing times.
1. **Benefits and limitations of accessibility test coverage** (19:58) — While automated protocols accelerate feedback loops, they can yield false negatives by missing subjective styling or shadow DOM interactions.

## Related Moments

- [Implementing a shift-left accessibility testing strategy](https://www.wearedevelopers.com/videos/100170-continuous-accessibility) (from "Continuous 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")
- [Testing accessibility with manual checks and automated tooling](https://www.wearedevelopers.com/videos/1239-accessibility-in-react-application) (from "Accessibility in React Application")
- [Defining the goals of continuous accessibility testing](https://www.wearedevelopers.com/videos/100170-continuous-accessibility) (from "Continuous Accessibility")
- [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")
- [Reviewing key learnings for continuous accessibility integration](https://www.wearedevelopers.com/videos/100170-continuous-accessibility) (from "Continuous Accessibility")

## 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**
- [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub**
- [QA Automation Engineer](https://www.wearedevelopers.com/jobs/ext/1414297-qa-automation-engineer) at **Bitpanda**
- [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.**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**