WCAG 2.2 Level A and AA
Know where you stand.
Certistate audits your site against WCAG 2.2, names every failure by the criterion it breaks, and issues a dated Statement you can actually file.
What we don’t do
Automated testing catches about a third of it.
Anyone who tells you otherwise is selling an overlay. Certistate is explicit about what it can and cannot see: every Statement separates automated Findings from the criteria that require human judgement, and it tells you which is which. You will know the shape of what is left.
Certistate does not fix your site and does not make you compliant. It establishes and records your compliance state. You decide what to fix first.
The engine
Three steps, no onboarding call.
Step 1
Point it at a URL
Certistate crawls your Property, up to 25 pages on the free tier, and runs every check in the rule reference against WCAG 2.2 Level A and AA. Same origin only. It reads robots.txt and your sitemap, and it respects both.
Step 2
Read the Findings
Each one names the criterion, the element, the page, and what it would take to clear it. Every Finding carries a CSS selector, the offending HTML, and a screenshot of the element in place.
Step 3
File the Statement
Timestamped, versioned, and citable. Hand it to counsel, a client, or a procurement team that asked. It has a stable URL and prints to PDF.
Standing
Three states. No score out of a hundred.
A percentage invites you to argue with the number. A Standing tells you whether you have a Level A failure open, which is the question a court asks first.
Clear
No open Findings at the target level.
At Risk
Open Findings, none of them at Level A.
Failing
One or more Level A Findings are open.
If a vendor sold you an overlay
Certistate detects accessibility overlay widgets and records the detection in the Statement. An overlay can restyle a page. It cannot repair the underlying HTML, and it does not remove legal exposure. In 2025 the FTC took action against one such vendor over its claims.
What’s next
One engine, more frameworks.
Accessibility is where we started because the law is clearest and the failures are measurable. The engine underneath does not care which framework it is checking. HIPAA and SOC 2 are on the roadmap.
Start with the question you actually have
Is my website ADA compliant?
What the law says, what it does not say, and how to find out where you stand.
WCAG 2.2 AA in plain language
All 55 success criteria, one plain sentence each, with what automation can see.
What a VPAT and an ACR are
The document your enterprise buyer is asking for, and what filling one in involves.