AllyProof: WCAG Audit, AI Fixes & VPAT

About

Find and fix WCAG accessibility issues on any website without leaving your browser. AllyProof runs the industry-standard axe-core engine locally on the page you're viewing and reports every
WCAG 2.1 / 2.2 Level AA violation it finds — with severity, the failing element, the success criterion that was breached, and a one-click jump to an AI-rewritten fix.

Built for the teams who actually have to ship the fixes. No overlays. No "one-line script that makes you compliant." Just the same evidence-grade axe-core scan that auditors use, surfaced
where you already work.


  WHO IT'S FOR
  • Web agencies maintaining client sites under ADA Title II, the EU Accessibility Act, or Section 508
  • In-house frontend developers shipping accessibility fixes sprint by sprint
  • Accessibility consultants doing site-by-site or template-by-template audits
  • Product managers building a case for an a11y backlog
  • Procurement teams that need DRAFT VPATs in response to RFP questionnaires


  WHAT THE EXTENSION DOES — NO ACCOUNT REQUIRED
  • One-click WCAG 2.2 AA scan of the current page
  • Severity-coded toolbar badge with the live violation count (red for critical, orange for serious, etc.)
  • Side panel with the full violation list — dock right, left, bottom, or detach as a floating window so it stays visible alongside the page
  • "Show on page" highlights the failing element in the live DOM with a contrast-safe outline
  • Plain-language explanation of the WCAG criterion behind every violation
  • Local-first storage: results live in your browser, the last 50 scans are kept on the device
  • Works on any http(s) page; no scan is sent off-device

  The free local scan covers roughly 57% of WCAG issues that can be detected automatically — the same coverage you get from axe DevTools or Lighthouse's accessibility audit. The other ~43%
  (focus order, meaningful sequence, alt-text appropriateness, etc.) need a human eye, and we tell you which ones in the violation detail panel rather than pretending they don't exist.


  WHAT YOU GET WHEN YOU CONNECT A FREE ALLYPROOF ACCOUNT
  • Save scans to your dashboard for trend tracking and team sharing
  • AI-rewritten fix code on every violation, generated by Anthropic's Claude — pasted straight into your editor, ready to test
  • Multi-page crawl: kick off a full-site scan from the toolbar and watch results land in the dashboard in real time
  • DRAFT VPAT export (Section 508 + WCAG 2.2 AA template, clearly labeled DRAFT, ready for your accessibility lead to sign off)
  • Weekly auto-scans across every site in your workspace, with email digests
  • Public shareable reports for clients and stakeholders
  • Jira integration (Agency tier) — push violations as tickets in one click


  WHY AGENCIES PICK ALLYPROOF
  • Multi-site dashboards from $79/month — one workspace, every client
  • White-label public reports
  • DRAFT VPATs that procurement actually accepts
  • Same axe-core engine your auditor uses — the score in the popup matches the score in the report
  • A real engineering team behind it, based in the EU, GDPR-compliant by design


  PRIVACY-FIRST DESIGN
  • No <all_urls> host permission — the scanner only runs on the tab you ask it to, on a user click
  • activeTab + scripting only — same scope axe DevTools and WAVE request
  • chrome.storage.sync is NEVER used — your account tokens never leave the device they were minted on
  • No analytics, no tracking pixels, no remote code loading, no eval'd scripts from the network
  • When you sign in, only the data you explicitly save (a scan, a crawl request, an AI fix lookup) is sent to AllyProof — no telemetry, no background phone-home
  • Full open-source-style transparency: every permission has a written justification in our developer-console listing
  • Read the full policy at https://allyproof.com/privacy


  WHAT THIS EXTENSION IS NOT
  • Not an accessibility overlay. Overlays were fined $1M by the US FTC for misleading compliance claims. We don't ship one.
  • Not a "make your site compliant" button. No tool can do that. We surface the violations; humans (or our AI suggestions) fix them in your codebase.
  • Not a tracker. We don't profile your browsing.


  OPEN STANDARDS
  Powered by axe-core v4.11 (Deque Systems, MIT licence). Scoring and severity classifications match the AllyProof dashboard so the number you see in the popup is the number your team sees in
  the report — no surprises in the handoff.


  COMPATIBILITY
  • Chrome 116+ (full feature set including the native side panel)
  • Microsoft Edge 116+ (same Chromium build)
  • Brave, Arc, Opera, and other Chromium browsers (sideload supported)
  • A Firefox build is in review on addons.mozilla.org


  PRICING
  The extension is free. The local quick-scan, side panel, badge, "Show on page" highlights, and the last 50 scans work without any account at all.

  AllyProof account features start at $79/month (Starter — 5 sites, weekly scans). Agency is $249/month (25 sites, daily scans, Jira, white-label reports). Enterprise is $399/month (custom
  limits + dedicated support). Full plan details at https://allyproof.com/pricing.


  GETTING STARTED
  1. Install the extension
  2. Click the toolbar icon on any page you want to audit
  3. Read the results — the most severe issues are listed first
  4. (Optional) Sign in to save the scan, generate an AI fix, or run a crawl


  SUPPORT & FEEDBACK
  • Website: https://allyproof.com
  • Documentation: https://allyproof.com/docs
  • Privacy policy: https://allyproof.com/privacy
  • Terms of service: https://allyproof.com/terms
  • Email support: [email protected]

  Found a bug or have a feature request? Drop us an email. We read every message and ship fixes in days, not quarters.


  ABOUT ALLYPROOF
  AllyProof is built by accessibility-focused engineers who got tired of watching agencies juggle three audit tools, two spreadsheets, and a Word-doc VPAT every time a procurement request came
  in. We've consolidated the workflow into one platform that respects your time, your clients' data, and the WCAG standard itself.

  A few notes:
  - Keeps the FTC/accessiBe distinction explicit ("not an overlay") — defensible, on-brand, and good SEO for buyers searching that comparison.
  - Mentions Firefox is "in review" — only true once you actually submit it. If you publish Chrome before Firefox, swap that line to "Firefox build available shortly."
  - Includes the 57% / 43% framing honestly — Chrome reviewers don't love overclaiming, users don't love being misled.
  - Pricing is exposed — Chrome's policy explicitly requires this if the listing implies paid features.