ADA Website Requirements: What the Law Actually Says

Last updated: October 18, 2026

The Americans with Disabilities Act never mentions websites, HTML, or WCAG — Title III's text covers "public accommodations," full stop. Courts, the Department of Justice, and three decades of settlement agreements have filled that gap, converging on one practical answer: build to WCAG 2.2 Level AA. This is a close reading of what ADA compliance for websites actually requires under the statute, the guidance, and the case law — not a how-to guide.

Key numbers: WCAG 2.2 Level AA sets 55 success criteria at Levels A and AA — the benchmark named in DOJ guidance and nearly every settlement agreement (W3C). Plaintiffs filed 3,117 federal website accessibility lawsuits in 2025, up 27% from 2,452 in 2024 (Seyfarth Shaw, March 2026). Ecommerce businesses are named in 69–77% of digital accessibility suits (Seyfarth Shaw). California's Unruh Civil Rights Act sets statutory damages of no less than $4,000 per violation (Cal. Civ. Code § 52). DOJ's Title II rule — the only federal rule that names a web standard — requires WCAG 2.1 Level AA, with compliance dates extended to April 2027 for large governments and April 2028 for small ones.

This article is a close reading of public statutes, regulations, and court filings — it is general information, not legal advice. Consult a licensed attorney about your own obligations, and before responding to any demand letter or complaint.

Does the ADA explicitly mention websites?

No. Title III, enacted in 1990, requires equal access to "public accommodations" and lists twelve categories of physical establishments — it never uses the words "website," "internet," or "online," because the commercial web did not exist yet.

The operative text, 42 U.S.C. § 12182(a), prohibits discrimination "in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation." Courts and DOJ have read that phrase to reach the goods and services a covered business offers through its website, treating the site as an extension of the business rather than requiring the statute to name it directly. DOJ formalized that position in its web accessibility guidance, stating plainly that the ADA's requirements apply to the websites of covered public accommodations.

Where courts split is whether a website needs any connection to a physical location at all. The First and Seventh Circuits have read "public accommodation" broadly enough to cover online-only services with no storefront. The Third, Sixth, Ninth, and Eleventh Circuits require a "nexus" between the website and a physical place of business before Title III applies. The Supreme Court declined to resolve this in Robles v. Domino's Pizza (cert. denied, 2019), so which circuit you are sued in still changes the legal answer to whether your site is covered at all.

What standard do courts and the DOJ actually require?

No regulation sets a binding technical standard for private-business websites under Title III. In practice, WCAG 2.1 or 2.2 Level AA is the requirement — the version named in DOJ guidance, in DOJ's own settlements, and in the one federal rule that does specify one.

DOJ's own web guidance is careful to say businesses have flexibility in how they comply and stops short of mandating one technical standard — while naming WCAG as an existing, widely recognized set of guidelines businesses can use to meet that obligation. That hedge is not an accident: DOJ tried twice to issue formal Title III web regulations (a 2010 advance notice, withdrawn in 2017) and abandoned both efforts. In the absence of a rule, three sources fill the gap and all point the same direction. DOJ's own settlement agreements with private companies have specified WCAG 2.0 or 2.1 Level AA for years. Private litigation consent decrees do the same. And DOJ's 2024 Title II rule — covering state and local governments, not private businesses — adopted WCAG 2.1 Level AA outright, the clearest signal of where the agency would land if it ever finished a Title III rule. For the compliance program this standard feeds into, see our master guide to ADA compliance for websites.

What are the concrete requirements in practice?

ADA compliance requirements for websites reduce to WCAG's four principles: perceivable content, operable navigation, understandable interfaces, and code robust enough for assistive technology. A short list of violation types recurs in nearly every complaint.

Those five violation types — alt text, contrast, keyboard access, form labels, and focus — are not a random sample; they are what a scanner or a tester finds fastest, which is why they dominate demand letters and complaints alike. In TestParty's audits across 100+ brands, automated scanning catches roughly 60–70% of WCAG issues; the remaining 30% — focus order, whether a status update is actually announced, whether alt text is accurate rather than merely present — requires a human tester, which is exactly the gap a self-check or scanner can't close on its own. Our eight-question self-check tests for several of these directly.

What triggers an ADA website lawsuit?

Most ADA website lawsuits start the same way: a tester using a screen reader or keyboard finds barriers within minutes of loading the home page, without ever placing an order or needing to.

Plaintiff-side testing operates at volume — a small number of firms run scanners and manual checks across thousands of sites, filing where the home page or a top entry page fails fast and visibly. That is one reason ecommerce absorbs 69–77% of digital accessibility suits (Seyfarth Shaw): a storefront home page, search bar, and add-to-cart flow are exactly the surfaces a tester checks first. Installing an overlay widget does not remove a site from that pool. Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses with an accessibility widget installed were named in lawsuits in 2024 — overlays run after the page loads, while a screen reader and a plaintiff's tester both encounter the underlying markup underneath it. Being sued once does not remove a business from future lists, either: Seyfarth Shaw found repeat defendants made up 46% of federal website accessibility cases filed in the first half of 2025. Our breakdown of what a demand letter contains and how the first 72 hours typically go covers the pre-suit version of this same pattern.

