Most owners first hear about an ADA website lawsuit secondhand. A friend who runs a dental practice got a letter. A trade association sent a warning email. A vendor’s sales pitch opened with a headline about “record filings.” It all sounds frightening and vague at the same time, which is the worst combination for making good decisions.
This post explains how these claims usually come about, what they tend to say about a website, and why some firms send so many of them. Knowing the mechanics takes a lot of the fear out of it, and it points straight at the things an owner can do. One note up front: this is general background, not legal advice. If you have a letter or a complaint in hand, take it to a lawyer.
Where an ADA website lawsuit comes from
Title III of the Americans with Disabilities Act bars businesses open to the public from excluding people with disabilities. The law does not mention websites, because it predates them, but the Justice Department has long taken the view that it covers the online content of public accommodations. Private individuals can bring claims under Title III, which is how website disputes usually begin.
The usual sequence looks something like this:
- A person who uses assistive technology, such as a screen reader, visits a business website and runs into barriers. Sometimes this is an ordinary customer. Sometimes it is a person who checks many sites on purpose, often called a tester.
- A law firm records what went wrong. That record can be detailed notes from the visit, results from an automated scanner, screenshots, or all three.
- The business then receives either a demand letter, which proposes settling before anything is filed, or a complaint filed in court.
Courts have not agreed on every question these claims raise, such as whether a business with no physical location is covered. Those arguments are for lawyers. For a business owner, the practical point is simpler: a claim can be built entirely from what is visible on your public site, from anywhere in the country.
What these complaints usually point to
When you read a website accessibility complaint or demand letter, the technical section tends to describe a familiar set of barriers. They are often mapped, loosely or precisely, to the AA level of the WCAG guidelines (2.1 or 2.2). Letters and settlements lean on WCAG because the DOJ has never issued a technical rule for private business websites.
| What the complaint says | What it usually means on the site | Related WCAG criterion |
|---|---|---|
| Images lacked alternative text | Product photos, logos or banners with no text equivalent, so a screen reader says “image” or reads a file name | 1.1.1 Non-text Content |
| Could not complete the form | Fields with no labels, errors shown only in red, a CAPTCHA puzzle | 3.3.1, 3.3.2, 4.1.2 |
| Navigation required a mouse | Dropdown menus that open only on hover, buttons the keyboard cannot reach | 2.1.1 Keyboard |
| Links were unclear | Many links that all say “Learn more” or icon links with no name | 2.4.4 Link Purpose (In Context) |
| Video had no captions | Promotional or how-to videos with speech and no accurate captions | 1.2.2 Captions (Prerecorded) |
| Text was hard to read | Light gray text, white text on pale brand colors | 1.4.3 Contrast (Minimum) |
Notice that none of this is obscure. These are the same issues a careful audit finds first, and the same ones that frustrate real customers. A complaint that lists them is not inventing problems; it is describing barriers that probably exist.
Also notice where the barriers often sit: in a booking widget, a menu PDF, a chat button, a third-party review carousel. Owners sometimes assume those belong to the vendor. In a claim, they are part of your site.
Why the same firms file so many similar claims
If you read about these cases, you will see the term “serial” filings: the same plaintiff or the same law firm bringing near-identical claims against one business after another. People argue about whether that is good or bad. Some see it as the main way a civil rights law gets enforced when no regulator checks websites. Others see letters that look nearly identical and conclude the goal is a quick settlement rather than a usable site. Both views exist, and you do not need to pick one to protect your business.
What matters is why the model works:
- Barriers are easy to find remotely. Anyone can visit your site at night from another state and record what fails.
- Many sites share the same faults. Popular themes, page builders and plugins repeat the same problems across a great many sites, so a firm can describe them with a template.
- Scans make documentation cheap. A free scanner produces a long list of errors in seconds, even if it misses a lot and overstates some things.
- Resolving can look easier than fighting. For a small business, a quick resolution may seem less disruptive than a long dispute, which keeps letters coming. Whether that is the right choice in your case is a question for your lawyer.
The takeaway is not that you are a target because you did something unusual. It is that ordinary, common barriers are what these claims are built on.
Things that do not work
Faced with the idea of an ADA website lawsuit, owners tend to grab whatever looks fastest. Three of the usual choices backfire.
Installing an overlay widget
Overlay toolbars and scripts promise to make a site accessible automatically. The script sits on top of the same broken menu and unlabeled form, and owners running these tools have still been named in claims. Advocacy groups and many practitioners object to them, and the FTC acted against the vendor accessiBe in 2025 over claims it called misleading. Our explainer on why accessibility widgets fall short covers the details.
Displaying a “compliant” badge
There is no official certification for Title III websites. A badge from a scanning service tells a plaintiff’s firm nothing about whether a screen reader user can book an appointment, and it can look like a claim you cannot support.
Taking the site down or hiding pages
Pulling pages offline without advice can cause new problems, especially if a claim is already in progress, because it may look like evidence is being removed. Ask your lawyer first.
What owners can do before anything arrives
No one can make a business immune from a website accessibility lawsuit, and you should distrust anyone who says otherwise. What you can do is remove the barriers these claims describe and keep a record that shows real, ongoing effort.
- Find out where you stand. Have your key pages and tasks tested against WCAG 2.2 AA with both automated tools and manual keyboard and screen reader checks. A good WCAG audit of your key templates gives you a prioritized list, not just a score.
- Fix the common items first. Alt text, form labels and errors, keyboard menus, focus visibility, contrast and captions. They are the items in the table above for a reason.
- Look at your third-party tools. Booking, chat, reviews, maps and payment widgets. Test them like the rest of the site and ask vendors what they are doing.
- Write down what you did. A dated log of findings, fixes and retests is useful for your own planning and for your lawyer if a question ever comes up.
- Publish a real contact route. An honest accessibility statement with a feedback channel tells visitors how to report a problem and how you will respond. Then answer people who use it.
- Keep checking. New pages, plugin updates and seasonal popups bring back old problems. Ongoing accessibility monitoring after updates catches regressions before a stranger does.
Already holding a letter? Then the order changes, and it starts with a lawyer. We cover that separately in the calm steps after a demand letter. For how the federal rules divide between businesses, governments and federal agencies, see our plain-English guide to the ADA requirements for websites, and for the services side, from audits to monitoring, see our website accessibility hub.
Frequently asked questions
Can someone sue over my website if they never visited my store?
Claims are usually based on barriers found on the website itself, which anyone can visit from anywhere. Whether a particular claim holds up depends on the facts, the court and how the law is read there, which is why courts have not all agreed. A lawyer is the right person to assess any specific claim.
Is a demand letter the same thing as a website accessibility lawsuit?
No. A demand letter is a private letter, usually from a law firm, that describes alleged barriers and proposes resolving the matter before anything is filed. A lawsuit is a complaint filed in court. Both deserve a lawyer’s attention, and the response to each is a legal decision, not a technical one.
Does fixing my website make a pending claim go away?
Not by itself. Fixing barriers helps your customers and can matter to how a dispute is resolved, but how a pending claim ends is a legal question. Let your lawyer direct the timing and scope of technical work and how it is documented once a claim exists.
Will an automated scan show what a plaintiff would find?
Only part of it. A scan can flag missing alt text, empty links and low contrast, which often appear in complaints. It cannot judge keyboard behavior, screen reader output or whether a form is usable, and those barriers are common in claims too. Manual testing fills the gap.
When the barriers themselves are what you want to tackle, our page on ADA website compliance support describes how we test, fix and document a site against WCAG 2.2 AA. We are not lawyers, and we work alongside yours when there is a legal question.
Next in this series: What to Do After an ADA Demand Letter About Your Site
