Skip to content

Details

Shift left for Accessibility: Our journey with axe in CI/CD

"Accessibility shouldn’t be a last-minute check—it should be a first-class citizen in your code. Here’s how we enabled our engineering teams to shift left with axe in CI/CD."
In this session, we’ll share how our team enabled developers to catch accessibility issues early by integrating axe into their workflows. You’ll learn:

  • The technical foundation:
  • axe linter in VS Code/IntelliJ (real-time feedback for developers)
  • CI/CD pipeline integration (static analysis with SonarQube external issue mapping)
  • axe Watcher + Cypress E2E tests (automated reporting to axe Developer Hub)
  • Chrome extension rollout (licensing, onboarding, and tooling support)
  • Scaling the solution:
  • Phased rollout strategy (team-by-team adoption with minimal disruption)
  • Community of Practice (CoP) sessions (driving awareness and shared ownership)
  • What’s next?

We’ll preview our roadmap for deeper integration—and how we plan to expand enablement across the org.

We hope this inspires you to explore how accessibility automation could work for your teams.

You may also like