What are the penalties and costs?

Federal ADA Title III lawsuits carry no statutory damages — a court can order injunctive relief (fix the barrier) and, because the ADA lets a prevailing plaintiff recover attorney's fees under 42 U.S.C. § 12205, make the defendant pay the plaintiff's legal bill. The real financial exposure comes from state law layered on top of the federal claim.

California's Unruh Civil Rights Act, routinely pleaded alongside ADA claims in that state, sets statutory damages of no less than $4,000 per violation — which is why California cases settle differently than cases filed anywhere else. New York's State and City Human Rights Laws support compensatory and, in the City law, punitive damages, without a fixed statutory floor comparable to Unruh's. Below the level of an actual judgment, most matters resolve well short of trial: typical filed-case settlements run $5,000–$20,000, per industry settlement tracking as of August 2026, with many pre-suit demand letters resolving for less. Documentation moves that number more than anything else — in one public TestParty matter, Dorai Home settled a $74,999 demand for $2,000 with dated remediation records behind it, and in another, Joanna Vargas's matter was dismissed at $0. The full line-item breakdown of settlement, defense counsel, and rush-remediation costs is in our ADA website lawsuit cost analysis.

What does documented compliance look like?

Evidence, not intention. Defense counsel and courts look for a dated WCAG 2.2 AA audit, a remediation log tied to specific fixes, a published accessibility statement, and monitoring records proving the work continued after the first fix.

Four records carry the most weight. A dated baseline audit against WCAG 2.2 AA, run before any fixes ship, so there is proof of a starting point rather than a reconstruction from memory. A remediation log mapping specific findings to specific code changes, ideally verified against post-fix reference thresholds — TestParty's remediation work targets a Lighthouse accessibility score of 90 or above, WAVE errors at 5 or fewer, and axe-core errors at 3 or fewer. A published accessibility statement naming the conformance target and a real contact route — evidence of intent, though not a substitute for the other three records. And monitoring output showing the site was checked again after launch, since a theme update or a new app can reintroduce failures within weeks; daily automated scans paired with monthly manual audits is the cadence TestParty runs across its customer base. Our 21-item ADA compliance checklist organizes this into a sequence a legal or operations team can actually run.

How do the requirements differ for government sites?

State and local government websites answer to Title II, not Title III — and Title II actually has a rule. DOJ's 2024 final rule requires state and local government web content and mobile apps to conform to WCAG 2.1 Level AA, with compliance dates that an April 2026 interim rule pushed back a full year: April 26, 2027 for governments serving 50,000 or more people, and April 26, 2028 for smaller jurisdictions.

That rule does not bind private businesses — Title II and Title III are separate statutory titles with separate obligations — but it matters to every private site anyway, because it is the only place the federal government has ever committed a specific WCAG version and conformance level to a binding regulation. Absent an equivalent Title III rule, Title II is the closest thing to a preview of where DOJ's technical expectations for the private sector would land if it ever wrote one. Government entities also lack the informal "we installed a widget" argument private defendants sometimes raise; the rule specifies conformance to a named standard, full stop.

Frequently Asked Questions

Is WCAG legally required under the ADA? Not by statute or regulation for private businesses — no rule names it. Functionally, yes: DOJ's own settlements, its web guidance, and virtually every private consent decree measure compliance against WCAG, so a business with no other standard to point to is judged against it anyway.

Should I build to WCAG 2.1 or 2.2 Level AA? Build to 2.2. It is the current W3C recommendation and is additive to 2.1 — conforming to 2.2 also satisfies the 2.1 benchmark named in DOJ's Title II rule and most existing settlement agreements, so one target covers both.

Can I still be sued if I installed an accessibility overlay? Yes. Based on TestParty's analysis of Court Listener public records, more than 1,000 businesses with an overlay widget installed were named in accessibility lawsuits in 2024. Overlays sit on top of the rendered page; they don't change the underlying markup a screen reader or a plaintiff's tester actually encounters.

Does the ADA require a numeric compliance score? No. There is no pass/fail percentage or point threshold in the statute or any regulation. Compliance is judged by whether specific barriers block specific tasks for a specific user, not by an aggregate score from any automated scanning tool, however useful that score is for triage.

What happens if a business ignores an ADA demand letter? Unanswered demand letters commonly become filed lawsuits, converting a negotiable pre-suit number into a docketed federal case with its own costs. Our complete guide to ADA demand letters covers what one contains and how the response window typically works.

Does company size change what's legally required? No — Title III contains no small-business exemption for public accommodations, and size is not protection in practice. Seyfarth Shaw found 67% of businesses named in 2024 ADA Title III website filings had under $25 million in annual revenue, because filing volume is driven by how fast a site fails a scan, not by company size.

Humans + AI = this article. TestParty uses a cyborg approach to content — combining human accessibility expertise with AI capabilities to produce accurate, comprehensive guides. This content is for educational purposes and reflects our analysis of publicly available information as of the publication date. TestParty competes in the digital accessibility market, and we encourage readers to evaluate all solutions independently based on their specific needs.