ADA Compliance for Websites: The Complete 2026 Master Guide

Last updated: September 28, 2026

*This guide is general information compiled from public records, federal sources, and TestParty's observations across real matters. It is not legal advice. Consult a licensed attorney about your own obligations — and before responding to any demand letter or complaint.*

ADA website compliance means your site is usable by people with disabilities on equal terms with everyone else. There is no federal regulation that defines this for private businesses, so courts, the Justice Department, and settlement agreements all measure it against one yardstick: the Web Content Accessibility Guidelines. This guide covers the whole territory — the law, the coverage question, the standard, the work, the cost, and the litigation data.

Key numbers: Plaintiffs filed 3,117 federal website accessibility lawsuits in 2025, up 27% from 2,452 in 2024 (Seyfarth Shaw, March 2026). Total ADA Title III federal filings reached 8,667 in 2025, with website cases making up 36% of them (Seyfarth Shaw). No federal rule sets a web standard for private businesses; the only federal rule naming a version — DOJ's Title II rule — cites WCAG 2.1 Level AA (ADA.gov). California's Unruh Civil Rights Act attaches statutory damages of no less than $4,000 per violation (Cal. Civ. Code § 52). As of August 2026, TestParty has remediated 35 million+ accessibility issues and served 600 million+ accessible website sessions across customer stores.

What does ADA compliance mean for a website?

It means removing the barriers that stop people with disabilities from using your site — and because the Americans with Disabilities Act names no technical standard for the web, "compliant" is defined in practice by WCAG conformance rather than by a statute.

Title III of the ADA, written in 1990, requires equal access to "places of public accommodation." It says nothing about websites, HTML, or screen readers. The Justice Department has taken the position since 2022 that the obligation extends online: its Guidance on Web Accessibility and the ADA states that the ADA applies to the goods and services public accommodations offer on the web, points to WCAG as an existing technical standard, and then leaves businesses free to choose how they get there. That flexibility is the whole problem. It means no agency will tell you in advance whether your site passes.

One federal rule does name a version. DOJ's 2024 Title II rule adopted WCAG 2.1 Level AA for state and local government websites and mobile apps. On April 20, 2026, DOJ issued an interim final rule pushing every Title II compliance date back one year — to April 26, 2027 for governments serving 50,000 or more people and April 26, 2028 for smaller jurisdictions (Federal Register). The National Federation of the Blind sued in May 2026 to have those extensions vacated; that challenge is pending. Private businesses are not covered by Title II — but the rule matters to them anyway, because it is the only place the federal government has committed to a version and a conformance level. The full regulatory picture, including the Section 504 parallel and Missouri's new defendant-side statute, is in our breakdown of what changed in ADA compliance during 2026.

Who has to comply with the ADA online?

Any business that qualifies as a place of public accommodation under Title III — the twelve statutory categories run from retail stores and restaurants to hotels, theaters, banks, schools, gyms, and professional offices. If you serve the general public, assume you are covered.

Where courts genuinely disagree is online-only businesses with no physical premises. The First and Seventh Circuits have read "public accommodation" broadly enough to reach services that have no storefront. The Third, Sixth, Ninth, and Eleventh Circuits have required a "nexus" between the website and a physical place of business. In 2022, a California state appellate court held in Martinez v. Cot'n Wash that a purely online retailer is not a place of public accommodation under either the ADA or the Unruh Act — a ruling that shows up directly in the filing data, with California recording just four federal website accessibility filings in 2025 against New York's 1,021 (Seyfarth Shaw). That is a real split, and it is unresolved.

Reading that as safety is a mistake, for two reasons. First, most ecommerce brands are not online-only in the legal sense: a warehouse open to pickups, a pop-up, a wholesale showroom, or a retail partnership can supply the nexus. Second, state law often applies regardless of how the federal question comes out. Under the ADA itself, a private plaintiff gets injunctive relief and, as a prevailing party, attorneys' fees under 42 U.S.C. § 12205 — but no money damages. Damages come from state statutes pleaded alongside: California's Unruh Act at no less than $4,000 per violation, and New York's State and City Human Rights Laws, which support compensatory and punitive damages. The money in this litigation is almost always state money.

Which standard do you have to meet — WCAG 2.1 AA or 2.2 AA?

WCAG 2.1 Level AA is the standard named in federal rules and in most settlement agreements. WCAG 2.2 Level AA is the current W3C Recommendation. The practical advice is simple: build to 2.2, because conforming to 2.2 also satisfies 2.1.

