Every failure names the element, the rule it broke and the number it has to hit. Tap one to copy the fix.
Pages that pass
A contract everyone agreed to and nobody runs is a document. Run it on every deploy and the share of screens that pass stops sliding.
21%Nobody checks54%A doc to follow96%Every deploy
Findings caught3,334over your first 30 months
1222040
That works out at 52 pages a month.
RegressionsFirst pass
◔◑◕●
Now30M
Findings fixed1,232,615Cleared on handsets since launch. A tally is all a scan sends home.
Nothing leaves the handset.
◎The scan runs here
The page is fetched and measured on your phone. No upload, no queue, no copy of your unreleased work on a server.
⛨Locked behind your face
History, gates and scores sit in the secure enclave. Lose the phone and whoever picks it up gets a login screen.
Before you install.
No. Point it at any address that loads in a browser: staging, a preview deploy, production, or the competitor you keep bringing up.
Sixty-one rules. Contrast, hit areas, type scale, spacing steps, focus rings, motion that ignores the reduced-motion setting, and whatever you add yourself.
The scan needs to fetch the page, so it needs a connection. Everything after that runs on the handset, history included.
Nobody. The page never leaves your phone, and the only thing that goes home is a count of findings fixed with no address attached.
It removes the part of review that is arithmetic, so the meeting is about the idea instead of the contrast ratio on one button.