If customers can walk into your business, courts in California have held that the Americans with Disabilities Act reaches the website tied to it. California's Unruh Civil Rights Act then treats an ADA violation as a state violation too, with a floor of $4,000 in damages per offense plus attorney's fees. No regulation tells a private business exactly what a compliant site looks like, so plaintiffs, defense lawyers and judges all end up measuring against the same private standard: the Web Content Accessibility Guidelines, known as WCAG, at level AA.

A business that sells only online is in a different spot since a 2022 appeals ruling, and a service company with a shop nobody visits sits somewhere between the two. Both situations are covered below, along with what an overlay widget can and can't do for you.

This is not legal advice. We build websites; we aren't lawyers. If a demand letter or a lawsuit has already arrived, take it to an attorney who defends disability access claims before you reply.

What the ADA says about websites

The ADA became law in 1990. Title III, the part that applies to private businesses, bans disability discrimination in "places of public accommodation," and the statute's list of those places is a list of physical ones: restaurants, stores, offices and the like. Websites aren't mentioned anywhere in the text.

The Department of Justice has filled some of that silence with opinion rather than rules. Its March 2022 guidance says the agency "has consistently taken the position" that the ADA covers the web content of businesses open to the public, and it points owners to WCAG as helpful guidance. The same page states that the guidance has no legally binding effect. There is still no federal regulation that hands a private business a technical checklist for its website.

One more piece of federal law shapes everything that follows. A private person who sues under Title III can win a court order requiring the business to fix the barrier, plus attorney's fees, but not money damages. Hold on to that, because it's the gap California fills.

Robles v. Domino's, the case that governs here

San Diego is in the Ninth Circuit, so the federal decision that matters most locally is Robles v. Domino's Pizza, decided January 15, 2019. Guillermo Robles, who is blind, alleged that he couldn't order a pizza through Domino's website or app using screen-reading software, and he sued under both the ADA and the Unruh Act.

The court let his case go forward. Customers use the site and app to find a nearby restaurant and order for delivery or pickup, it reasoned, so an inaccessible site blocks access to the goods of physical restaurants, which the ADA does cover. The court called that link between the website and the stores "critical to our analysis." It rejected Domino's argument that holding it liable without federal web rules would violate due process, and it said a trial court could order the company to meet WCAG 2.0 as a remedy if the site turned out to violate the ADA. It expressly declined to decide whether the site complied. Domino's asked the Supreme Court to step in, and the Court declined on October 7, 2019.

Two ideas from Robles carry straight over to a small business. The hook is the physical location: your website matters under the ADA because it's a door into a business people can visit. And WCAG wasn't turned into law. The court treated it as a likely description of the fix, which is how it has been used ever since.

Why California adds a price tag: the Unruh Civil Rights Act

California's Civil Code section 51 guarantees equal access to "business establishments of every kind whatsoever," and subdivision (f) says a violation of anyone's rights under the ADA "shall also constitute a violation of this section." Every ADA website claim is therefore an Unruh claim as well.

Section 52 supplies the money the federal law leaves out. Whoever violates section 51 is liable "for each and every offense" for actual damages, up to three times that amount, "but in no case less than four thousand dollars ($4,000)," plus attorney's fees set by the court. Because the floor attaches to each offense rather than to the lawsuit, a plaintiff may try to count every failed visit separately, though the trial judge in the Midvale case below treated repeat visits to the same site as a single offense.

The California Supreme Court closed the last obvious defense in Munson v. Del Taco (2009). When an Unruh claim is built on an ADA violation, the plaintiff doesn't have to prove the business meant to discriminate. An owner who never knew the contact form was unreadable to a screen reader gets no credit for not knowing.

The combination

Federal law supplies the rule and a repair order. State law adds a minimum payment per offense, and both let a winning plaintiff recover legal fees. That's why Robles paired the two statutes, and why each California case below is an Unruh claim that leans on the ADA.

What California's appeals courts have decided

Three published Court of Appeal decisions do most of the work in state court. Read them together and the line runs between businesses with a physical place and businesses without one.

Thurston v. Midvale Corp.2019 · Second District

