Chrome & Edge extension

Find WCAG 2.2 problems in DevTools — and the ones no scanner can find.

Runs in DevTools against the page you are actually looking at. Every finding points at the element, explains what a real user would experience, and gives you a fix you can paste. Then it walks you through the 18 checks no scanner can answer.

How it works

What it will not do

Automated rules find a meaningful subset of WCAG failures — commonly cited as between a third and a half. No scanner establishes conformance on its own, and one that tells you it has is setting you up for a complaint you cannot answer.

That is the reason the guided checks exist, and the reason a completed review is recorded as human judgement rather than added to a score.

Everything it does

Questions

Does this make my site compliant?

No tool can do that, and you should be wary of any that says otherwise. Automated rules catch a meaningful subset of WCAG failures — commonly cited as a third to a half. The guided manual checks exist to cover the rest, and a completed review is recorded as human judgement rather than folded into a score.

Which browsers does it work in?

Chrome and Edge, as a Manifest V3 extension. It runs as a DevTools panel, and also as a detached window if you would rather keep DevTools for something else.

Does it work with my framework?

Every check runs on plain DOM, so React, Angular, Vue, Svelte, Rails, WordPress and hand-written HTML are all scanned identically. When a framework is recognised you additionally get the fix written in its idiom. Detection changes the suggestions, never the findings.

Does anything I scan get sent anywhere?

No. There is no backend, no analytics and no third-party SDKs. Some things are stored on your own device so they survive a restart — settings, recent scans, recorded flows, manual review notes — and each can be deleted.

What does it cost?

Every feature is free in the current release. Some are marked PRO: the licensing machinery is built and nothing is withheld, so those badges are a statement of intent rather than a gate.

Can I run it in CI?

Yes. The same engine ships as a single file with no browser APIs, so any runner that can inject a script can produce the same report as JSON.