Got a demand letter about your store's accessibility?

• 469 → 20

  WCAG failures on the W3C's own broken-vs-fixed demonstration site, measured by our engine (96% fewer).

• 3 witnesses

  Two separately built rule engines must independently report the same defect on the same element before it is marked corroborated. A screen reader reads every page as well, and its transcript is saved as evidence.

• 42 gates · 65 tests

  42 automated gates and 65 sabotage tests — our engine is audited harder than your site ever will be.

• SHA-256

  Every screenshot, tree and transcript is fingerprinted the moment it is made.

We scan our own site

An accessibility vendor whose own site fails a scan is a joke. Here is ours, run on our engine, in full.

How it works

1. Scan. With your written authorization we crawl an agreed set of pages. Two rule engines and a screen reader examine each one.
2. A human triages it. Every finding is read by a person before it reaches you. Machines cannot tell a good alt from a filename; we can.
3. Fixes written out, located by template. Not "your site has 400 errors" — the specific change, in the specific template. Fixing product once fixes every product page.
4. Evidence package with a named signature, and a verification re-scan. Someone signs it. After you fix, we scan again and show what changed.

What the screen reader hears

Honest limits

• An automated scan is a floor, not a certificate. It finds what machines can decide. It cannot tell you a site is accessible.
• Some failures need a human, and we use one. Whether alt text is meaningful, whether captions are accurate, whether focus order is logical — judgment, not rules.
• Third-party apps and embeds are often the problem and rarely ours to fix. Review widgets, chat bubbles, payment iframes: we report them, we tell you which vendor owns the fix, and we cannot force that vendor to ship it.
• We test with a screen reader, not with every screen reader. NVDA and JAWS interpret the same markup differently; passing here is not a promise about a reader we did not run.
• Fixes can regress. A theme update can undo a month of work. That is what monitoring is for, and why every report is dated.
• We do not provide legal advice and cannot certify compliance. Nobody can, by automated means. Anyone promising it is selling something they cannot deliver.

Pricing

Scope caps, stated up front: one site · up to 8 template types · up to 60 content items · one revision round. Beyond that, $12 per additional item. We would rather cap the scope than discover it halfway.

Not included: fixes to third-party apps or embeds we do not control · native mobile apps · PDF or document remediation · video captioning or audio description · legal advice or representation · any claim of certification.

For agencies

We run the audit; you deliver it under your brand. White-label without laundering: partner reports carry your brand and our engine's identity. Evidence provenance never disappears — our own test suite fails any report that tries.

For counsel

Dated method, named signatory, before-and-after evidence on the same scope, and artifacts fingerprinted at capture so a report can be re-verified later. We state what was tested, when, and with which versions. We do not certify compliance, and we will say so in writing.

Free scan