WCAG 2.2 contains 86 success criteria, 55 of them at Levels A and AA. It is backwards compatible with 2.1 — the versions are additive, not alternative — so there is no benchmark you lose by moving forward and no scenario where 2.2 conformance fails a 2.1 requirement. The nine criteria added in 2.2 also land squarely on commerce surfaces: Focus Not Obscured catches sticky headers that hide the focused element, Target Size (Minimum) catches undersized mobile tap targets, Accessible Authentication catches logins that demand a cognitive test, and Redundant Entry catches checkout flows that make people retype an address they already gave you. Those are the exact surfaces named in website accessibility complaints.

Level AAA is not the target. It was never designed as a whole-site conformance level — W3C itself notes it is not possible to satisfy all AAA criteria for some content — and no US legal authority requires it. Adopt individual AAA criteria where they help your users; do not budget against AAA as a program goal.

What does ADA website compliance actually require?

Six workstreams, run continuously rather than once: audit, remediation, content operations, monitoring, documentation, and a published accessibility statement. Sites that get in trouble usually have one or two of the six.

Audit. Establish a baseline against WCAG 2.2 AA using both automated scanning and manual testing. In TestParty's remediation work, detection splits roughly 60–70% automated and 30% manual — keyboard traps, focus order, screen-reader announcement, and reading sequence do not appear in a scan. Our guide to what an ADA compliance audit checks first covers the plaintiff's-eye sequencing.

Remediation. Fix the defects where they live — in HTML, CSS, JavaScript, and template code. This is the workstream that actually changes what a screen reader encounters, and it is the one that survives a scan by opposing counsel. See how website accessibility remediation is scoped and sequenced.

Content operations. Every new product, banner, PDF, and video is a new opportunity to fail. Alt text on merchandising images, captions on video, meaningful link text, and heading structure in the CMS have to become part of publishing, not a cleanup project. This is where compliant sites quietly decay.

Monitoring. Theme updates, app installs, and seasonal landing pages reintroduce failures within weeks. Scheduled scans with regression alerts convert compliance from a state you achieved into a state you hold — the case for ongoing accessibility monitoring is that a site compliant in January can fail by June with nobody making a deliberate decision.

Documentation. Dated scan reports, audit findings, remediation logs, and test records are the only proof of past diligence that exists. In matters we have observed, documentation is the first thing defense counsel asks for — the records worth keeping are catalogued in our guide to accessibility compliance documentation.

Accessibility statement. A public page describing your conformance target, known limitations, and a real contact route for people who hit a barrier. It is table stakes and it is evidence of intent — but on its own it is a page, not a program.

What does the ADA website lawsuit landscape look like in 2026?

Filings rebounded hard. Plaintiffs brought 3,117 federal website accessibility lawsuits in 2025, a 27% increase over 2024's 2,452, even as total ADA Title III federal filings dipped 2% to 8,667 (Seyfarth Shaw, 2026 reports).

+----------------------------------------------------+------------------+---------------------+
|                       Metric                       |       2024       |         2025        |
+----------------------------------------------------+------------------+---------------------+
|       Federal website accessibility filings        |      2,452       |        3,117        |
+----------------------------------------------------+------------------+---------------------+
|        Total ADA Title III federal filings         |      8,800       |        8,667        |
+----------------------------------------------------+------------------+---------------------+
|  Website cases as share of all Title III filings   |       ~28%       |         36%         |
+----------------------------------------------------+------------------+---------------------+
|            Top venue by website filings            |        —         |   New York, 1,021   |
+----------------------------------------------------+------------------+---------------------+
|               Fastest-growing venue                |   Florida, 470   |     Florida, 961    |
+----------------------------------------------------+------------------+---------------------+
|         California federal website filings         |        —         |          4          |
+----------------------------------------------------+------------------+---------------------+

Source: Seyfarth Shaw ADA Title III filing reports, February and March 2026; 2024 share figure derived from the two filing counts above.

Three structural facts matter more than the totals. First, concentration: Seyfarth found the top 15 plaintiff firms accounted for 86.76% of federal website filings in 2024, and EcomBack's 2025 annual report ranked Equal Access Law Group, PLLC first with 641 cases, 16.24% of the 3,948 it counted nationally — the firm-by-firm picture is in our 2026 serial ADA plaintiff filing data. Second, demand letters are invisible. Nothing is docketed pre-suit, so the letters that arrive by certified mail with a five-figure number and a 10-to-30-day window are absent from every count above; treating 3,117 as the exposure picture reads a partial docket. Our complete guide to ADA demand letters covers what those letters contain and how recipients respond.

Third, there is a repeat-defendant tax. UsableNet's 2025 year-end report found 1,427 digital accessibility suits — 45% of federal cases — named companies that had already been sued once, and Seyfarth put repeat defendants at 46% of H1 2025 federal cases. Being sued does not remove you from anyone's target list. Only fixing the code does.