A blind woman couldn't use a restaurant's website with her screen reader. The court held the site was covered by the ADA, and so by Unruh, because it connected customers to the restaurant. It upheld an order requiring the site to meet WCAG 2.0 AA, while noting that liability rested on the site being inaccessible, not on WCAG itself being law.

Have a storefront, dining room or office customers visit? Your site is in scope.

Thurston v. Omni Hotels Management Corp.2021 · Fourth District

The same plaintiff sued a hotel operator over its booking site. The court said she didn't need to be a customer, but she did need a bona fide intent to use the hotel's services, which here meant genuinely wanting to book a room. The jury found she hadn't shown one, and the court affirmed.

Whether the visitor meant to buy anything is a real question in these cases, and one for your lawyer to raise.

Martinez v. Cot'n Wash, Inc.2022 · Second District

A retailer that sold only online was not a "place of public accommodation" under the ADA, the court held. Without an ADA violation to borrow, the Unruh claim needed proof of intentional discrimination, and running an inaccessible site, even after being told about the problem, wasn't enough on its own. The California Supreme Court declined to review the decision that November.

Online-only sellers face a harder case against them in California state court. Harder is not the same as none.

Sources: the Midvale opinion, the Omni opinion and the Cot'n Wash opinion, with the review denial reported by Buchalter.

Cot'n Wash is a California state court decision. It doesn't bind a federal judge in another state, and some federal courts elsewhere haven't required any physical location at all. An online shop that ships nationwide can't treat it as the last word.

Where a service business with no storefront fits

Plenty of San Diego businesses sit between those rulings: a plumber whose yard customers never see, a detailer who works out of a van, a pool route run from a home office. The cases above involved a restaurant, a hotel company and an online retailer. None of them decided whether a business that only meets customers at the customer's own property counts as a place of public accommodation.

If that describes you, it's a question for a lawyer, and the safer working assumption until you have an answer is that your site will be measured with the same WCAG yardstick as everyone else's.

The Legislature keeps returning to it

Bills to change these rules come up regularly. One recent bill, AB 2190, would have given businesses a defense against statutory damages in some situations and changed how intent is proven under Unruh. It cleared three Assembly committees, and on May 21, 2026 its author moved it to the inactive file. Something similar may return, so check the current law before relying on any summary, including this one.

What "compliant" means when no rule defines it

WCAG is published by the World Wide Web Consortium, or W3C. It breaks accessibility into testable success criteria, each assigned a level: A, AA or AAA. Level AA is the level California courts have ordered and the level the federal government picked when it finally wrote an ADA web rule for state and local governments.

WCAG 2.2 became a W3C Recommendation on October 5, 2023. It adds nine success criteria to 2.1 and removes one, 4.1.1 Parsing, which W3C now calls obsolete. Otherwise the 2.0 and 2.1 criteria carry into 2.2 essentially unchanged. In practice, a site built to 2.2 AA meets what the older versions ask for, apart from that single retired criterion.

The 2024 federal rule is for governments

In April 2024 the Department of Justice published a rule under Title II making WCAG 2.1 AA the technical standard for websites and mobile apps run by state and local governments, special purpose districts, Amtrak and commuter authorities. It does not apply to private businesses. A company is pulled in only when it does the government's work, because public agencies must make sure their contractors follow Title II too.

The original deadlines were pushed back by an interim final rule on April 20, 2026. According to ADA.gov, governments serving 50,000 people or more now have until April 26, 2027, and smaller ones and special districts until April 26, 2028. For a café or a contractor, the rule matters for a different reason: it shows which yardstick the federal government chose once it actually wrote one down under the ADA.

Why an overlay widget won't settle it

Overlays are scripts that sit on top of a finished site and try to adjust the page in the visitor's browser, usually behind a small icon in a corner. They're sold as a quick route to compliance, and the federal government has weighed in on that pitch.

In April 2025 the Federal Trade Commission finalized an order requiring accessiBe, maker of the accessWidget plug-in, to pay $1 million. The FTC alleged that the company's claim that its tool could make any website compliant with WCAG was false, misleading or unsubstantiated, and that it formatted third-party reviews and articles to look like independent opinions without disclosing its connections to them. The order bars accessiBe from claiming its automated products can make any site WCAG compliant, or keep it compliant over time, without evidence to back that up.

