Every year, thousands of businesses — many of them small — receive demand letters or lawsuits claiming their websites are inaccessible to people with disabilities. The claims arise under Title III of the Americans with Disabilities Act and, in California, the Unruh Civil Rights Act, which adds statutory damages that make this state a center of accessibility litigation. This article explains how these claims work, what the technical standard really is, and the practical steps that reduce your risk.
The legal framework
Title III of the ADA prohibits discrimination on the basis of disability in "places of public accommodation" — restaurants, stores, hotels, professional offices, and most other businesses open to the public. The statute was written in 1990 and never mentions websites, so courts have had to decide how it applies online. In the Ninth Circuit (which includes California), the leading case is Robles v. Domino's Pizza: the ADA applies to the websites and apps of businesses with a nexus to a physical place of public accommodation, because the site connects customers to the goods and services of the physical location. Other circuits differ on whether a web-only business is covered, and the Supreme Court has declined to resolve the split, so exposure varies with geography — but a California business with any physical customer-facing presence should assume its website is covered.
California's Unruh Act (Civ. Code § 51) independently prohibits disability discrimination by business establishments and expressly incorporates ADA violations: a violation of the ADA is automatically a violation of Unruh. The difference is remedies. The ADA supports injunctive relief and attorney's fees; Unruh adds minimum statutory damages of $4,000 per occurrence. That damages hook is why so many web accessibility cases are filed in or target California.
What "accessible" means: WCAG
No federal regulation sets a binding technical standard for private-sector websites. In practice, courts, the Department of Justice, and settling parties all use the Web Content Accessibility Guidelines (WCAG), currently version 2.1 or 2.2 at Level AA, as the benchmark. Common failures alleged in complaints include:
- Images without alternative text, leaving screen-reader users no description
- Forms and buttons without proper labels, making checkout impossible
- Poor color contrast and text that cannot be resized
- Menus, carousels, and popups that cannot be operated by keyboard alone
- Videos without captions
- PDFs that screen readers cannot parse
These are the exact issues serial plaintiffs' testing tools flag, so they are also your remediation priority list.
How the claims typically unfold
Most matters start with a demand letter or a filed complaint from a plaintiff who has brought many similar cases, often describing an attempted visit to your site with a screen reader. California has procedural reforms for physical-access construction claims (such as reduced damages for timely corrections in some circumstances), but those protections are limited and do not reliably extend to website cases. Many defendants settle for a payment plus an agreement to remediate on a schedule, because defense costs alone exceed typical settlement value. That economic reality is frustrating, but it also means prevention is dramatically cheaper than response. If you receive a demand, do not ignore it and do not email the plaintiff admissions — preserve evidence of your site's state and get counsel involved early, as you would with any business litigation threat.
Reducing your risk
- Audit against WCAG 2.1/2.2 AA. Combine automated scanning with manual testing (keyboard-only navigation and a screen reader session). Automated tools catch only a fraction of issues.
- Fix the high-traffic paths first. Homepage, navigation, search, product pages, forms, and checkout. Plaintiffs plead the transaction they could not complete.
- Be careful with accessibility overlay widgets. Overlay toolbars marketed as one-line fixes have not stopped lawsuits and are themselves criticized in complaints. They are not a substitute for remediation of the underlying code.
- Post an accessibility statement with a working contact channel for users who encounter barriers, and actually route and answer those messages.
- Put accessibility in your vendor contracts. If an agency builds or maintains your site, require WCAG conformance and warranty language so the cost of defects does not land solely on you.
- Retest after redesigns. Accessibility regressions after a site refresh are a recurring source of repeat claims.
Accessibility work overlaps naturally with the rest of your website legal stack — privacy policies, terms of service, marketing disclosures — so it makes sense to fold it into a broader regulatory compliance review rather than treating it as a one-off scramble.
Talk to a California business attorney
Whether you want to get ahead of accessibility risk or you are already holding a demand letter, an early assessment of your exposure and options costs nothing to start. Schedule a free consultation or call (949) 418-2113.
This article is attorney advertising and provides general information only. It is not legal advice and does not create an attorney–client relationship. Facts matter; consult a lawyer about your specific situation.
