DocsRead your first scan
Read your first scan
Updated: 10 September 2026
What the scan tests, how findings are ranked, and the two things a score deliberately does not tell you.
What is tested
Every page on your plan is tested against WCAG 2.2 AA and graded by axe-core. Findings are written the way a site owner would say them — “text too light to read”, not “1.4.3 Contrast (Minimum)”. If you need a glossary to read your own report, the report failed.
How findings are ranked
Findings are ordered by risk, not by count, so the problems that actually get sites complained about come first. Every finding says which pages it affects and what fixing it involves.
The part a machine cannot judge
Roughly a third of WCAG is human judgement — whether alt text is accurate, whether an error message genuinely helps. Automated testing cannot decide those, so they are listed separately as a 16-check manual list rather than folded into a score that would look better.
Two things follow from that, and both are deliberate:
- A score is not a compliance claim. There is no certification to hold, and we will not generate a “fully conformant” statement.
- Roadmap items are labelled. Where something is planned rather than shipped, the page says so.
Fix, then verify
Nothing ships until you approve it. Once applied, a second scan re-measures on the live page. If that re-check cannot finish, the improvement figure is suppressed rather than estimated — you see that it did not finish.
Need help?
If this page did not answer your question, contact support. If it answered it wrongly, tell us that too — a documentation page that overstates what the product does is the same problem as a product that overstates itself.