ADA Compliance Checker: The 4-Step Method to Test Your Website Against WCAG [2026]

Last updated: September 10, 2026

No ADA compliance checker — free or paid — can truthfully certify your website, because the Americans with Disabilities Act contains no technical standard for websites. What courts and the Department of Justice consistently point to instead is WCAG 2.1 and 2.2 Level AA. A real ADA compliance check therefore means testing your site against WCAG: one automated scan, five manual checks, and a screen reader. This guide covers the full method in under an hour.

Key numbers: Plaintiffs filed 3,117 federal website accessibility lawsuits in 2025, up 27% from 2024 (Seyfarth Shaw). Ecommerce is named in 69–77% of digital accessibility suits (Seyfarth Shaw). Automated checkers detect roughly 60–70% of WCAG issues; the rest require human testing (TestParty remediation data). Most website accessibility settlements fall between $5,000 and $20,000 (industry settlement tracking as of August 2026).

Why can't any checker certify ADA compliance?

The Americans with Disabilities Act never mentions websites, WCAG, or any technical standard — which is why no honest tool will ever output the words "ADA compliant."

Title III, written in 1990, requires equal access to places of public accommodation. The Department of Justice's 2022 web guidance confirms that obligation extends to the websites of businesses open to the public, but it names no required standard. The clearest federal signal is the DOJ's 2024 rule under Title II, which adopted WCAG 2.1 Level AA for state and local government websites — the first compliance deadline arrived April 24, 2026. Private-sector complaints, settlement agreements, and court decisions define website accessibility in WCAG terms as well, because there is little else to measure against.

The practical consequence: every "website ADA compliance checker" is a WCAG checker wearing a legal label. Testing against WCAG 2.1/2.2 AA is the closest thing to an ADA compliance check that exists — and it is exactly what the method below does.

How do you check a website for ADA compliance?

Checking ADA compliance takes four steps: an automated WCAG scan, five manual checks anyone can run in 15 minutes, a screen reader spot test, and a legally prioritized reading of what you find.

+--------------------------------+-----------------+----------------------------------------------------+----------------------------------------------------+
|              Step              |       Time      |                   What you need                    |                What it establishes                 |
+--------------------------------+-----------------+----------------------------------------------------+----------------------------------------------------+
|       1. Automated scan        |   ~10 minutes   |  A free scanner (TestParty, WAVE, or Lighthouse)   |    The machine-detectable 60–70% of WCAG issues    |
+--------------------------------+-----------------+----------------------------------------------------+----------------------------------------------------+
|     2. Five manual checks      |   ~15 minutes   |             Your keyboard and browser              | Keyboard access, focus visibility, zoom, captions  |
+--------------------------------+-----------------+----------------------------------------------------+----------------------------------------------------+
|   3. Screen reader spot test   |   ~15 minutes   |      VoiceOver (Mac) or NVDA (free, Windows)       | Whether a blind shopper can actually use the page  |
+--------------------------------+-----------------+----------------------------------------------------+----------------------------------------------------+
|    4. Legal-priority triage    |   ~10 minutes   |            Your findings from steps 1–3            | What to fix first, based on what complaints allege |
+--------------------------------+-----------------+----------------------------------------------------+----------------------------------------------------+

No step requires a developer, a budget, or platform-specific tooling — the method works the same on Shopify, WooCommerce, a custom build, or a plain marketing site. In under an hour, you will know more about your legal posture than any single scan report can tell you.

Step 1: What does a free automated scan cover?

Free scanners test the machine-checkable portion of WCAG — roughly 60–70% of issues, based on TestParty's remediation data across 100+ brands.

If your store runs on Shopify, TestParty's free scanner in the Shopify App Store checks your home, collection, product, and cart templates rather than a single URL; the 60-second setup walkthrough for the free Shopify scan covers installation to first report. On any other platform, paste a URL into WAVE at wave.webaim.org, or open Chrome DevTools, select the Lighthouse tab, and run an accessibility analysis — both are free and test one page at a time.

The automated 60–70% covers color contrast, missing alt text, unlabeled form fields, link and button names, ARIA validity, heading structure, and page language. Those are the web's most frequent failures: 83.9% of home pages had low-contrast text in 2026, 53.1% lacked alt text, and 51% had unlabeled form inputs (WebAIM Million). Expect findings — in TestParty's audit data, even Shopify's free Dawn theme ships with 30–100 detectable violations.

