Compliance Guide • United States Federal Law
ADA Website Compliance
Updated July 2026Reviewed by Khushwant Parihar, CPACC
How the Americans with Disabilities Act applies to websites and mobile apps: the DOJ's Title II web rule and its WCAG 2.1 AA standard, the Title III case-law landscape for private businesses, demand letters and lawsuit trends, and the practical steps that actually reduce risk.
Title II Standard
WCAG 2.1 AA
Codified by DOJ rule (2024)
Title III Web Rule
None
Courts apply the ADA case by case
2025 Federal Lawsuits
3,117
+27% year over year
Title III Damages
$0
Injunctions + fees; states add damages
ADA web accessibility, the numbers
- Title II deadline for state and local bodies serving 50,000 or more; 26 April 2028 for smaller ones
- 26 Apr 2027DOJ interim final rule,
- The technical standard the Title II rule requires; there is no Title III equivalent in regulation
- WCAG 2.1 AA28 CFR Part 35,
- website accessibility lawsuits filed in US federal courts in 2025, up 27%
- 3,117Seyfarth Shaw,
- damages available to a private plaintiff under Title III; injunction and fees only
- $042 U.S.C. 12188,
- circuits that require a connection to a physical place before a website is covered
- 5ADA website case law reference,
- appellate decisions in force holding that websites are outside Title III
- 0The Eleventh Circuit vacated its own in December 2021,
Title II vs. Title III: Which Part of the ADA Covers Your Website?
The Americans with Disabilities Act (1990) predates the commercial web, and its text never mentions websites. Digital accessibility obligations flow from two of its titles, and which one covers you determines whether you face a codified technical standard or a body of case law.
Title II — Public Entities
- State and local governments: cities, counties, public schools and universities, transit agencies, courts, libraries.
- Now has a formal DOJ web accessibility regulation with a named technical standard (WCAG 2.1 AA) and fixed deadlines.
- Enforced by the DOJ and through private lawsuits; Section 504 of the Rehabilitation Act often applies in parallel to federally funded entities.
Title III — Private Businesses
- “Places of public accommodation”: retail, restaurants, hotels, banks, healthcare providers, entertainment venues — regardless of company size.
- No formal web regulation. Courts apply the ADA's general nondiscrimination mandate to websites, and the DOJ has long taken the position that the ADA covers web content.
- Remedies are injunctive relief and attorney's fees — no damages under the ADA itself, which is why state-law claims are frequently attached.
The practical upshot: a city's website has a regulation with a deadline, while a retailer's website has thousands of court decisions and settlements pointing at the same technical standard. Either way, the work converges on WCAG conformance. For a global view of how other jurisdictions regulate this, see our accessibility laws tracker.
The DOJ Title II Web Rule: WCAG 2.1 AA Becomes Law
In April 2024, the Department of Justice published its first-ever regulation setting a specific technical standard for web accessibility under the ADA. The rule requires state and local government websites and mobile apps to conform to WCAG 2.1 Level AA, with limited exceptions for things like archived content and certain third-party materials.
The original rule set compliance dates of April 2026 for public entities serving populations of 50,000 or more and April 2027 for smaller entities and special-district governments. In April 2026, the DOJ issued an Interim Final Rule extending each deadline by one year — to April 26, 2027 and April 26, 2028 respectively — without changing the standard, the scope, or the exceptions. Our Title II deadline extension guide covers exactly what moved and what did not.
Healthcare entities: a separate, earlier deadline
The HHS Section 504 web accessibility rule — covering hospitals, providers, and other recipients of HHS funding — also requires WCAG 2.1 AA, and it was not extended. Its May 2026 compliance date has already arrived for most covered entities. Where an organization is covered by both rules, the earlier deadline controls. See our Section 504 deadline guide.
Beyond its direct reach, the Title II rule matters for everyone: it is the federal government's clearest statement that WCAG 2.1 AA is what “accessible” means under the ADA, and plaintiffs' counsel and courts cite it as persuasive authority in private-sector Title III cases.
Title III Case Law: The Circuit Split Over Websites
Because there is no Title III web regulation, the private-sector rules have been built by courts — and the federal circuits do not fully agree on when a website is a “place of public accommodation.”
- Nexus approach (Ninth Circuit and others): the ADA covers a website when it has a sufficient connection to a physical place of business. In Robles v. Domino's Pizza, the Ninth Circuit held the ADA applied to Domino's website and app because they connected customers to physical restaurants; the Supreme Court declined to review the decision.
- Broad approach (First Circuit line of cases; many SDNY/EDNY decisions): public accommodations are not limited to physical spaces, so a website can be covered on its own. This reading has made New York federal courts a magnet for filings, including against online-only businesses.
- Physical-place approach (Eleventh Circuit and similar reasoning elsewhere): courts have been more skeptical that a standalone website is itself a public accommodation. The Eleventh Circuit's Gil v. Winn-Dixie opinion — later vacated as moot, but still influential in reasoning — reflected this narrower view.
The split affects where cases get filed far more than whether businesses get sued: plaintiffs simply choose plaintiff-friendly venues (New York federal courts, California state courts). Any business selling nationally should assume it can be reached in a favorable forum. See our state-specific guides for New York and California.
Demand Letters and the Lawsuit Landscape
Website accessibility litigation is high-volume and heavily concentrated. Federal courts saw 3,117 website accessibility lawsuits in 2025 — up 27% year over year — and more than 5,000 cases including state-court filings, with 2026 on pace to set another record. E-commerce and retail account for roughly 70% of filings, and a large share of cases come from repeat plaintiffs represented by a small group of law firms. Our accessibility lawsuit tracker maintains the full dataset by year, state, and industry.
Formal lawsuits are only part of the picture. Thousands of demand lettersare sent each year that never appear in court statistics: a letter asserts your site violates the ADA (often attaching an automated scan), demands a settlement payment and remediation, and threatens suit. Because ADA Title III offers prevailing plaintiffs attorney's fees — and state laws like California's Unruh Act add statutory damages — settling is usually cheaper than litigating, which sustains the volume.
Defense costs, settlement ranges, and total exposure are covered in detail in our ADA website lawsuit cost guide. To gauge your own exposure, try our free ADA compliance risk checker.
WCAG: The De Facto Standard for ADA Compliance
The Web Content Accessibility Guidelines are not a law, but they are the measuring stick every serious actor uses. The DOJ codified WCAG 2.1 AA in the Title II rule and has required WCAG conformance in Title III settlement agreements for years. Courts reference WCAG when framing injunctive relief, expert witnesses audit against it, and essentially every private settlement specifies WCAG 2.1 or 2.2 Level AA as the remediation target.
For teams starting out: learn the framework in our WCAG guide and work through the WCAG 2.2 checklist. Targeting 2.2 AA satisfies every 2.1 AA obligation while covering the current version of the standard.
Practical Steps Toward ADA Website Compliance
- Audit against WCAG 2.1/2.2 AA. Combine automated scanning with manual and assistive-technology testing — automated tools alone catch only a fraction of issues. A professional accessibility audit gives you a defensible baseline.
- Prioritize by user impact and legal exposure. Fix blockers first: keyboard traps, missing form labels, inaccessible checkout and navigation, missing alt text on functional images. These are the failures demand letters cite most.
- Remediate the code, not the symptoms. Skip overlay widgets — they do not confer compliance and appear frequently in lawsuits. Fix templates, components, and content at the source.
- Publish an accessibility statement with a working feedback channel, and actually respond to reports. Documented responsiveness matters in negotiations and in court.
- Build accessibility into your process. Add automated checks to CI, test new features before release, train designers and developers, and re-audit periodically. Compliance is a practice, not a milestone.
- Keep records. Audit reports, remediation tickets, and testing logs demonstrate good-faith, ongoing effort — often the difference between a quick resolution and an expensive one.
Frequently Asked Questions
Is WCAG legally required under the ADA?
It depends on which title of the ADA covers you. For state and local governments (Title II), yes: the DOJ's 2024 web accessibility rule explicitly requires WCAG 2.1 Level AA for websites and mobile apps, on a tiered timeline based on population size. For private businesses (Title III), no regulation formally names WCAG — but courts, the DOJ, and virtually every settlement agreement use WCAG as the benchmark for whether a website is accessible. In practice, WCAG conformance is how ADA website compliance is measured everywhere.
What WCAG level does the ADA require?
The DOJ Title II rule requires WCAG 2.1 Level AA. For Title III (private businesses), settlements and consent decrees overwhelmingly specify Level AA as well — Level A alone is almost never accepted as sufficient, and Level AAA is not expected. Many organizations now target WCAG 2.2 Level AA, the current version of the standard, since it includes everything in 2.1 AA plus additional criteria and future-proofs remediation work.
Does the ADA apply to small business websites?
Generally yes. ADA Title III applies to businesses open to the public regardless of size — there is no small-business exemption comparable to the employment provisions of Title I (which only apply at 15+ employees). Small e-commerce shops, restaurants, medical practices, and local service businesses are regularly named in website accessibility lawsuits and demand letters. Small businesses may have more flexibility in arguing that specific fixes are not 'readily achievable,' but that is a case-by-case defense, not an exemption.
Who can sue over an inaccessible website?
Any person with a disability who encounters barriers on a covered website can sue under ADA Title III, and the DOJ can also bring enforcement actions. Title III plaintiffs can obtain injunctive relief (an order to fix the site) and attorney's fees, but not damages — which is why many suits are filed in states like California and New York, where state civil rights laws (the Unruh Act, the NY Human Rights Laws) add statutory damages on top of ADA claims. A large share of filings come from a relatively small group of repeat plaintiffs and law firms.
What is the difference between ADA Title II and Title III for websites?
Title II covers state and local government entities — cities, counties, public schools, transit agencies, courts — and now has a formal DOJ regulation requiring WCAG 2.1 AA for web content and mobile apps, with fixed compliance deadlines. Title III covers private businesses open to the public — stores, restaurants, banks, hotels, healthcare providers — and has no formal web regulation; instead, courts apply the ADA's general nondiscrimination requirements to websites, using WCAG as the practical measuring stick.
What should I do if I receive an ADA website demand letter?
Do not ignore it — unanswered demand letters routinely become lawsuits. Involve counsel experienced in ADA digital accessibility, preserve evidence of your site's current state, and get an independent audit so you know your actual exposure rather than relying on the letter's claims. Most demand letters settle for a monetary payment plus a remediation commitment; the remediation is usually the more expensive and more important part. Fixing the site is also what prevents the follow-on lawsuit from the next plaintiff.
Do accessibility overlays or widgets make a website ADA compliant?
No. Overlay widgets do not reliably fix underlying WCAG failures, and sites using overlays are sued regularly — in recent years roughly a fifth of website accessibility lawsuits have targeted sites that already had an overlay installed. Courts and the FTC have both rejected overlay marketing claims. Durable protection comes from remediating the site's actual code and content to WCAG 2.1/2.2 AA and maintaining it with ongoing testing.
Has the ADA Title II web deadline changed?
Yes. The original 2024 rule set compliance dates of April 2026 for public entities serving populations of 50,000 or more and April 2027 for smaller entities. In April 2026, the DOJ issued an Interim Final Rule extending each deadline by one year — to April 26, 2027 and April 26, 2028 respectively. The WCAG 2.1 AA standard, the rule's scope, and its exceptions are unchanged; only the dates moved. The separate HHS Section 504 web rule for healthcare entities was not extended.
Educational Content — Not Legal Advice
This page is provided for general educational purposes only and does not constitute legal advice. ADA case law varies by circuit and changes over time, and regulations and deadlines can be amended. For advice about your specific situation, consult an attorney experienced in digital accessibility law.
Essential Accessibility Resources
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences