Website Accessibility and the Demand Letters That Follow

A demand letter is often the first sign that your site has accessibility barriers. Here is what the letters claim, why an overlay isn’t a defense, and what a defensible record looks like.

Written byConor Meyers
Reviewed byLee Clark
Published October 19, 2026
Last updated October 19, 2026

Businesses open to the public can face ADA claims over inaccessible websites, and the claim often arrives as a demand letter. No federal rule sets the standard for private sites, but WCAG is the common benchmark. An overlay widget isn’t proof of compliance. Dated testing, fixes and a way to report problems are.

Key takeaways

  • The Department of Justice says Title III covers websites of businesses open to the public, and the Ninth Circuit applied the ADA to a website and app tied to physical locations in Robles v. Domino’s.
  • The Department says it has no regulation setting out detailed standards for web accessibility, and treats WCAG as helpful guidance. Its only web rule so far, for state and local governments, adopts WCAG 2.1 Level AA.
  • Federal private plaintiffs can seek an injunction and attorney’s fees. In California, the Unruh Act adds statutory damages of up to three times actual damages, with a minimum of $4,000 per offense.
  • The FTC’s April 2025 order against accessiBe, a seller of an automated accessibility tool, requires evidence before any claim that a tool makes a website WCAG-compliant, so a widget alone is a weak answer to a demand letter.
  • A defensible record is dated and specific: a stated benchmark, manual and automated test results, a prioritized fix plan, re-testing, and a published way for people to report problems.

Can you be sued over your website’s accessibility?

Yes. A business open to the public can face a claim if its website or app has barriers that keep people with disabilities from using what it sells, and the claim often arrives as a demand letter before it becomes a lawsuit. The question for most owners is not whether the risk exists but how much of it your site carries today.

Public accommodation is the ADA’s term for a business open to the public, such as a store, restaurant or hotel. Title III of the ADA prohibits discrimination against people with disabilities by these businesses.

The Department of Justice’s web accessibility guidance, published in March 2022, puts it plainly: a website with inaccessible features can limit the ability of people with disabilities to access a public accommodation’s goods, services and privileges available through that website. The Department expects businesses to make sure the goods and services they provide online are accessible, even though it leaves them flexibility in how.

WCAG is the Web Content Accessibility Guidelines, a set of technical success criteria for accessible web content published by the World Wide Web Consortium (W3C), at levels A, AA and AAA.

Courts have applied the statute to websites too. In Robles v. Domino’s Pizza, decided in January 2019, the Ninth Circuit held that Title III applies to a website and mobile app that connect customers to physical restaurants. The court wrote that the statute “applies to the services of a place of public accommodation, not services in a place of public accommodation.” California and Idaho are both in the Ninth Circuit, so that decision governs federal cases in both states.

Selling or booking online? A short accessibility risk review shows what a demand letter would find on your site and what a sensible fix list looks like.

Book Your Free Legal-Strategy Call

What do accessibility demand letters typically claim?

Accessibility demand letters generally allege that specific features of your website created barriers for a person with a disability, and the barriers named usually fall into a short list of familiar categories. The Department of Justice’s guidance lists the barriers it considers common, and it is a useful way to read a letter or to audit your own site.

Common web barriers named by the Department of Justice, and where to look on a sales or booking site
BarrierWhat the Department saysWhere to look on your site
Low color contrastPeople with limited vision or color blindness can’t read text without enough contrast.Button labels, sale prices, placeholder text, text over images.
Information conveyed by color alonePeople who are color-blind may miss information shown only through color cues.Required-field markers, sold-out labels, calendar availability.
Missing text alternativesPeople who are blind can’t understand images or their purpose without a text alternative.Product photos, icon-only buttons, image links, maps.
Videos without captionsPeople with hearing disabilities may not understand video that has no captions.Product demos, promotional and tour videos.
Inaccessible formsForms need labels that screen readers can convey, clear instructions and error indicators.Checkout, booking and contact forms, date pickers, payment fields.
Mouse-only navigationPeople who can’t use a mouse or trackpad can’t reach content they can’t operate by keyboard.Menus, carousels, pop-ups, calendars, add-to-cart flows.
Missing headingsPeople who are blind use headings to navigate and understand the layout of the page.Page templates, category pages, long policy pages.

