What makes it different
Built to be checked, not just believed.
Anyone can put a number on a file. The question worth asking a tool is what the number counted, what it left out, and whether you can see the working. Here is where we land on that, and the six things that follow from it.
One upload, two answers
Every file you put in gets a brand result and an accessibility result on the same screen, from the same upload. Brand consistency and accessibility are usually two tools, two subscriptions and two reports that never meet. Here they are one pass over the same file.
Measured against your Blueprint, not a generic rulebook
Your approved logo artwork, your hex values, your typefaces. Logo and colour are measured against what you actually signed off, to the pixel — so a near-miss on your red is a finding, not a matter of opinion. Set the Blueprint up once and every check afterwards is against your brand, not a general idea of good practice.
Documents, not just web pages
PDFs, PowerPoint decks, Word files, Excel workbooks, images and SVGs — read as the original file, not a flattened screenshot or a converted copy. Most of what an agency actually ships is a document, and a document is where an accessibility problem is least likely to be noticed and most likely to be forwarded.
The number shows its work
Every check we run and every formula behind a score is published on one page — and that page is generated from the same file the engine scores against, so it cannot quietly drift from what the product does. If a score matters enough to put in front of a client, you should be able to see how it was arrived at.
Read the methodologyIt tells you where automation stops
Roughly a third of the WCAG criteria can be tested by a machine at all. The rest need a person. We list those as needing a person rather than folding them into the number, and every report states which pages it covered. A clean automated result is described as exactly that, and never as a verdict on the whole file.
What automation can and cannot decideA known problem never improves the score
When a finding is set aside, the reason is recorded with a name and a date. Only exceptions written into the standard itself — a logo, an image marked decorative in the file — leave the calculation. Anything else stays a known issue, counted as a failure and disclosed on the report. A number that can be talked upwards is not worth showing anyone.
Check one real file and see what comes back.
Upload something you shipped last week. You will have a brand result and an accessibility result, with the working shown, in a few minutes.