1 of 34

Accessibility CI/CD

How to automate with AI & Inclusivity

2 of 34

Accessibility = A11y

3 of 34

2.2 billion

People globally experience visual impairments

4 of 34

Is A11y still broken in 2025?

5 of 34

Is A11y still broken in 2025?

Our recent 6-month Accessibility Audit Report

6 of 34

Web Accessibility

What does it mean?

7 of 34

Why is A11y always an afterthought?

8 of 34

9 of 34

The Accessibility Compliance Checklist

WCAG 2.1 Level AA and above

  • Color contrast
  • Navigation
  • Focus
  • Landmarks
  • Content Layout (200% & 400%)
  • Understandable content
  • Form handlings
  • Media
  • Typography
  • External/Internal link behaviors
  • Tab order (Flow)
  • And many more…

10 of 34

11 of 34

Accessibility issues ARE bugs

12 of 34

~30%

Common A11y Bugs are Found By Automated Tests

13 of 34

Let’s bake it in our CI/CD

14 of 34

CI/CD

Continuous Integration/ Continuous Deployment

  • CI = Automated Builds/Tests
  • CD = Deploy continuously with confidence

15 of 34

PLAN

REVIEW

BUILD

TEST

CODE

A11y Linter

A11y Tests

DEPLOY TEST

RELEASE

PRODUCTION

CI

A11y Tests

AI Feedback

PR Analysis

Automated accessibility checks in in dev, test, and deploy workflows

16 of 34

Meet The Tools

17 of 34

Meeting Tools For A11y

Test Automation

Playwright

Developer Tools

A11y Add-on

Chromatic

ESLint A11y Plugins

18 of 34

Axe-core + PlaywrightJS

E2E meets a11y

19 of 34

Evinced CLI Analyzer

Great for complex UI

20 of 34

Lighthouse CI

Make your pipeline care about A11y

21 of 34

Swimm.IO

22 of 34

Demo

  • Use ESLint to find A11y bugs
  • Playwright + Axe-core
  • Lighthouse CI + GitHub Actions
  • Swimm for PR & docs

23 of 34

A11y = AI + A11y

24 of 34

AI as A11y Assistant Agent

What Can AI Do To Help?

  • Generate E2E tests for component
  • Detect wrong pattern
  • Summarize error report
  • Offer code editing inline
  • Validate and generate PR comment
  • Enhance CI workflow

25 of 34

Demo

CoPilot Agent Mode + A11y + GitHub Actions

26 of 34

Know the Limits

AI in Accessibility CI/CD

  • AI can’t detect or fix Flow (Navigation) issue.
  • AI can’t fix 200% and 400% layout issue
  • AI can’t replace designer with actual human understanding for A11y.
  • Code quality is YOUR responsibility
  • Need human’s review

27 of 34

Adopt without Overwhelm

Take it slow, take it accessible

  • Prioritize bugs
  • Add non-blocking scans (axe-core, Evinced)
  • Use Swimm to document fixes
  • Onboard and include designer.
  • Use CoPilot Agent/Cursor help.
  • Add Playwright + axe-core tests
  • Gate PRs with Lighthouse CI
  • Document patterns
  • Enable ESLint/Storybook

Existing bugs

New feature

28 of 34

Faster Fixes, Better UX

~50+%

A11y common bugs identified with automation

~27%

A11y bugs identified by Linter

29 of 34

Let’s Build Better By Default

The Next Steps

  • Accessibility = Performance + Usability
  • Part of DoD (Definition of Done)
  • Part of Onboarding Training for Developers
  • Design with “Accessibility First” for Designers
  • Ask Cursor (or CoPilot) for help
  • Manual test is still required (but at less scope)

30 of 34

Resources

31 of 34

If your CI doesn’t catch it, your users will.

And that would already be too late.

32 of 34

MAYASHAVIN.COM

Lead Software Engineer

Web & Accessibility

Mom of 4

Illustrator

Book Author

33 of 34

34 of 34

Be Accessible.