Rules
Digital product accessibility: ADA and state laws for US sellers
US digital product sellers face ADA Title III, WCAG 2.1 AA, California and New York claims, plus a compliant statement, record keeping and enforcement outcomes.
What to take away
- The ADA does not name a web standard, but the Department of Justice reads Title III to cover storefronts of public accommodations.
- WCAG 2.1 Level AA is the benchmark US courts and agencies use when they measure a site.
- California and New York add state statutes and city rules that raise the odds of a complaint.
- A compliant statement names the standard, the conformance level, a contact route and the last audit date.
- An unanswered demand letter can become a consent decree that governs the site for years.
Who holds jurisdiction over a US storefront
Federal enforcement sits with the Department of Justice, which applies Title III of the ADA. The statute lists places of public accommodation and says nothing about websites.
ADA vs Section 508 duties
ADA Title III
- Who enforces
- DOJ
- Who is bound
- Public accommodations
- Technical standard
- None named
- Trigger
- Physical store link
Section 508
- Who enforces
- Federal agencies
- Who is bound
- Agencies and vendors
- Technical standard
- WCAG criteria
- Trigger
- Federal contract
DOJ guidance closes that gap: a site counts as an extension of the physical store when the two are connected. Read the department's position on DOJ guidance on web accessibility before you argue a purely online shop falls outside the rule.
Section 508 sets a separate duty. It binds federal agencies and the vendors that sell to them, and it points to the same technical criteria used in WCAG. Sell digital products to a federal buyer and the contract carries that standard with it. The Section 508 laws and policies page lists the obligations that flow down to contractors.
What a compliant disclosure contains
An accessibility statement is the first document a plaintiff's attorney reads. It should be plain, current and specific. The plan for fixes belongs with the rest of your digital product strategy, because remediation competes with every other item on the roadmap.
Accessibility statement contents
- Standard tested, by version and level
- Conformance level claimed, gaps listed
- Contact route plus response window
- Last audit date and next audit date
- Process followed when a request arrives
The W3C WCAG standards define the criteria behind every claim you make. A statement that cites a standard you have not tested against is worse than no statement, because it is easy to disprove.
Example: California and New York against the federal floor
California and New York against the federal floor
Instrument
- Federal
- ADA Title III
- California
- Unruh Civil Rights Act
- California
- State web accessibility policy
- New York
- State Human Rights Law
- New York
- New York City Human Rights Law
What it adds for a seller
- Federal
- Coverage with no named technical standard
- California
- Statutory damages and plaintiff attorney fees
- California
- Procurement pressure on vendors to declare conformance
- New York
- A parallel claim that can be filed in state court
- New York
- A city route with its own damages provision
California matters because the Unruh Act lets a plaintiff recover damages without proving intent, and it shifts attorney fees. A barrier that stops a checkout is a conversion problem before it is a legal one, which is why digital product funnels work and accessibility reviews belong in the same pass.
Federal floor vs state adds
Federal
- Instrument
- ADA Title III
- Damages
- None named
- Attorney fees
- Not shifted
- Extra route
- DOJ enforcement
California
- Instrument
- Unruh Act
- Damages
- Statutory damages
- Attorney fees
- Shifted to plaintiff
- Extra route
- State procurement policy
New York
- Instrument
- Human Rights Law
- Damages
- State court claim
- Attorney fees
- Parallel claim route
- Extra route
- NYC Human Rights Law
New York allows parallel claims in state court, and the city human rights law adds a second route. A seller registered in both states faces two complaint channels and one remediation plan.
Records to keep
Keep the audit report, the ticket list and the dates fixes shipped. A vendor's accessibility conformance report, usually called a VPAT, belongs in the same folder. So does any training record for the staff who publish product pages.
These files matter for two reasons. They show good-faith effort if a complaint arrives, and they tell you what still needs work. A compliance file is also what a buyer asks for during vendor review, so the same folder does double duty. Dates matter more than descriptions, because they show the fix came before the complaint.
A dated log of barriers found and closed is the cheapest evidence you will hold, and the habit of recording what changed is the same one that makes digital product analytics worth reading.
What happens when a seller ignores the standard
Three outcomes are common. The DOJ can investigate and negotiate a settlement. A private plaintiff can sue under the ADA and add state claims in California or New York. A customer complaint can also reach a state attorney general, and several states act without waiting for a federal case.
A consent decree typically sets a conformance deadline, names an independent auditor, and keeps the court supervising the site for several years.
The 2008 settlement in National Federation of the Blind v. Target, litigated in California, became the template. Target agreed to make its site usable with screen readers, to fund accessibility work and to accept monitoring. Domino's Pizza appealed a similar ruling to the Supreme Court in 2019, which declined to hear the case and left the Ninth Circuit decision standing.