Step 2: Which manual checks can anyone do in 15 minutes?

Five manual checks cover the high-stakes failures no scanner reliably catches, and none requires technical skill — just a keyboard, a browser, and 15 minutes.

1. Tab through your home page. Press Tab repeatedly. Every link, button, and menu should be reachable, in an order that matches the visual layout (WCAG 2.1.1, 2.4.3). Anything you cannot reach is a finding.
2. Run checkout keyboard-only. Add a product to cart and proceed through payment without touching the mouse. A dialog or drawer you cannot escape is a keyboard trap (WCAG 2.1.2) — and a purchase blocker.
3. Watch the focus indicator. As you tab, you should always see which element is active. If the outline vanishes, keyboard users are navigating blind (WCAG 2.4.7).
4. Zoom to 200%. Use Ctrl/Cmd and +. Text must stay readable with no content or function lost (WCAG 1.4.4).
5. Play a product video muted. Captions should convey everything the audio says (WCAG 1.2.2).

When TestParty runs these checks during customer onboarding, keyboard-only checkout fails most often — usually an app-injected cart drawer or promotional pop-up that traps focus.

Step 3: How do you spot-test with a screen reader?

You already own a screen reader: VoiceOver ships with every Mac (Command-F5), and NVDA is a free download for Windows. Fifteen minutes on your best-selling product page is enough for a spot test.

Navigate the page by headings first, then tab through the interactive elements, listening for three things. Images should be announced with meaningful descriptions — "red linen midi dress," not "IMG_2047" or a filename. Buttons should announce a name: "Add to cart, button," never just "button." Form fields should announce their labels, and error messages should be read aloud when something goes wrong.

Then add the product to your cart and listen. Silence after an action is a failure — a sighted user sees the cart update; a screen reader user hears nothing. You are not aiming for expert fluency here. You are listening for the moments where the interface stops making sense without eyes.

Step 4: How do you read the results by legal priority?

Read your findings the way a plaintiff's firm would: purchase-path blockers first, high-volume content failures second, cosmetic issues last.

In the demand letters and complaints TestParty has reviewed with customers, the same barrier types recur — and ecommerce draws 69–77% of digital accessibility suits (Seyfarth Shaw) precisely because claims turn on whether a shopper with a disability could browse, select, and buy.

+--------------------+----------------------------------------------------+----------------------------------------------------+
|      Priority      |                    Finding type                    |              Why it leads complaints               |
+--------------------+----------------------------------------------------+----------------------------------------------------+
|      Fix now       | Keyboard traps and unreachable controls in cart or checkout | Blocks the purchase itself — the core allegation in ecommerce suits |
+--------------------+----------------------------------------------------+----------------------------------------------------+
|      Fix now       | Screen reader blockers: unnamed buttons, unannounced updates | Renders the store unusable with assistive technology |
+--------------------+----------------------------------------------------+----------------------------------------------------+
|   Fix this week    | Unlabeled forms — search, discount codes, checkout fields | Sits directly on the money path and is trivial to verify |
+--------------------+----------------------------------------------------+----------------------------------------------------+
|   Fix this week    |         Missing alt text on product images         | The most visible automated finding; cited in complaint after complaint |
+--------------------+----------------------------------------------------+----------------------------------------------------+
|   Fix this month   |      Contrast, heading order, vague link text      |  High-volume failures, but rarely the lead claim   |
+--------------------+----------------------------------------------------+----------------------------------------------------+

A finding's severity score matters less than its location: a "minor" issue on your product template repeats on every product you sell.

What can an ADA compliance checker not tell you?

Roughly 30% of WCAG issues are invisible to automated tools — and that share includes the failures most likely to anchor a lawsuit (TestParty remediation data).

Three blind spots matter most. First, judgment: a scanner confirms alt text exists, not that it describes the product; it cannot evaluate whether focus moves in a logical order or whether an error message actually helps. Second, third-party code: apps, embeds, and marketing scripts inject markup after your theme loads, and Shopify does not review apps for accessibility before App Store approval (Shopify) — your checker tested a page those apps have since changed. Third, drift: a clean scan describes one moment, while themes update, apps install, and content ships daily.

