Ship accessible. Stay accessible.
AccessLint checks your app for accessibility issues as you build, on every pull request, and on your live site, so problems get caught, not shipped.
Coverage from pull request to production
The pull request review catches what your team would introduce. Monitoring catches everything that reaches production without a pull request.
In development
Catch issues in the tests you already run: assertions for Playwright, Vitest, and Storybook, plus a Chrome extension for spot checks.
In review
AccessLint reviews every pull request, auditing the changed files and commenting inline so regressions are flagged before they merge. See pull request reviews.
In production
Monitor real user journeys on your live site. A new accessibility issue triggers an alert you can trust, with evidence you can share. See monitoring.
Try it now: scan any page or repo
Try: demo.accesslint.com/broken · github.com/AccessLint/demo
One engine, so the two halves agree
The same rules that review your pull request walk your production journeys. A review comment and a monitoring alert cannot disagree about what counts as a violation, because there is only one definition of one: @accesslint/core, with 95 rules, zero dependencies and a 53ms median audit.
The toolkit
Core
A zero-dependency WCAG engine for browsers, headless browsers, and server-side DOMs.
Playwright
Accessibility assertions for your Playwright end-to-end tests with a single matcher.
Vitest
Accessibility assertions for your Vitest test suite with a single matcher.
Storybook
Accessibility feedback for every component in your Storybook.
a11y agent
Real-time WCAG auditing in your browser with AI-powered guidance.