Skip to main content
Accessibility Pro
Startscanning

Legal-risk aware compliance scanning. Overlay-free.

Every issue we report is tagged with its ADA Title III litigation tier and its EAA / EN 301 549 article. You see "Tier 1 exposure: 4 issues" at the top of every report, not "237 issues by category."

What the Team plan drafts for you

The European Accessibility Act has applied to consumer-facing websites and e-commerce since 28 June 2025. On the Team plan and above, every report has a Compliance tab with three documents:

  1. An accessibility statement draft built from the scan, as a Markdown file. It leaves blank what only a person can know: how visitors report a barrier, what a person tested and when, and what you intend to fix by when.
  2. The EN 301 549 criterion table, marking each criterion as supported, partial, not supported or not tested, so the gaps automation cannot see are named rather than hidden. Exported as JSON for your legal team.
  3. A VPAT 2.4 (Rev 508) as a Word file. Criteria no rule tested are marked Not Evaluated, never Supports.

Why we never claim full compliance

An overlay changes what a scanner sees, not what a person using a screen reader experiences. We fix the code instead, and we say plainly where automated testing stops. You get a validated remediation chain, never a compliance certificate. Your developers can run the same checks on every pull request with the accessibility GitHub Action

What a report gives a legal reviewer

  • Tier-1 count up front. The report header states how many findings sit in the litigation tier before any other number.
  • Evidence per finding. Which engines agreed, whether the live-DOM verifier confirmed it, and the exact element, page and fetch timestamp.
  • Honest coverage. Engines that skipped a page, pages that could not be reached, and criteria no engine evaluates are all reported, never scored as a pass. How often the scanner is right is published too: the precision and recall benchmark and a field audit of real websites
  • Exports you can file. Markdown, JSON, CSV and SARIF from every report, plus, on Team and above, the statement draft, the EN 301 549 criterion table and the VPAT from the Compliance tab.

Legal-risk tier examples

Tier 1
  • 1.1.1 · non-text content
  • 1.4.3 · contrast
  • 2.1.1 · keyboard
  • 2.4.7 · focus visible
  • 4.1.2 · name / role / value
Tier 2
  • 1.3.1 · info and relationships
  • 2.4.4 · link purpose
  • 3.3.1 · error identification
  • 3.3.2 · labels or instructions
Tier 3

Everything else. Still WCAG AA, but rarely makes the front page of a lawsuit.

See plans Read the published benchmark