What you actually get
after a scan.
Every scan produces a dated document: the score, the verdict at each WCAG level, and every finding mapped to the success criterion it fails. Below is a real one, page by page — the site scanned is our own demo store.
Real report · Real findings · Sample data from our demo store
- 01Cover
The score, and what it is not
The first page carries the site, the scan id, the timestamp and the score out of 100 — and, directly underneath, a sentence saying the score is a severity-weighted health signal rather than a WCAG or ADA conformance claim. That sentence is on every report we produce.
Most tools put a badge here. We put the caveat.

- 02Verdicts
Pass, review, or fail — per level
Level A, AA and AAA are judged separately. A level fails when it carries a confirmed must-fix issue, sits at review when it carries only should-fix advisory findings, and passes when it carries neither. Best-practice findings never break a level card, which is why the count and the verdict can disagree without either being wrong.

- 03Findings
Every issue, against the criterion it fails
Findings are grouped by level and listed with a priority, a severity, the rule that caught it, the WCAG success criterion number, how many times it occurs and across how many pages. Detected by axe-core and Pa11y, with the engine named on each row so a developer can go and read the rule.

- 04Advisory
The findings that do not change the verdict
Contrast and colour, performance and mobile, and best-practice groups are reported separately, along with a count of the checks that need a human and could not be decided automatically. Keeping them out of the verdict is what stops a score being padded by things that are not conformance failures.

The documents around the report.
Accessibility statement
A publishable statement generated from your latest scan, on every plan including the free ones.
ACR / VPAT report
The conformance report procurement teams ask for, against the VPAT template. Pro plans.
PDF and Excel exports
The same findings as a spreadsheet, for handing to a developer or working through as a backlog.
Re-scan and compare
Run the same scope again after the fixes and keep both reports. Two dated documents is the evidence.
Run one on your own site.
The free plan is enough to see it.
Create an account, paste a URL, and get your score and top issues on screen in about a minute. No card, no trial clock, nothing installed on your site.