Real-browser audits
axe-core in a real browser against WCAG 2.0, 2.1 and 2.2, levels A and AA, per page or per recorded flow.
Read moreAccessibility · updated 2026-10-05
Accessibility audits and VPAT
axe-core audits in a real browser against WCAG 2.2 A and AA, manual-review criteria never auto-passed, 66 country standards, and a VPAT from the actual scan.
For: Accessibility leads, front-end teams under the European Accessibility Act or Section 508, and procurement teams that need a conformance report they can defend.
Capabilities
Honest about what automation cannot judge
Level AAA and judgement criteria are marked for manual review; nothing is auto-passed.
VPAT from a real scan
An Accessibility Conformance Report generated from the audit that was actually run, criterion by criterion.
66 country standards
Results mapped to the standard your buyer cites: EN 301 549 and the European Accessibility Act, Section 508, the UK Equality Act and more.
Read moreIn the pull request
Audit a preview in the pull request and fail it on findings at the level you choose.
Flows and assistive technology
Audit a recorded user flow rather than one static page, with assistive-technology checks and continuous monitoring of pages you name.
How it works
- Choose a page or a recorded flowA URL, a set of URLs, or a journey the recorder captured.
- Run the auditIn a real browser, against the WCAG version and level you need.
- TriageFindings carry the element, the rule, the criterion and a remediation; manual-review items are listed separately.
- Export the VPATGenerated from this scan, for the buyer or the regulator asking for it.
What you receive, and what we do not do
Evidence ledger
- Per finding
- The element, the axe rule, the WCAG criterion and level, and a remediation.
- Per audit
- What was tested, which criteria need manual review, and the mapped country standards.
- Per VPAT
- A conformance report generated from the scan that was run, not a template.
Limits we state
- Automation judges a minority of WCAG criteria; everything else is marked for a person to review, and we say so on every report.
- A VPAT describes your product. Our own site’s accessibility statement is partial, with the gaps named and dated.
- Mapping to a country standard is a mapping, not a legal opinion.
Plans: Solo Pro, Team and Enterprise. See the metering table.
Questions buyers ask
Can a tool make us WCAG 2.2 compliant?
No tool can. Automation finds a minority of the criteria reliably; the rest need a person. The audit here finds what it can, marks what it cannot judge for manual review, and never auto-passes a criterion.
How is the VPAT produced?
From the scan that was actually run: each criterion is filled from the audit results and the manual-review items, so the report says what was tested rather than what a template assumes.
Which standards do you map to?
Sixty-six country standards, including EN 301 549 and the European Accessibility Act, Section 508 and the ADA in the United States, the UK Equality Act and India’s RPwD Act.
Try it on your own application
The Free plan has no time limit and asks for no card. Or bring one flow from your product and we record it live.