ADA Title III compliance for websites.

Title III of the Americans with Disabilities Act of 1990 (42 U.S.C. §§ 12181-12189) prohibits discrimination on the basis of disability in "places of public accommodation" operated by private entities. The Act lists 12 categories of public accommodation — retail, hotels, restaurants, theaters, museums, professional offices, and others — covering essentially every consumer-facing private business in the US.

Title III predates the modern web. Its application to websites has been litigated extensively since the early 2000s. The dominant US federal court position today: commercial websites are places of public accommodation under Title III if they offer goods and services to the public, regardless of whether a physical location exists.

The US Department of Justice has consistently — including in its March 2022 web accessibility guidance — pointed to the Web Content Accessibility Guidelines (WCAG) as the de-facto technical standard for Title III conformance. DOJ has not formally adopted WCAG by regulation for Title III private entities, but:

• Virtually every Title III consent decree and settlement in 2020-2024 references WCAG (typically 2.0 or 2.1 Level AA).
• The April 2024 DOJ rulemaking for Title II (public entities) explicitly adopted WCAG 2.1 Level AA — a strong signal for Title III interpretation.
• Federal courts in the Ninth, Eleventh, and Second Circuits have routinely cited WCAG AA as the operative standard.

Practical target: WCAG 2.2 Level AA (a superset of 2.0 and 2.1). Conforming to 2.2 AA satisfies every published settlement standard and aligns with the DOJ's direction of travel.

The typical ADA web case follows a predictable pattern:

1. Plaintiff scans the target site, either manually or with an automated tool, capturing WCAG violations.
2. Demand letter sent to the operator (or to the agency listed in the WHOIS / footer). Common asks: remediation timeline, statutory damages, plaintiff legal fees ($5K-$25K typical).
3. Filed lawsuit if the demand isn't resolved — typically in federal court, sometimes in state court under parallel state laws (California Unruh Act, New York State Human Rights Law).
4. Settlement in roughly 90% of cases, with negotiated remediation, monitoring, and fee payment.

Top filing jurisdictions: SDNY (Southern District of New York), EDNY, ND California, CD California. New York State has historically led in volume; California has led in plaintiff-friendly damages under the Unruh Act ($4,000 per violation statutory).

The top target sectors: e-commerce (~70% of filings), restaurants/hospitality, financial services, healthcare-adjacent (insurance, providers), and entertainment.

A common reaction to a demand letter is to install an "accessibility overlay" widget (accessiBe, UserWay, AudioEye, EqualWeb, Equally AI, and similar) that injects a JavaScript snippet promising automatic remediation. The legal track record is unfavorable:

• No federal court has held that an overlay alone constitutes Title III conformance.
• Public lawsuit trackers from UsableNet and Seyfarth Shaw show suits continuing to be filed and won against overlay-protected sites.
• The Overlay Fact Sheet (overlayfactsheet.com), signed by 900+ accessibility practitioners, argues overlays cannot reliably fix the most common WCAG failures and can introduce new accessibility barriers.
• DOJ's March 2022 web guidance specifically called out overlays as not sufficient on their own.

The practical defense is conformance to WCAG at the source code level, demonstrated through a dated audit trail. Overlays may have a place as a temporary stopgap; they are not a defense strategy.

The most effective Title III defensive posture combines four elements:

1. Conformance to WCAG 2.2 AA at the source level. Audit your site, prioritize critical and serious violations, ship fixes through normal engineering process.
2. Continuous, dated audit evidence. Run automated scans weekly or per-deploy; archive the PDF reports. The "ongoing remediation activity" standard is the bar plaintiffs settle around — a single annual audit is much weaker than a continuous record.
3. Accessibility statement publicly linked from the footer. Should declare your conformance target, current known limitations, the contact mechanism for accessibility feedback (typically an email), and the response-time commitment.
4. Responsive feedback channel. The accessibility statement's contact email must be monitored. Cases where the operator responded quickly and remediated specific reported issues settle far better than cases where the feedback went ignored.

If a demand letter arrives: do not respond directly. Engage ADA-defense counsel (specialists exist), preserve the site state at the time of the letter, run an immediate baseline audit, and let counsel handle written communications.

From AccessProof scans across thousands of US commercial sites, these are the highest-impact remediation priorities — ordered by frequency in actual Title III complaints:

1. Color contrast (WCAG 1.4.3) — the single most-cited violation. Light gray text, button copy, link colors.
2. Missing or generic alt text (WCAG 1.1.1) — especially on product images, icon buttons, banner graphics.
3. Unlabeled form inputs (WCAG 3.3.2) — checkout, contact, search, account.
4. Inaccessible modal dialogs (WCAG 2.1.2, 2.4.3) — quick-views, cart drawers, cookie banners.
5. Keyboard navigation failures (WCAG 2.1.1) — custom dropdowns, carousels, multi-step forms.
6. Heading hierarchy (WCAG 1.3.1) — pages without h1, skipped levels, decorative use of headings.
7. Link text (WCAG 2.4.4) — "click here", "read more" as link text.
8. Focus visibility (WCAG 2.4.7) — outline: none without a custom focus indicator.
9. Status messages (WCAG 4.1.3) — cart updates, form errors, toasts not announced.
10. Skip links (WCAG 2.4.1) — no skip-to-content, or hidden incorrectly.

An AccessProof scan flags each of these with the WCAG criterion and the offending element selector — drop the report into your engineering backlog and ship through normal sprint cadence.

In addition to federal ADA Title III, several state laws create parallel or stronger web accessibility obligations:

• California Unruh Civil Rights Act — provides $4,000 statutory damages per violation, plus attorney's fees. Has driven a significant portion of California ADA web filings.
• New York State Human Rights Law + NYC Human Rights Law — used in parallel with federal Title III in many SDNY/EDNY cases.
• Colorado HB21-1110 — explicit web accessibility obligation for state government and adjacent entities (overlaps with ADA Title II).
• Massachusetts — settlement history and AG enforcement.
• Illinois — civil rights and human rights frameworks applied to web.

The technical standard across these regimes converges on WCAG AA. A single WCAG 2.2 AA audit covers Title III and the major state law overlays.