Drift is not hypothetical. More than 40% of digital accessibility suits are repeat suits against previously sued companies (TestParty analysis of Court Listener public records). A one-time check is how defendants become repeat defendants.

When should you escalate to a professional audit?

Self-testing is triage, not defense. Escalate to a professional audit when a demand letter arrives, when you sell into the EU, or when your manual checks failed and you cannot diagnose why.

The EU raises the stakes on its own: the European Accessibility Act has been enforceable since June 28, 2025, requires WCAG 2.1 AA via EN 301 549, and carries penalties up to €500,000 per member state (European Commission; amounts vary by country). A professional audit adds expert manual testing across assistive technologies and produces formal documentation self-testing cannot — here is what a professional accessibility audit involves, from scoping to deliverables.

Remember that audits and checkers only find problems; compliance comes from fixing them in code, a path covered in this walkthrough of turning scan findings into remediated source code. TestParty pairs daily automated scans with monthly expert manual audits for customers, and as of August 2026 has remediated 35 million+ accessibility issues across customer stores.

Why should you date and keep every scan report?

A dated scan report is evidence: it shows when you tested, what you found, and what you fixed — the good-faith record counsel reaches for when a demand letter lands.

The economics are straightforward. Typical website accessibility settlements run $5,000–$20,000 (industry settlement tracking as of August 2026), and documented effort moves outcomes toward the low end. In one public TestParty matter, documented remediation helped Dorai Home settle a $74,999 demand for $2,000.

The habit costs minutes: export each report with its date, log what you fixed and when, re-scan after every batch of fixes to show the numbers falling, and store it all where your attorney can find it. Our guide to building a defensible accessibility paper trail lists exactly which records matter at each stage of a dispute.

Frequently Asked Questions

Is there an official government ADA compliance checker? No. Neither the DOJ nor any federal agency offers a website checker or issues ADA compliance certifications. The DOJ publishes guidance — its 2022 web guidance for businesses and its 2024 Title II rule adopting WCAG 2.1 AA for state and local governments — but verification is left to you. Any tool claiming to grant official ADA certification is overstating what the law makes possible.

Which WCAG version should a website ADA compliance checker test against? Test against WCAG 2.2 Level AA. It is the current W3C standard, and because it is backwards compatible, passing 2.2 AA also satisfies the WCAG 2.1 AA benchmark cited by the DOJ's Title II rule and required by the European Accessibility Act through EN 301 549. One test run covers every regime you are likely to face.

Which free ADA compliance checker is the most accurate? All reputable automated checkers hit the same ceiling — roughly 60–70% of WCAG issues (TestParty remediation data) — so the real differences are scope and workflow: WAVE and Lighthouse test one page at a time, while TestParty's free Shopify scanner covers template types across a store. This head-to-head look at free Shopify accessibility checkers breaks down what each catches and misses.

Can you be sued even if your checker shows zero errors? Yes. A zero-error scan means the automated 60–70% is clean; the manual 30% — keyboard traps, screen reader failures, illogical focus order — is where many complaints originate, and no scanner can rule those out. That is why the manual checks and screen reader spot test in this method are not optional extras.

Do accessibility overlay widgets make a website ADA compliant? In our assessment, no tool can, and overlays leave the underlying code largely unchanged. Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses with accessibility widgets installed were named in lawsuits in 2024. Separately, the FTC fined accessiBe specifically $1 million in 2025 for unsubstantiated claims about its overlay's ability to achieve WCAG compliance.

How often should you re-check your website? After every meaningful change — a theme update, a new app, a redesign, a seasonal content push — and monthly at minimum, since each change can introduce new violations. Sites drift out of compliance faster than most owners expect, which is why TestParty runs daily automated scans plus monthly expert manual audits for customers rather than annual check-ups.

TestParty practices a cyborg approach to content: AI assists with research and drafting, our accessibility experts validate every claim. This article represents our editorial perspective based on public data as of the publication date. We compete in the digital accessibility space — which means we have informed opinions, but also a vested interest. All sources are cited so you can draw your own conclusions.