Skip to main content
WCAG 2.1 AA · axe-core 4.11 · for developers

The accessibility scan
that ships real code

Paste your URL. Free scan returns your top 3 WCAG 2.1 AA rule violations with the exact HTML element, the W3C rule citation, and a plain-English failure explanation. Paid plans unlock every violation and a developer-reviewable AI code fix per occurrence — never an overlay widget.

Informational only — not legal advice. ADA and state-law obligations vary by jurisdiction and business type.

Free scan shows top 3 issues. No credit card required.

Engine
axe-core 4.11
Same engine that powers Lighthouse and Pa11y
Standard
WCAG 2.1 A & AA
The conformance level courts and the DOJ reference
Rules tested
50+
Every reachable WCAG 2.1 AA success criterion
Lawsuits / year
4,000+
Federal ADA web filings, $15K–$75K typical settlement
What you get

Not a widget. A deliverable.

Every scan produces something an engineer can act on the same day: real rules, real selectors, real code.

Every WCAG 2.1 AA violation

We run the full axe-core 4.11 ruleset against every reachable element on the page. Each finding cites its W3C success criterion and lists every selector where it appears.

Code fixes, not summaries

Paid plans generate a before/after snippet for every violation your dev team can paste into the template — always reviewable, never auto-applied. Free scans show the failure explanation so you can validate the tool before paying.

Whole-site scanning

Submit one URL and we'll read your sitemap, scan every page, and roll the findings into one shareable report with per-page drill-downs. Up to 500 pages on Business.

The report

A deliverable your dev team will actually open.

Same WCAG rule triggering on twenty elements? It collapses into one finding with a count badge and an expandable list of every selector. Sortable by impact. Printable to PDF. Shareable as a link.

  • Severity-weighted compliance score with editorial-grade scoring methodology
  • Findings grouped by WCAG rule, sorted by score impact
  • Per-occurrence selector, current HTML, and the axe failure explanation (AI-generated code fix on paid plans)
  • Print / save PDF with auto-expanded findings
Read the scan methodology
Why this matters

Plaintiff firms run the same scan you can.

The most-cited tools in ADA web demand letters — axe-core, Lighthouse, Pa11y — are the same engines we use. What ADA CodeFix flags is what their experts will flag. Settle for $15K–$75K, or fix it before the letter arrives.

Informational only, not legal advice. Specific ADA Title II / Title III obligations vary by jurisdiction. Consult an attorney before relying on this for any compliance decision.

Workflow

Three steps, one shareable report.

  1. 01

    Submit your URL

    Single page from the homepage, or whole site from the dashboard. We resolve your sitemap and queue every reachable page.

  2. 02

    We audit

    A real Chromium browser opens each page, runs the full axe-core 4.11 ruleset, and captures every WCAG 2.1 A and AA failure with selector + HTML.

  3. 03

    Get the deliverable

    Grouped findings sorted by score impact, per-occurrence code fixes, shareable URL, printable PDF. Your engineers know exactly what to ship.

FAQ

Questions worth answering.

What is ADA website accessibility?

WCAG 2.1 AA is the technical standard most commonly referenced for ADA web accessibility. The DOJ's 2024 Title II rule adopts WCAG 2.1 AA for state and local government web and mobile content, with phased compliance dates based on entity size. Private businesses' obligations under Title III vary by jurisdiction and circuit, but courts and the DOJ routinely reference WCAG 2.1 AA. This is informational only, not legal advice.

What do ADA website lawsuits cost?

Public-record ADA web accessibility settlements commonly range from $15,000 to $75,000 or more, plus remediation costs and legal fees. More than 4,000 federal ADA web cases are filed each year, with additional state-court filings (notably under the California Unruh Civil Rights Act). Actual exposure varies significantly by jurisdiction, business size, and the specific accessibility issues identified.

Do overlay widgets satisfy ADA Title III?

Multiple federal courts have held that overlay or "accessibility widget" products do not, by themselves, satisfy ADA Title III. Meaningful accessibility generally requires changes to a site's underlying HTML, CSS, and ARIA — which is what ADA CodeFix surfaces as developer-reviewable code suggestions.

What WCAG standards does ADA CodeFix test against?

ADA CodeFix tests against WCAG 2.1 Level A and AA criteria, which is the standard referenced by ADA Title II regulations. It checks over 50 accessibility rules using the industry-standard axe-core testing engine.

How are AI code fixes generated?

When we detect an accessibility violation, we send the specific HTML element and WCAG rule to an AI model that generates a corrected code snippet. Fixes are suggestions — always review before applying. Unlike overlays, these are real changes to your source code.

What's included in the free scan?

The free scan runs a full WCAG 2.1 AA audit on your page and shows your top 3 rule violations — one representative occurrence per rule — with severity, the exact HTML element, the WCAG criterion, and a plain-English explanation of why each element fails (from axe-core's failureSummary). AI-generated code fix snippets unlock on the paid plans, along with every occurrence and whole-site scanning.

How is ADA CodeFix different from overlay widgets?

Overlay widgets add a JavaScript toolbar on top of your broken code. ADA CodeFix identifies the specific violations in your source code and generates real HTML, CSS, and ARIA fixes you apply directly. Courts have ruled overlays insufficient — only real code fixes provide genuine compliance.

Ready when you are

Scan your site in 60 seconds.

Free scan, no signup required. See the top three findings with severity, WCAG citation, current HTML, and a plain- English failure explanation. Upgrade for AI-generated code fixes, every occurrence, and whole-site scanning.

Real WCAG 2.1 AAReal code fixesNo overlay widgets