The Department presents these as examples, not as a complete list, and the right-hand column is our own prompt for where the same issues tend to occur on sales and booking pages. The highest-stakes places are usually the ones that turn a visit into revenue: search, cart, checkout and booking.

One caution applies to both sides of a letter. The Department notes that “a ‘clean’ report does not necessarily mean everything is accessible,” and also that “a report that includes a few errors does not necessarily mean there are accessibility barriers.” A letter built from a scan may overstate the problem. A clean scan of your own site may understate it. Either way, a person has to look.

Is WCAG the law for private businesses?

Not by name. The Department of Justice says it does not have a regulation setting out detailed standards for web accessibility, and it describes WCAG and the Section 508 standards as helpful guidance on how to make website features accessible. The obligation comes from the ADA’s general requirements, which courts apply case by case.

The Ninth Circuit addressed the gap in Robles. It said that the lack of specific regulations cannot eliminate a statutory obligation, and it described compliance with WCAG 2.0 as a potential equitable remedy for the district court to consider, not the basis for liability. In other words, WCAG isn’t the test of whether you violated the statute, but a court deciding what to order may reach for it.

Where the Department has written a rule, it chose WCAG. Its Title II web rule sets WCAG 2.1 Level AA as the technical standard for the web content and mobile apps of state and local governments, and 28 CFR 35.200 incorporates that standard. An interim final rule published on April 20, 2026 extended the compliance dates to April 26, 2027 for larger entities and April 26, 2028 for smaller ones. The rule says it addresses only Title II, so it does not set a deadline for private businesses.

WCAG isn’t the statute. It is the measuring stick the Department chose when it did write a rule.

The W3C published WCAG 2.2 as a Recommendation on December 12, 2024. It organizes its criteria under four principles: content must be perceivable, operable and understandable, and it must work reliably with assistive technologies. It defines conformance at levels A, AA and AAA and is designed to be compatible with earlier versions. You can read the standard at w3.org/TR/WCAG22.

For a business that wants a working target, WCAG 2.1 or 2.2 at Level AA is a reasonable choice: it matches the standard the Department adopted for governments and gives your developer a concrete target. Which version to pick is a judgment call, and your counsel and developer should make it together.

Editorial image accompanying the section on WCAG and the law
WCAG is the benchmark most often used, not the statute itself.

What can a plaintiff recover over an inaccessible website?

Under federal law, a private plaintiff can generally seek an injunction and attorney’s fees but not compensatory damages, while California’s Unruh Act adds statutory damages of up to three times actual damages, with a minimum of $4,000 per offense. That difference is why the same website can carry different risk in different places.

Start with the federal statute. 42 U.S.C. § 12188(a)(1) gives private plaintiffs the remedies and procedures in 42 U.S.C. § 2000a-3(a), which provides for a civil action for preventive relief, including a permanent or temporary injunction, restraining order or other order. Section 2000a-3(b) lets the court, in its discretion, allow the prevailing party a reasonable attorney’s fee. It does not provide compensatory damages to private plaintiffs. The Attorney General has separate authority to bring certain actions and seek civil penalties.

So a federal-only claim is mainly about fixing the site and who pays the lawyers. That is not a small matter, because the cost of fees on both sides and the cost of the fix are what a settlement conversation is built from.

California adds money damages

The California Civil Rights Department explains that the Unruh Civil Rights Act requires businesses to comply with the ADA, and lists remedies that include up to three times actual damages and no less than $4,000 in statutory damages, plus attorney’s fees. Its FAQ answers the website question with “it depends.” According to the CRD, courts have interpreted the Unruh Act’s accessibility provisions to apply to websites associated with businesses that have physical locations, and courts have found that online-only businesses are not places of public accommodation under the Act, though the CRD encourages them to make their sites accessible anyway.

Two cautions. First, whether an online-only business is covered by the federal ADA is a separate question that the Ninth Circuit did not resolve in Robles, which involved a site tied to physical restaurants. Second, the facts of your business matter: a booking page for physical locations looks more like Robles than a purely digital store does. Don’t assume either outcome without advice.

Does an accessibility overlay protect you from a claim?

Not on its own. A vendor’s statement that a widget makes your site compliant isn’t evidence that it does, and the FTC has treated that kind of claim as one that needs proof. An overlay may help with some features, but it doesn’t replace testing, fixes at the source and records.

