ADA Website Compliance

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.

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.

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

1. 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.
2. 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.
3. 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.
4. Publish an accessibility statement with a working feedback channel, and actually respond to reports. Documented responsiveness matters in negotiations and in court.
5. 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.
6. 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