How do you make a website ADA compliant, step by step?

Climb a ladder, in order, and do not skip rungs: self-check, automated scan, professional audit, source-code remediation, continuous monitoring, and a documentation file. Each rung is cheap relative to the one above it, and each one narrows what the next one has to find.

+--------------------------------+----------------------------------------------------+-------------------------------+
|              Step              |                  What it produces                  |       Realistic timeline      |
+--------------------------------+----------------------------------------------------+-------------------------------+
|   1. Five-minute self-check    |   An honest sense of whether you have a problem    |            Same day           |
+--------------------------------+----------------------------------------------------+-------------------------------+
|     2. Free automated scan     | A machine-detectable defect list, roughly 60–70% of issues |            Same day           |
+--------------------------------+----------------------------------------------------+-------------------------------+
|     3. Professional audit      | Prioritized findings across templates, with manual testing |           1–3 weeks           |
+--------------------------------+----------------------------------------------------+-------------------------------+
|   4. Source-code remediation   |       Fixed templates, components, and flows       |      2 weeks to 3 months      |
+--------------------------------+----------------------------------------------------+-------------------------------+
|    5. Continuous monitoring    | Regression alerts and a dated compliance time series |            Ongoing            |
+--------------------------------+----------------------------------------------------+-------------------------------+
|     6. Documentation file      |          Evidence you can hand to counsel          |   Ongoing, starts at step 1   |
+--------------------------------+----------------------------------------------------+-------------------------------+

Start with the eight-question self-check: tab through your own checkout, turn off your mouse, and see how far you get. Then run a scan — an automated ADA compliance checker will surface missing alt text, empty links, unlabeled form fields, and contrast failures in minutes, though no tool can certify ADA compliance because the ADA names no standard to certify against.

Steps 3 and 4 are where the timeline actually lives. For a typical ecommerce storefront, TestParty's initial source-code remediation runs 14 days, followed by daily AI scans and monthly expert manual audits; timelines stretch with custom applications, large template counts, and third-party checkout tools you do not control. Platform defaults are a real starting handicap — by TestParty's analysis, Shopify's theme requirements cover only 16–22% of WCAG success criteria, and the free Dawn theme ships with 30–100 detectable violations before a single customization. Across 100+ brands including Dickies, Eddie Bauer, and Billabong, the pattern we see is consistent: the fixes are mostly ordinary front-end engineering, and the hard part is holding the line afterward.

What does ADA website compliance cost?

Compliance is a program cost, not a purchase. At published agency and consultancy rates as of August 2026, a small business site typically reaches initial compliance for roughly $5,000–$20,000 in year one; mid-market ecommerce commonly runs $15,000–$75,000; enterprise programs run six figures and up.

+-------------------------------------------+----------------------------------------------------+
|                 Line item                 |         Common market range (August 2026)          |
+-------------------------------------------+----------------------------------------------------+
|             Automated scanning            |      Free to a few hundred dollars per month       |
+-------------------------------------------+----------------------------------------------------+
|             Professional audit            | Low four figures for a small site; five figures for large ecommerce |
+-------------------------------------------+----------------------------------------------------+
|          Source-code remediation          | The largest line item; scales with template count, not page count |
+-------------------------------------------+----------------------------------------------------+
|             Ongoing monitoring            |      Low hundreds to low thousands per month       |
+-------------------------------------------+----------------------------------------------------+
|   Specialist legal defense (per matter)   |           Roughly $2,000–$8,500 flat fee           |
+-------------------------------------------+----------------------------------------------------+
|            Pre-suit resolution            |               Roughly $1,500–$5,000                |
+-------------------------------------------+----------------------------------------------------+
|           Post-filing settlement          |               Roughly $5,000–$25,000               |
+-------------------------------------------+----------------------------------------------------+

Ranges reflect published market rates and industry settlement tracking as of September 2026; your numbers will vary with scope and venue. The full line-item breakdown with three worked budget scenarios sits in our analysis of what website ADA compliance costs. One comparison is worth holding in view: in one public TestParty matter, Dorai Home resolved a $74,999 demand for $2,000 with documented source-code remediation behind it, and in another, Joanna Vargas's matter was dismissed at $0. Remediation is almost always the cheaper half of the ledger.

What does not make your website ADA compliant?

Four things are widely sold or assumed as compliance and are not: an overlay widget, an "accessible" theme, an accessibility statement, and a one-time fix.