The FTC’s April 2025 final order against accessiBe is the clearest example. The agency alleged that the company’s accessWidget “did not make all user websites WCAG-compliant” despite its marketing, and that it presented paid reviews as independent opinions. The order requires accessiBe to pay $1 million and bars it from claiming its automated products make websites WCAG-compliant, or ensure ongoing compliance, unless it has the evidence to support the claim.

The FTC’s guidance for businesses on the case states the lesson in general terms: before you claim your product can perform a certain task, you need evidence it will work as promised. Buyers should apply the same standard from the other side. If a vendor tells you its product makes your site compliant, ask for the testing, the conformance reports, and the contract terms that stand behind the statement.

Keep the case in perspective. It concerned one company’s claims and marketing, and it does not decide how every overlay performs. The Department of Justice makes a related point about automated tools generally: pairing automated checks with human review gives the clearest picture. A widget can be one layer of an accessibility program. It is a weak answer to a demand letter by itself, because it doesn’t show what you tested, what you fixed or when.

Your vendor contract matters here too. Our guide to reviewing a vendor contract before you sign covers the warranties, indemnities and exit terms to look for when a tool promises a legal outcome.

What does a defensible remediation record look like, and what do you do when a letter arrives?

A defensible record shows a stated benchmark, dated test results, a prioritized fix plan, completed and re-tested work, and a published way for people to report problems. It is dull and specific, which is the point. Records made before a letter arrives carry more weight than records assembled afterward.

  1. Set a benchmark and scope. Choose WCAG 2.1 or 2.2 at Level AA as your working target, and list the journeys that matter: browsing, search, cart and checkout, booking, account pages, forms, PDFs and video.
  2. Test with tools and with people. Run automated checks, then test the key journeys by keyboard and with a screen reader, because automated tools miss barriers. Save the dated results.
  3. Write a dated remediation plan. Rank issues by whether they block a purchase or booking, assign owners and deadlines, and update the plan as work is completed.
  4. Fix at the source and re-test. Correct the templates and components, not individual pages, then re-test and keep the before-and-after results.
  5. Publish a statement and a way to report problems. Offer a monitored email or form and log each report and fix. The Department of Justice notes that a way for the public to report accessibility problems helps site owners fix them.

Third-party tools count. Booking engines, payment forms, chat widgets and embedded calendars are part of the experience a visitor sees. Ask each vendor for its conformance information and put accessibility expectations in the contract.

Want a remediation record you could hand to a judge or an insurer? We can scope the audit, review the vendor terms and keep the file organized with your developer.

Book Your Free Legal-Strategy Call

If a letter arrives

Don’t ignore it and don’t pay it reflexively. Preserve the current state of your site and the relevant records, as we explain in our guide to preserving evidence when a dispute looms. Check whether your insurance may respond, which our overview of business insurance every owner should consider can help with. Read the letter for facts: what the person says they tried to do, on which pages, and whether you can reproduce the barrier.

Then look at the legal footing. Do you have physical locations that the site serves? Does California law apply to the claim? Start fixing the issues that are real, since that helps however the claim ends. Have counsel handle the reply, and keep it measured: our guide to responding to a demand letter without escalating explains why. If settlement makes sense, settling a business dispute: when and how covers the options.

Your site’s legal pages belong in the same review. See our overview of website terms and policies your business needs for the documents that should sit alongside an accessibility statement.

Editorial image accompanying the section on remediation records
Dated test results and fixes are what a remediation record is made of.

Key terms

Overlay
A third-party script or widget added to a website that claims to detect and fix accessibility problems automatically, usually without changing the site’s underlying code.
Title III
The part of the Americans with Disabilities Act that prohibits discrimination against people with disabilities by businesses open to the public.
Equitable remedy
A court order that requires or prohibits specific action, such as fixing a website, as opposed to an award of money damages.

What does a reviewed accessibility record change?

The problem

A demand letter arrives alleging barriers on your online store and booking page. You installed an accessibility widget years ago, nobody has tested the checkout by keyboard, and you don’t know whether the person who wrote the letter has a claim.

The solution

We preserve the evidence, map the allegations to your actual site and locations, and set a testing and remediation plan with your developer. Then we handle the reply and any settlement discussion so the file shows what you did and when.

The resolution

You either resolve the claim on informed terms or answer it with a dated record of fixes. If you have no letter and no sales or booking on your site, you probably don’t need a lawyer yet: ask your developer to test against WCAG 2.1 or 2.2 Level AA, publish a way to report problems, and keep the results.

