California web accessibility and the Unruh Act

The federal ADA lets a plaintiff win an injunction, meaning a court order to fix the site, plus legal fees. It does not award damages to the individual. That alone rarely justifies the cost of a case.

California adds the Unruh Civil Rights Act (Civil Code section 51). Unruh provides statutory damages with a minimum of $4,000 per violation, and critically, a violation of the ADA is automatically a violation of Unruh. So the same inaccessible website that would yield only an injunction federally carries a per-violation damages floor in California.

That single provision is why so many claims are filed there. It is a structural feature of the law, not a judgement about local web development.

This is the part that generates the most confusion, and the honest answer is that it is contested. Defendants argue a violation means one visit by one person. Plaintiffs have sometimes argued for counting separate barriers or separate visits, which multiplies the figure quickly.

You will see marketing that multiplies $4,000 by every failing element on your site to produce a terrifying number. Treat that as a sales tactic. The realistic exposure for most small and mid-sized businesses is a demand letter seeking a settlement in the low five figures plus a commitment to remediate, and most of these resolve without litigation.

None of this is legal advice, and if you have received a demand letter you should speak to a lawyer rather than a scanner vendor.

Neither the ADA nor Unruh names a technical standard for private businesses. In practice the benchmark is WCAG 2.1 or 2.2 at Level AA, which is what DOJ guidance references and what settlement agreements almost universally require. Targeting WCAG 2.2 AA also satisfies 2.1 AA, so it is the sensible aim.

California state agencies are a separate case with an explicit rule: AB 434 requires state agency websites to meet WCAG 2.0 Level AA and to post an accessibility certification. If you are a state entity rather than a business, that is your obligation.

Demand letters are remarkably repetitive, because they are usually generated from an automated scan of the homepage and a few key pages. The recurring items are:

• Text with insufficient colour contrast against its background
• Images with missing or unhelpful alt text
• Form inputs with no associated label
• Links and buttons with no accessible name
• Content that cannot be reached or operated with a keyboard

These are the machine-checkable failures, which is exactly why they appear so consistently: whoever sent the letter ran a scanner too. The practical implication is encouraging, because you can run the same check yourself and see most of what they would see.

Accessibility overlay widgets that promise instant compliance from one line of JavaScript do not fix your underlying markup, and they have themselves become a target. In 2026 the FTC fined accessiBe $1 million over its accessibility claims. Installing a widget does not remove the barriers a plaintiff would cite, and it can add a false claim of conformance to the record.

Fix issues in the code and content, then verify. There is no button for this.

Run the free scan above on your highest-traffic pages, not just the homepage, since that is where claims tend to look first. It runs axe-core against WCAG 2.2 A and AA, outlines each failing element, and maps it to the success criterion so you can hand the output to a developer.

Then fix at the source and keep evidence. Records of scans over time, fixes shipped and monitoring for regressions demonstrate ongoing effort, which matters considerably more than any one-off result. Automated testing covers the machine-checkable subset of WCAG and cannot tell you that you are compliant, so treat a clean scan as a floor rather than a finish line.