WCAG audits that fit in a click.

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.

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.