About the author

Conor Meyers, Clark Meyers PC
Conor Meyers
Co-Founder, Clark Meyers PC · Licensed in California (Bar #157601)

Co-founder of Clark Meyers PC and a Notre Dame Law School graduate who also serves as CEO and General Counsel of ACE Building Envelope Design and Chief Legal Officer of ZEA Biosciences. He has run companies as well as advised them, across construction, design, forensic investigation and biotech.

Business transactions and M&AFractional general counselContract drafting and complianceEntity formation and structuring

Reviewed by

Lee Clark, Clark Meyers PC
Lee Clark
Co-Founder, Clark Meyers PC · Licensed in Idaho and California (CA Bar #175238)

Co-founder of Clark Meyers PC, lead trial counsel, and a private mediator and arbitrator since 2008. He has served as a court-appointed arbitrator in Santa Clara County and as Judge Pro Tem in the San Mateo County Superior Courts, and handles complex commercial disputes, contract claims and real estate conflicts. Reviewed this article for legal accuracy on October 19, 2026.

Commercial litigationMediation and arbitrationCommercial real estateBusiness succession planning

How we check this work

Attorney reviewed Primary sources cited Updated when the law changes

Written from Department of Justice and FTC materials, the Ninth Circuit’s decision in Robles, the statutes cited, and California Civil Rights Department publications, and reviewed by a Clark Meyers attorney before publication. WCAG is published by the W3C at w3.org/TR/WCAG22. Whether a given website is covered, and what a court would order, depends on the facts and on the court.

Sources

  1. U.S. Department of Justice, Civil Rights Division. “Guidance on Web Accessibility and the ADA.” March 18, 2022. https://www.ada.gov/resources/web-guidance/
  2. U.S. Department of Justice, Civil Rights Division. Fact sheet on the Title II web and mobile app accessibility rule (WCAG 2.1, Level AA), March 2024. https://www.ada.gov/resources/2024-03-08-web-rule/
  3. U.S. Department of Justice. Interim final rule published in the Federal Register on April 20, 2026, document no. 2026-07663, extending Title II web accessibility compliance dates. https://www.federalregister.gov/documents/2026/04/20/2026-07663/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web
  4. Electronic Code of Federal Regulations, Title 28, Part 35, Subpart H, § 35.200. Incorporates WCAG 2.1 (a W3C Recommendation) by reference for public entities. https://www.ecfr.gov/current/title-28/chapter-I/part-35/subpart-H/section-35.200
  5. Federal Trade Commission. Press release announcing the final order against accessiBe Inc. and accessiBe Ltd., April 2025. https://www.ftc.gov/news-events/news/press-releases/2025/04/ftc-approves-final-order-requiring-accessibe-pay-1-million
  6. Federal Trade Commission, Business Blog. Lessons from the accessiBe settlement, April 2025. https://www.ftc.gov/business-guidance/blog/2025/04/million-dollar-blunder-how-ftcs-settlement-software-provider-accessibe-can-help-your-business-avoid
  7. United States Court of Appeals for the Ninth Circuit. Robles v. Domino’s Pizza, LLC, No. 17-55504, opinion filed January 15, 2019. https://cdn.ca9.uscourts.gov/datastore/opinions/2019/01/15/17-55504.pdf
  8. United States Code, Title 42, § 12188 (Americans with Disabilities Act, Title III enforcement), 2022 edition. U.S. Government Publishing Office. https://www.govinfo.gov/content/pkg/USCODE-2022-title42/html/USCODE-2022-title42-chap126-subchapIII-sec12188.htm
  9. United States Code, Title 42, § 2000a-3 (civil actions for preventive relief and attorney’s fees). Office of the Law Revision Counsel, U.S. House of Representatives. https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section2000a-3&num=0&edition=prelim
  10. California Civil Rights Department. Unruh Civil Rights Act (scope, remedies and relationship to the ADA). https://calcivilrights.ca.gov/unruh/
  11. California Civil Rights Department. Unruh Civil Rights Act frequently asked questions, including the question on website accessibility. https://calcivilrights.ca.gov/wp-content/uploads/sites/32/2024/12/Unruh-FAQ.pdf

Last reviewed: October 19, 2026 · What changed: First publication, reflecting Department of Justice, FTC and court materials as of October 2026.

Legal disclaimer

This article is general information about the law, not legal advice, and it is not a substitute for advice from a lawyer about your specific situation. Reading it does not create an attorney-client relationship with Clark Meyers PC. Laws change and apply differently depending on the facts and the state involved.

Licensed to practice in California (Bar #157601). Licensed to practice in Idaho (Idaho State Bar) and California (Bar #175238). Clark Meyers PC does not offer legal advice in states where its attorneys are not licensed. This page may be considered attorney advertising in some jurisdictions.

Frequently asked questions

Can a business be sued if its website isn’t accessible?

Yes: the Department of Justice takes the position that the ADA applies to the websites of businesses open to the public, and the Ninth Circuit has applied it to a website tied to physical locations. Whether an online-only business is covered is a different question that depends on the court. In California, the Unruh Act adds its own rules and damages. Under federal law a private plaintiff’s remedy is injunctive relief plus fees, not damages.

Does the ADA require WCAG compliance for private websites?

Not by name: the Department of Justice says it has no regulation setting out detailed standards for private websites, and describes WCAG as helpful guidance, though courts can still order accessibility measures. In Robles, the Ninth Circuit said the lack of regulations doesn’t eliminate the obligation and treated WCAG 2.0 as a potential remedy rather than the basis for liability. Many businesses use WCAG 2.1 or 2.2 Level AA as a working target. The only place the Department has adopted WCAG 2.1 Level AA is for state and local governments.

What is the difference between an ADA claim and an Unruh claim over a website?

Federal ADA claims by private plaintiffs seek an injunction and attorney’s fees, while California’s Unruh Civil Rights Act also provides statutory damages of up to three times actual damages, with a minimum of $4,000 per offense. The California Civil Rights Department says the Unruh Act requires businesses to comply with the ADA. It says the reach to websites depends on whether the business has physical locations. That difference affects how a demand is valued.

Does an accessibility overlay or widget protect my business?

Not on its own: a vendor’s claim that a tool makes your site compliant isn’t evidence that it does, and the FTC’s 2025 order against accessiBe turned on that kind of claim. The FTC alleged that accessWidget did not make all user websites WCAG-compliant and required evidence before such claims are made. The Department of Justice says a clean automated report doesn’t necessarily mean everything is accessible. Treat any tool as one input, and keep your own testing records.

What should I do when I receive an accessibility demand letter?

Don’t ignore it and don’t pay it reflexively: preserve your website’s current state and relevant records, notify your insurer if your policy may respond, and have counsel review the claim before anyone replies. Compare the letter’s allegations with your actual site. Check what the letter says the person tried to do, and whether you can reproduce the barrier. Start fixing the issues that are real.

Does the new federal rule for government websites apply to my business?

No: the Department of Justice’s Title II rule requires WCAG 2.1 Level AA for state and local government web content and mobile apps, and it doesn’t apply to private businesses under Title III. An April 2026 interim final rule moved the compliance dates to April 26, 2027 for larger entities and April 26, 2028 for smaller ones. The rule says it doesn’t address the Department’s Title III regulations. It is still a reasonable benchmark for private businesses to consider.

What should an accessibility remediation plan include?

A dated audit of your key user journeys against a stated benchmark such as WCAG 2.1 or 2.2 Level AA, a prioritized list of fixes with owners and deadlines, and records that show the work was done and re-tested. Add an accessibility statement and a monitored way for people to report problems. Include checkout, booking and forms. Revisit the plan after each major site release.

Do I need an accessible website if my business is online-only?

It depends: the Ninth Circuit’s Robles decision tied ADA coverage to a website’s connection to physical places, and California’s Civil Rights Department reports that courts have found online-only businesses are not places of public accommodation under the Unruh Act. The CRD still encourages online-only businesses to make their websites accessible. Other courts may see the federal question differently. Accessibility also helps you reach more customers.

The short version

Treat accessibility as a records problem as much as a technical one. Choose a benchmark, test with tools and people, fix at the source, publish a way to report problems, and date everything. A widget can help, but it isn’t proof. If a letter arrives, preserve the site first and respond second.

Protect What You’re Building

Schedule a complimentary strategic consultation with Clark Meyers PC and get a clear plan for your business.

Book Your Free Legal-Strategy Call
AI Assistant Online

Schedule a Consultation

Fill out the form below and we'll get back to you within 24 hours.

Request Sent!

We've received your request and will be in touch within 24 hours.

Something went wrong