The W3C's own position points the same way: no tool alone can determine whether a site meets accessibility standards, and a knowledgeable person has to evaluate it. The durable fixes live in the page's own markup, where a form field has a real label, a photo has a description written by someone who knows what it shows, and headings follow an order a screen reader can navigate. That's one reason we hand-code sites rather than assemble them: when a check fails, the fix is an edit to the page itself, not another layer on top of it.

A website accessibility check you can run yourself

A first pass needs no budget and no developer. Use a laptop with an up-to-date browser and your phone, keep a note open, and write down what fails as you go. Start with three pages: the homepage, the page where people contact or book you, and the service page that brings in the most calls.

Put the mouse awayWCAG 2.1.1, 2.1.2, 2.4.7, 2.4.11

Click once in the address bar, then press Tab over and over. Every link, button, menu and form field should take a visible outline as you reach it, in an order that follows the page. Enter should follow a link, and the space bar should tick a checkbox.

Failures to look for: the outline disappears, a menu only opens on hover, a pop-up you can't leave without the mouse, or a sticky header that covers the item you've just tabbed to.

Check the contrastWCAG 1.4.3

Paste your text and background colors into the free WebAIM Contrast Checker. Ordinary text needs a ratio of at least 4.5:1, and large text 3:1.

The usual offenders are pale gray fine print, white lettering over a photo, and light placeholder text inside form fields.

Describe your imagesWCAG 1.1.1

Run the page through WAVE, a free checker from the same group, or right-click an image and choose Inspect to read its alt text. A photo that tells the visitor something needs a short description of what it shows. A purely decorative one should have an empty alt so screen readers skip it, and the logo's should be your business name.

Watch for a menu, price list or flyer uploaded only as a picture. A screen reader can't read the words inside it, so the same text needs to be on the page.

Test the formsWCAG 1.3.1, 3.3.1, 3.3.2, 3.3.3

Click the words next to each field. If the cursor jumps into the field, the label is wired up properly. If nothing happens, a screen reader probably can't tell what the box is for.

Labels that exist only as gray text inside the box vanish once someone starts typing. Then submit the form with a mistake on purpose: the error message should name the field and say what to change.

Caption the videoWCAG 1.2.2

Any recorded video with speech needs captions, including clips embedded from YouTube or Instagram. Automatic captions often get names, street names and trade terms wrong, so watch them through once and correct them before you rely on them.

Zoom in hardWCAG 1.4.4, 1.4.10

Press Ctrl and plus (Command and plus on a Mac) until the browser reads 200%. Text should grow without overlapping, getting clipped or hiding buttons.

Then make the window about 1280 pixels wide and zoom to 400%. W3C treats that as a 320-pixel-wide screen, and the page should rearrange itself so it scrolls only up and down, with nothing cut off.

Read the basicsWCAG 2.4.2, 3.1.1, 2.5.8

Each browser tab should name its page in words a stranger would understand. View the page source and confirm the opening html tag declares a language, such as lang="en".

On your phone, buttons and menu links should be at least 24 by 24 CSS pixels, or sit far enough from their neighbors to make up the difference.

Listen to itThe whole page

Turn on the screen reader built into your phone and try to do one real job: find your phone number, or send the contact form. Learn the on and off gesture first, because the phone behaves differently while it's running.

Finally, run WAVE on the same three pages. It will catch things a person misses and raise a few false alarms of its own. Treat its report as a list to review rather than a verdict, for the reason W3C gives above.

Turning the findings into fixes

Some failures cost more than others, so sort the list before anyone starts editing:

  1. Anything that blocks contact or payment. A booking widget you can't tab through or a form with unlabeled fields stops a customer cold, and it's the easiest kind of barrier for a complaint to describe.
  2. Navigation. Menus, the mobile menu button and links in the header and footer, because every other page depends on them.
  3. Content. Missing image descriptions, low-contrast text, uncaptioned video and image-only menus.

As the work happens, keep a dated log of what you tested, what failed, who fixed it and when. Retest with the same steps afterward, not just the automated checker.

It also helps to publish a short accessibility page with a phone number and an email address for anyone who runs into a problem, then answer what arrives. Describe the standard you're working toward and how to reach you. Leave out phrases like "fully ADA compliant," which no honest owner can promise and which a plaintiff's lawyer will happily test.

