California is the largest single source of lawsuits filed under Title III of the Americans with Disabilities Act, the section that applies to businesses open to the public. In 2024, plaintiffs filed 3,252 Title III cases in California out of 8,800 nationally, roughly 37 percent of every such case in the country. National filings eased slightly to 8,667 in 2025, with California, Florida, and New York again the top three.
The lead has moved around. New York overtook California in 2022 and held the top spot through 2023 before California reclaimed it. What has not changed is that a handful of states account for most of the national total, and California is reliably among them.
The reason is not that California businesses are less accessible than businesses elsewhere. It is a matter of how two laws interact.
The federal layer: the ADA
The ADA is a federal law, in force since 1990. Title III requires "places of public accommodation," which includes most retail stores, restaurants, offices, and service businesses, to be accessible to people with disabilities. That covers physical features like parking, entrances, restrooms, and counter heights.
Under federal law alone, a private plaintiff who wins an ADA case can get an injunction, meaning a court order to fix the barrier, plus attorney's fees. Federal law does not award money damages to the plaintiff.
The state layer: the Unruh Act
California's Unruh Civil Rights Act changes that math. Under state law, any violation of the ADA is automatically also a violation of the Unruh Act, and the Unruh Act provides statutory damages of at least $4,000 per occurrence, plus attorney's fees.
That combination, a federal standard plus automatic state damages, is what draws high-volume filers. A small number of plaintiffs and law firms file hundreds of suits per year, often over parking lot striping, signage, ramps, and website accessibility.
Websites are part of this
Courts have divided on exactly when a website counts as a place of public accommodation, but businesses with both a website and a physical location in California are regularly sued over sites that do not work with screen readers or keyboard navigation. The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA are the benchmark most settlements and court orders reference, even though no statute formally adopts them for private businesses.
What defenses exist
California has created some protections, mainly for physical-access claims. A business that has had its property inspected by a Certified Access Specialist (CASp) before a claim is filed may qualify for reduced statutory damages and a window to fix violations. Small businesses can qualify for further reductions in specific circumstances. These protections apply to construction-related claims, not website claims.
Which customer tasks should you check on your website?
Choose a task a customer needs to finish, such as finding the right location, asking about a service or booking an appointment. Use your own test environment for submissions, bookings and payments so the check does not create a real appointment, message or charge.
- Find the business. On a phone, locate the service, correct address, opening hours and a contact option. Increase the browser's text size and check that information and controls remain readable.
- Navigate without a mouse. Use Tab and Shift+Tab to reach the menu, service links and booking control. Check that focus stays visible, that the appropriate Enter or Space key activates controls, and that you can leave menus and dialogs.
- Understand the page without its pictures. With a screen reader, check whether headings, link names, image descriptions and control labels explain the task. Include people who use assistive technology when reviewing the result.
- Check the booking handoff. Follow the link into any third-party booking or payment service and repeat the navigation check. In a test environment, check field labels, instructions, error messages and the confirmation.
- Keep another route open. Make the contact method for reporting a barrier easy to find. Record what failed, assign someone to resolve it and repeat the same task after the change.
The DOJ's website guidance explains common barriers. W3C's Easy Checks gives more detailed starting checks. This checklist is not an ADA audit, legal determination, certification or full accessibility assessment. Passing it does not establish compliance, and an automated scan alone cannot show that a customer can finish a task.
What should you put in a fix log?
Record the page URL, customer task, device and input or assistive method, expected result, actual barrier, person responsible, next action and retest date. Use synthetic examples and omit customer personal details. Keep the same task when retesting so a closed ticket reflects a working journey.
The practical takeaway
Start with the customer journey on the site you already operate. A technical repair and a legal assessment answer different questions. Ask a provider to state what it will inspect, repair and retest, and what falls outside its scope. Keep the observed barrier and its resolution in the fix log.
