How Clearpath turns scans into an evidence trail lawyers accept
A compliance score means nothing in a legal dispute. What matters: what was scanned, when, against which standard, and what changed since. Clearpath is built around that record.
Most accessibility tools optimize for a number — "your site is 87% compliant." That number is legally and practically meaningless: WCAG conformance is per-criterion, per-page, per-state, and an 87 tells you nothing about whether a screen-reader user can complete checkout.
Scans as immutable records
Every Clearpath scan is stored as an immutable record: the exact page states scanned, the axe-core ruleset version, the WCAG 2.2 AA criteria evaluated, every violation with selector and screenshot, and the commit hash of the deploy that triggered it. Records are append-only — you can't quietly re-run history.
- Each violation maps to the specific WCAG success criterion it breaches, not a proprietary category
- Dated, exportable reports — the format legal teams actually request during a demand letter
- A regression diff per deploy: what was fixed, what broke, what's still open
- Baseline handling so legacy issues are tracked as debt, not noise
Why CI placement matters
The gap between annual audits is where lawsuits live. A quarterly PDF describes your site as it was; a pull-request check describes it as it's about to be. Clearpath blocks the regression before merge, which is cheaper than any remediation project and infinitely cheaper than a settlement.
Clearpath
LiveAccessibility monitoring that lives in your CI, not a quarterly audit.