WCAG audits that fit in a click.
Three focused extensions for Chrome and Edge. Each checks one thing thoroughly, tells you exactly what is wrong, and produces a report you can hand to a client. Every page is analysed inside your browser — nothing is uploaded, stored, or sent anywhere.
Goes straight to a person, not a mailing-list service. One message when the first tool is live, and nothing else — a signup form that tracked you would be a strange thing to put on this page.
4 contrast failures, 1 item needs a manual check on this page.
- 2 AA failures
- 2 AAA failures
- 1 item needing a manual check
-
AA
AaGrey at 4.478 to 1 fails AA.
4.47:1 needs 4.5:1 ·
#777777on#ffffff -
AA
AaGrey at 2.995 to 1 fails AA.
2.99:1 needs 4.5:1 ·
#959595on#ffffff -
Manual
Text on a gradient needs a manual check.
Text sits on an image or gradient. Check the lowest-contrast part by eye.
2 more not shown 2 more AAA failures
- 83.9%of home pages had low-contrast text
- 96%of home pages had detectable WCAG failures
- €100kupper end of national penalties under the EAA
Failure rates from the WebAIM Million, the annual automated study of the top one million home pages — confirm the current year's figures before launch. Penalties vary by member state; the European Accessibility Act has applied since June 2025.
Six failure types account for almost every error found on the web. These tools cover five of them.
Low contrast, missing alt text, unlabelled inputs, empty links, empty buttons. Between them they make up the overwhelming majority of what any automated audit turns up — and they are the ones with a concrete fix rather than a judgement call. Browser devtools check one element at a time. Full-site scanners return hundreds of findings across a dozen criteria and leave you to sort them out. Neither hands you something to send a client.
One failure type, checked properly
Colour is resolved through inheritance, transparency and element opacity, composited the way the browser actually paints it. Text inside shadow-DOM components and same-origin iframes is included.
A report you can send
Branded, with the page URL, the date, every measured ratio and the WCAG criterion it failed. Opens in Word and Google Docs.
Numbers you can defend
Ratios are shown as measured and never rounded up, so 4.49:1 is reported as a failure. Text on an image or gradient is flagged for manual review rather than guessed at, and never counted as a failure.
Three tools, one job each
Buy only the one you need. Each is a separate extension with a separate listing, because a tool that does one thing well is easier to trust than one that does six things adequately.
-
Contrast Auditor
WCAG 1.4.3 · 1.4.6 · 1.4.11
Every text node on the page measured against AA and AAA, plus non-text contrast for borders, icons and focus indicators.
Ships first -
Alt Text Auditor
WCAG 1.1.1
Missing alt text, empty alt on meaningful images, and the filename-as-alt and duplicate-alt patterns that pass automated checks but help nobody.
Ships second -
Form & Interactive Auditor
Labels · empty links · empty buttons
Inputs without labels, links and buttons with no accessible name, missing page language, and duplicate IDs that silently break label association.
Ships third
How we know the numbers are right
A tool like this is only worth what its numbers are worth. So the checking is not an afterthought, and none of it is a claim you have to take on faith — it all runs on every change.
-
240
Automated tests, run on every commit. The contrast maths is checked against the WCAG formula at the exact boundaries: the greys either side of 4.5:1, the 18pt and 14pt-bold thresholds, alpha compositing, inherited backgrounds.
-
0
Findings axe-core catches that we miss. axe is the engine the accessibility industry runs on. We diff against it on every fixture, and where both engines commit to an answer we agree element for element — and, for contrast, ratio for ratio.
-
7
Things we catch that axe does not. File names used as alt text, placeholders standing in for labels, and text on a dark-scheme page where axe declines to answer. Each one is written down and justified.
-
5
Fixture pages with hand-counted failures. The scanner must match the count and the exact elements — no false positives, no misses. They caught four real bugs before axe did.
-
0.3s
To scan 25,000 elements, including shadow DOM and same-origin iframes.
The site you are reading is scanned by all three tools before every deploy. It reports nothing — in light and dark, at AAA rather than AA. If our own shop window failed, the tool would be wrong or the site would be, and either way you should know.
Nothing leaves your browser
Not a policy — a property of how the extensions are built. There is no server to send anything to.
No network requests during a scan
The extensions contain no code that can make one. This is checked automatically on every commit, and asserted again in the browser before each release.
No account, and no permission to read your browsing
The scanner only runs on the tab you clicked, from the moment you clicked it. There is no sign-up, and no host permissions in the manifest at all.
Nothing stored but your own settings
A daily scan counter and your licence key, held locally. Uninstalling removes them.
Pricing
One payment. No subscription, no seats, no renewal. The free tier always shows the true number of failures on a page — it meters the detail, never the total.
Free
$0 always
- Full, honest failure counts
- First 10 issues in detail
- Five scans a day
- Eyedropper and ratio checker, unlimited
One tool
$19.99 once
- Every issue, unlimited scans
- Branded client report
- Suggested passing colours
- Multi-page reports
All three
$39.99 once
- Everything in all three tools
- Saves $19.98 against buying separately
- One payment, three listings
Questions worth asking
Why pay, when axe and WAVE are free?
Because they answer a different question. They audit everything at once across dozens of criteria and hand you a list. These tools check one failure type thoroughly, tell you which colour to use instead, and produce a report you can send to a client. If a free tool already does what you need, use it — we would rather you did that than buy something you will not open twice.
What does the free version actually do?
It always tells you the true number of failures on a page. It shows the first ten in full, says exactly what the rest are, and allows five scans a day. The eyedropper and ratio checker are unlimited and always free. The counts are never reduced to push you toward paying.
Can it prove my site is compliant?
No, and nothing can. Automated testing cannot detect every WCAG failure, and a clean result means the checks we run found nothing on the page in the state it was scanned. A full audit needs a person. We say this in the report itself rather than only in the terms.
What happens to the pages I scan?
Nothing. They are analysed in your browser and no request is made. That is checked automatically on every change to the source, so it stays true rather than being a promise made once.
What if it does not work for me?
Email hello@auditlint.com within 30 days for a full refund. No form. If you are in the EU or UK you also keep your statutory withdrawal rights.