Automated WCAG 2.1 accessibility testing, delivered as an API.

Year

2025

Vertical

SaaS

The challenge

Accessibility is a legal requirement and a manual audit is a PDF that is out of date the week after it lands. Teams need the check to run on every release, not once a year.

What we built

01Accessibility testing API built on NestJS

02Headless browser rendering via Puppeteer so pages are tested as they actually render

03axe-core rule engine covering ADA and WCAG 2.1 criteria

04React dashboard for running scans and reading results

Outcomes

WCAG 2.1

Criteria covered

API-first

Runs in CI, not once a year

How we shipped it

Test the rendered page

Accessibility problems live in the DOM the browser actually builds, not in the source. Scans run through a headless browser so single-page apps and client-rendered content are tested the way a screen reader would meet them.

A rule engine, not a checklist

axe-core supplies the ADA and WCAG 2.1 rules, which keeps the criteria auditable against a published standard instead of a hand-written list nobody can trace.

API before dashboard

The product is the API — the dashboard is one consumer of it. That is what lets a team put the check in their pipeline and fail a build on a regression.