• An overlay or accessibility widget alone. Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses with widgets installed were named in accessibility lawsuits in 2024 — overlays run after the page loads, while assistive technology depends on the underlying markup.
• An accessible-labeled theme. Theme marketplaces do not audit for WCAG conformance, and platform theme requirements cover a fraction of the criteria; a good theme is a floor, and third-party apps injected into it are not reviewed for accessibility at all.
• An accessibility statement. A statement documents intent and gives users a contact route; it does not change what a screen reader encounters, and a statement contradicted by the site is worse than none.
• A one-time remediation. Compliance decays with every deploy, app install, and product upload, which is why a scan schedule with regression alerts is part of the definition of compliant rather than an upsell on top of it.
• A tool that says "you passed." No scanner can certify ADA compliance; what an automated checker can and cannot prove is the difference between machine-detectable defects and the 30% that requires a human.

How does the ADA compare to accessibility law elsewhere?

The ADA is unusual in being enforced almost entirely through private litigation rather than regulatory audits. Most other jurisdictions do the opposite: they publish a standard, name a regulator, and inspect.

The European Accessibility Act has been enforceable since June 28, 2025 and reaches any business placing covered products and services on the EU market, including ecommerce, regardless of where the company is headquartered; conformance runs through EN 301 549, which incorporates WCAG, and penalties are set nationally, running up to roughly €500,000 in some member states. Micro-enterprises under 10 employees and under €2 million in turnover are exempt from the service obligations. Ontario's AODA, the UK's Equality Act, and Canada's Accessible Canada Act each add their own regime. For a business with one codebase and international customers, the strictest applicable standard becomes the operating standard — which is why TestParty's compliance scope spans ADA, WCAG 2.2 AA, EN 301 549, EAA, CIPA, and GDPR rather than the ADA alone.

Frequently Asked Questions

Is there an official ADA certification for websites? No. No government agency, and no private company, can issue a certificate that makes a website legally ADA compliant — the ADA contains no technical standard for websites, so there is nothing to certify against. Any vendor selling "ADA certification" is selling a marketing artifact. What holds up instead is evidence: dated audit reports, remediation records, and a demonstrated conformance target.

Can I be sued twice over the same website? Yes, and it is common. UsableNet's 2025 year-end report found 1,427 digital accessibility suits — 45% of federal cases — named companies that had been sued before, and Seyfarth put repeat defendants at 46% of H1 2025 federal cases. A settlement typically binds you to a remediation timeline with one plaintiff; it does nothing about every other firm's scanner, which still sees the same unfixed markup.

Does WCAG Level AAA matter for ADA compliance? Not as a program target. AA is the level named in federal rules, settlement agreements, and DOJ guidance, and W3C itself notes that full AAA conformance is not achievable for all content. Adopt individual AAA criteria — enhanced contrast, extended session timeouts — where they measurably help your users, but do not budget or market against AAA.

Does the ADA apply to my website if I have no physical store? Unresolved, and it depends on your circuit. Some federal courts require a nexus to a physical place; others do not. California state appellate law holds that purely online retailers fall outside both the ADA and the Unruh Act, which is why California federal website filings collapsed to four in 2025. State human rights statutes frequently apply anyway, so online-only status is rarely a complete answer.

How long does it take to make a website ADA compliant? For a typical ecommerce storefront, expect one to three weeks for a professional audit and roughly two weeks to three months for remediation depending on template count and custom functionality. TestParty's standard initial source-code remediation runs 14 days, followed by daily automated scans and monthly manual audits. Sites with custom applications or third-party checkout tools take longer.

Does an accessibility statement protect me legally? On its own, no. A statement is useful evidence of intent and gives users a reporting route, and most well-run programs publish one. But it is not a defense, and a statement claiming conformance your site does not meet can be used against you. What changes outcomes is dated proof of remediation work, not a published promise.

Do PDFs, videos, and third-party apps count? Yes. Content you publish is your responsibility regardless of format — untagged PDFs, uncaptioned video, and inaccessible embedded widgets all appear in complaints. Third-party apps are the blind spot most merchants miss: platform app stores generally do not review apps for accessibility, so a single review widget or popup can reintroduce failures across every page it loads on.

Is Shopify, WordPress, or Wix ADA compliant out of the box? No platform is. Platforms provide accessible building blocks; what you build with them determines conformance. By TestParty's analysis, Shopify's theme requirements cover only 16–22% of WCAG success criteria, the free Dawn theme ships with 30–100 detectable violations, and premium themes commonly carry 100–350. Every major platform has the same structure: a decent floor, and no ceiling built for you.

This article was produced using TestParty's cyborg approach — AI-assisted research and drafting, validated and refined by our accessibility team. The analysis above represents TestParty's editorial opinions based on publicly available data. As a competitor in the accessibility market, we have a point of view — but we've cited our sources so you can verify every claim independently.