The short version
- There is no federal regulation setting a technical accessibility standard for private business websites. The Justice Department rule that adopts WCAG 2.1 Level AA binds state and local government under Title II only.
- Whether an online-only business is covered at all depends on the circuit. The First, Second and Seventh read "public accommodation" beyond physical places; the Third, Sixth and Ninth require a nexus to premises.
- A private claimant under Title III gets an injunction and, at the court's discretion, legal fees — not damages. The fee exposure, not the merits, is what makes these demands settle.
- An accessibility overlay is not a defence. In January 2025 the FTC ordered the largest overlay vendor to pay $1 million and barred it from claiming its product makes a website WCAG-compliant.
Most pages on this subject close the gap between what is written down and what decides cases by asserting a rule. There is no rule. There is a statute from 1990, a set of voluntary technical guidelines, and thirty years of courts joining the two together case by case.
The rule everybody quotes was not written for you
In April 2024 the Department of Justice issued a regulation adopting WCAG 2.1 Level AA as the technical standard for web content and mobile apps. It was made under Title II, which covers state and local government. In April 2026 the Department pushed the compliance dates back a year: 26 April 2027 for public entities serving 50,000 people or more, and 26 April 2028 for smaller entities and special districts.
None of that reaches a shop, a SaaS product or a restaurant. Private businesses fall under Title III, and there is no Title III web regulation at all. The Department's published position is that the ADA applies to the goods and services a public accommodation offers online, but that businesses have "flexibility in how they comply", with WCAG offered as helpful guidance rather than a standard. A Title III rulemaking has sat on the regulatory agenda for years with no proposed rule.
Sixteen years of nearly making a rule
2010
Advance notice
DOJ asks for comment on web rules under both Title II and Title III.
2017
Title III withdrawn
The private-business rulemaking is formally pulled. Nothing replaces it.
2022
Guidance, not a standard
DOJ publishes web guidance saying the ADA applies online and businesses may choose how.
2024
Title II rule
WCAG 2.1 AA becomes binding for state and local government. Dates later moved to 2027 and 2028.
Is a website a place of public accommodation?
Title III applies to a "place of public accommodation", and the statute lists physical categories — inns, restaurants, shops, professional offices. Whether that list can hold something with no address has divided the federal appeals courts since the mid-1990s.
The First, Second and Seventh Circuits have read the phrase as not limited to physical structures, following Carparts Distribution Center v. Automotive Wholesalers' Association (1st Cir. 1994). The Third, Sixth and Ninth require a connection to premises; the Ninth put the nexus test most plainly in Robles v. Domino's Pizza (2019), holding the statute applies to the services of a place of public accommodation, not the services in a place. An Eleventh Circuit panel held in 2021 that websites are not places of public accommodation, but the court vacated that opinion as moot the same year, so it binds nobody.
The question that decides whether the split matters to you
Does the public visit premises that your website supports?
Yes — shop, clinic, office, restaurant
Covered everywhere. The nexus test is satisfied on the facts, so the coverage argument is not worth running.
No — online only
Coverage depends on the circuit, and the claimant picks the court. A venue question, not a shield.
WCAG is not the law, and it is the standard anyway
Because no technical standard exists for Title III, courts reach for the one that already exists. WCAG 2.0 and 2.1 at Level AA appear routinely in consent decrees, settlements and remedial orders — as the measure of the fix, not the definition of the violation. That distinction is real but narrow: you do not defend a claim by proving conformance to a rule, you defend it by showing the person could use the service. The target written into the settlement is WCAG AA either way.
On versions: WCAG 2.2 is the current W3C Recommendation and is backwards compatible, so content conforming to 2.2 also conforms to 2.1 and 2.0. Building to 2.2 Level AA therefore satisfies a 2.1 AA target and costs nothing extra to specify. WCAG 3.0 is a separate multi-year project, not something to wait for.
Where the accessibility statement sits
An accessibility statement belongs alongside your terms and privacy pages. The website terms of use template shows the block those pages normally occupy.
The remedy is what makes the letter work
This explains the volume of the litigation better than any argument about coverage. Under 42 U.S.C. § 12188 a private claimant under Title III gets injunctive relief; monetary damages are available only where the Attorney General brings the action. Separately, § 12205 lets a court, in its discretion, award reasonable legal fees to a prevailing party.
So the recoverable money in a private website case is fees. The claimant wants a prompt settlement covering them plus a commitment to remediate; you want to avoid a defence bill that exceeds that figure long before anyone reaches the merits. Both sides know this on day one, which is why most demands never become filed cases. The number in the letter is calibrated to the cost of arguing, not to the harm.
California is the exception that proves the mechanism. Civil Code § 52 sets statutory damages of no less than $4,000 for an Unruh Civil Rights Act violation, and an ADA violation is a violation of Unruh. That converts an injunction-only federal claim into a damages claim, which is why California website cases are typically brought in state court.
The overlay is not a defence, and it is becoming evidence
Accessibility overlays — a line of JavaScript loading a widget that promises to correct a site at runtime — are sold precisely to businesses that have received one of these letters. In January 2025 the Federal Trade Commission announced an order requiring the largest vendor, accessiBe, to pay $1 million over claims that its product could make a website conform to WCAG 2.1 Level AA. The FTC alleged the widget failed on basic components including navigation menus, form fields and image descriptions, and that paid reviews had been presented as independent opinion. The order bars it from representing that an automated product makes a site WCAG-compliant without competent and reliable evidence.
The practical point is narrower than the headline. An overlay sits on top of the page; the barriers stay in the markup underneath, where a screen reader meets them. Running one is also a dated record that you knew accessibility was an issue and chose the cheapest response, which is why complaints have started naming the widget rather than ignoring it. Buy remediation as work on the codebase, and put the conformance target in the service agreement.
What to do when a letter arrives
Cheapest response first
- Days of dev time
Fix the named pages
The letter names specific barriers on specific URLs. Fixing those removes the relief being asked for, and costs less than the first hour of argument.
- Low
Reply with a dated plan
A written schedule and a published accessibility statement move the negotiation from whether you will fix it to when. Silence invites a filing.
- Nuisance value
Negotiate the fee figure
The recoverable interest is legal fees. Most demands resolve here, below the cost of preparing a motion to dismiss.
- High
Test standing and coverage
Intent to return, tester status, or no physical nexus in a nexus circuit. Genuine defences that cost more than the typical demand.
Only the first rung changes your position permanently. The rest buy time on a site that still cannot be used.
Do not send an admission of non-conformance in an unguarded email, and take advice before replying substantively if the letter comes from a firm that files. Accessibility also sits with the rest of your published obligations: the legal pages a site actually needs and whether your terms bind anyone are worth reviewing at the same time, because the same neglected footer usually holds all three.
The barriers that appear in almost every complaint
These letters are generated from automated scans, so the same findings recur. Clearing this list will not make a site conformant, but it removes most of what a scan reports.
A first pass before you commission an audit
- Informative images have alt text; decorative ones have empty alt attributes rather than filenames.
- Every form field has a programmatically associated label, and errors are announced, not just coloured.
- The site works by keyboard alone, with a visible focus indicator and no traps in modals.
- Text contrast meets the AA ratio, including placeholders, disabled states and text over images.
- Headings are real heading elements in order, and buttons are buttons rather than styled divs.
- Checkout and account flows are tested end to end with a screen reader, not just the home page.
The last item matters most and is skipped most often. Demands cluster on transactional flows, because that is where an inaccessible page stops being an inconvenience and becomes a denial of the service itself. A site whose terms of service and privacy policy are immaculate but whose checkout cannot be completed without a mouse has solved the visible problem and left the expensive one alone.
The uncomfortable conclusion is that the absence of a rule sustains the litigation. If a regulation existed, conformance would be a defence and the demands would mostly stop. Until one does, the only durable position is a site people can actually use — and the businesses that get a second letter are the ones that paid the first and changed nothing.
Sources
- DOJ — Title II web accessibility rule (WCAG 2.1 AA) and compliance dates
- DOJ — Guidance on Web Accessibility and the ADA
- CRS — The ADA and Public Accommodations in Web Services (R48104)
- 42 U.S.C. § 12188 (Title III enforcement and remedies) — Cornell LII
- California Civil Code § 52 (Unruh Act damages) — Legislative Information
- FTC $1m order against accessiBe over WCAG compliance claims — summary
- European Commission — European Accessibility Act (covers e-commerce)
General information, not legal advice. This guide explains how these documents and rules generally work. Law varies by jurisdiction and changes, and none of it is applied to your circumstances here. For anything consequential, consult a licensed attorney where you are.
Frequently asked
Does my small business website have to be ADA compliant?
There is no federal regulation setting an accessibility standard for private business websites, so "compliant" has no fixed technical meaning under Title III. The Justice Department maintains that the ADA covers the services a public accommodation offers online. Small size is not an exemption; the ADA has no employee-count or revenue threshold for Title III, unlike the employment provisions in Title I.
Is a website a place of public accommodation under the ADA?
The federal appeals courts disagree. The First, Second and Seventh Circuits have read "public accommodation" as reaching beyond physical structures. The Third, Sixth and Ninth require a nexus between the website and physical premises. A business with a shop or office is effectively covered everywhere, because the nexus is satisfied on the facts. For an online-only business the answer depends on where the case is filed.
Is WCAG 2.1 AA legally required for a business website?
Not by regulation. WCAG 2.1 Level AA is binding on state and local government web content under the 2024 Title II rule, with compliance dates in 2027 and 2028. For private businesses it functions as the standard courts and settlements adopt to define an adequate fix. Building to WCAG 2.2 Level AA covers a 2.1 target, because the later version is backwards compatible.
Do accessibility overlay widgets prevent lawsuits?
No. An overlay runs on top of a page and leaves the underlying barriers in the markup, where assistive technology meets them. In January 2025 the FTC ordered the largest vendor to pay $1 million and barred it from claiming its automated product makes websites conform to WCAG. Installing one also documents that the business was aware of the issue and chose a superficial response.
How much do website accessibility demand letters usually settle for?
There is no published tariff, and any figure quoted as typical is guesswork. The economics are what matter: a private ADA claim recovers no damages, only an injunction and possibly legal fees, so the demand is generally set below what defending would cost. In California an Unruh Act claim adds statutory damages of at least $4,000 per violation, which shifts the arithmetic considerably.