Accessibility also drifts. A new booking tool, a chat bubble, a redesigned header or a video added by a well-meaning employee can undo a clean result in an afternoon. Third-party tools embedded on your pages are part of what a visitor has to use, so test them too and ask the vendor which WCAG level they meet. Repeat the check whenever something like that goes live.

If a demand letter arrives

Don't ignore it, and don't answer it yourself. Send it to a lawyer, note any deadline it sets, and save a copy of the site as it looked on the dates the letter mentions. Installing an overlay the next morning isn't a response, for the reasons the FTC laid out.

How we handle it on the sites we build

Every site we make is written by hand, with no WordPress and no page builders, so each tag these checks look at is one we wrote and can change directly. Nobody can honestly promise that a site will never draw a complaint, and we won't either. WCAG has dozens of success criteria, content changes after launch, and courts decide what the ADA requires one case at a time.

What we can offer is a site where those fixes are ordinary edits. On our Starter plan, $99 a month, the two hours of edits included each month can go toward exactly this kind of work: rewriting alt text, relabeling a form, darkening a color that fails contrast. If your current site runs on a theme and a stack of plugins, some failures will trace back to code you don't control, and a rebuild is sometimes the cleaner answer. Our San Diego web design page explains how we build, and pricing lists every plan, including a one-time build if you'd rather pay for the site once.

Questions owners ask about ADA website compliance

Does the ADA cover my website if I don't have a storefront?

It depends on what you have instead. For a retailer that sells only online, a California appeals court held in Martinez v. Cot'n Wash (2022) that the business is not a place of public accommodation under the ADA. A business with a shop, office or dining room that customers visit is covered under Robles v. Domino's and Thurston v. Midvale. A service business that only meets customers at their own homes falls between those decisions, so ask a lawyer and plan as if your site will be judged against WCAG anyway.

How much can an Unruh Act website claim cost a business?

Civil Code section 52 sets damages at actual damages up to three times that amount, with a minimum of $4,000 for each offense, plus attorney's fees decided by the court. In Munson v. Del Taco (2009), the California Supreme Court held that a plaintiff whose claim rests on an ADA violation does not have to prove the business intended to discriminate. Your own defense costs come on top of whatever is paid out.

Which version of WCAG should my website meet?

Aim for WCAG 2.2 at level AA. W3C published it in October 2023, and it keeps the 2.0 and 2.1 success criteria essentially unchanged apart from one it retired as obsolete. The federal rule for state and local governments names WCAG 2.1 AA, and California courts have ordered sites brought up to WCAG 2.0 AA, so building to 2.2 AA covers what each of those asked for.

Will an accessibility overlay or widget make my site compliant?

Don't count on it. In April 2025 the FTC finalized a $1 million order against accessiBe after alleging that its claim that accessWidget could make any website WCAG compliant was false, misleading or unsubstantiated. W3C says no tool alone can determine whether a site meets accessibility standards. Problems in a page's code get fixed in the code.

Does the DOJ's 2024 web accessibility rule apply to my business?

No. That rule, issued under Title II of the ADA, covers the websites and mobile apps of state and local governments and related public bodies. After an April 2026 extension, governments serving 50,000 people or more must meet WCAG 2.1 AA by April 26, 2027, and smaller ones by April 26, 2028. A private business is affected only when it does work for a public agency, since the agency must make sure its contractors follow Title II.

Can anyone certify my website as ADA compliant?

Treat that offer with caution. No federal regulation sets a pass or fail test for private business websites, and the Department of Justice says its 2022 web guidance has no legally binding effect. An audit report tells you how your pages measured against WCAG on the day someone tested them. That's useful for finding the work to do, but it isn't a shield.

What should I do if I get an ADA demand letter about my website?

Contact a lawyer who defends disability access claims, note any deadline in the letter, and keep a copy of your site as it appeared on the dates it describes. Don't ignore it and don't reply on your own. Fixing real barriers in the code is still worth doing, with a record of each fix, but let your lawyer handle the response. Nothing in this article is legal advice.

The Starter plan

Want a site where these fixes are yours to make?

Starter is $99 a month: custom design up to five pages, hosting, and two hours of edits every month. You own the code, and it's live in 7 days.

See how we build
← Back to journal