Find and fix your site's accessibility gaps.

No. Automated scanning catches a large share of real-world issues — in Deque’s published audit dataset, automated testing identified 57.38% of recorded issues, including the violations most often cited in ADA lawsuits (missing alt text, contrast failures, missing labels). That is a share of issue volume, not of WCAG success criteria, and it cannot establish conformance. Manual testing by an accessibility specialist is still required. AllyProof clearly labels which criteria require manual review.

We test against WCAG 2.2 Level AA — the most current standard. This covers all criteria from WCAG 2.0 and 2.1 as well. Our primary scanner, axe-core, has a zero false-positive policy. We supplement it with HTML_CodeSniffer and APCA contrast checking for broader coverage.

Lighthouse runs a basic accessibility check on one page at a time. AllyProof scans multiple pages per site (up to your plan's page limit), tracks violations over time, generates AI-powered code fix suggestions, produces proprietary VPAT-based evidence drafts, and lets you monitor all your sites from one dashboard.

AllyProof's export is a proprietary VPAT-based evidence draft, not the official ITI report form, a completed Accessibility Conformance Report, or a certification. It covers the 55 active WCAG 2.2 A/AA success criteria with automated evidence pre-filled and leaves every official conformance level blank. A qualified evaluator must perform manual testing and complete the official report before procurement use.

Not directly, but yes — it moves rankings through the same signals Google already rewards. Semantic HTML, alt text, descriptive titles and heading hierarchy, mobile-friendly layout, and readable content are all WCAG requirements and core on-page SEO fundamentals. A widely cited SEMrush/BuiltWith study found WCAG 2.2-compliant sites rank for ~27% more keywords and earn ~23% more organic traffic. Google's John Mueller has said accessibility isn't a standalone ranking factor (it's hard to measure automatically), but the work itself produces cleaner markup, better UX signals, and better crawlability — which do. And you pick up legal safety and a wider audience along the way.

1 site, a one-time full-site scan on signup (up to 100 pages), then 25 pages per scan (15 scans per month), WCAG violation list with impact levels, the litigation-risk scoring card, a shareable scan summary, the browser extension, and 90 days of scan history. It's enough to evaluate your own site and see exactly what violations look like. The Business plan adds unlimited pages per site, weekly monitoring, AI fix suggestions, compliance reports, VPAT and accessibility-statement generation, team members, and CSV export.

If you don't cancel during the 14-day trial, your card is charged and your subscription continues at the rate of the plan you selected. Cancel anytime during the trial at no cost — your sites, scan history, and violations are preserved either way; you can downgrade to the free plan or come back later.

AllyProof tests WCAG 2.2 Level AA failure patterns and provides a proprietary draft mapping to EN 301 549 v3.2.1. That standard is harmonised for the Web Accessibility Directive and is widely used as technical guidance, but the current version is not an EAA-specific harmonised standard. EN 301 549 also contains non-web requirements that an automated URL scan cannot evaluate.