ADA Website Lawsuits and Small Businesses: What the Law and Courts Say

Yes, a small business can face an ADA website lawsuit. There is no DOJ regulation setting a web standard for private businesses, but DOJ says the ADA applies to goods and services offered online, and WCAG 2.1 AA is the benchmark that complaints and settlements use. Plaintiffs filed 3,117 federal website accessibility suits in 2025.

That figure comes from Seyfarth Shaw's annual count, and it excludes state courts. This guide explains what the law says, where courts disagree, what usually triggers a claim, and the order we fix things in. It is written for owners and marketing managers, not lawyers, and it is general information rather than legal advice.

The short answer

A small business can be sued over its website under Title III of the ADA, and it happens thousands of times a year. Size gives no exemption. What protects you is a site that people with disabilities can actually use, and evidence that you test and fix it.

Here are the facts that matter, each with its source:

• There is no DOJ regulation with a web standard for private businesses. DOJ's own guidance says it "does not have a regulation setting out detailed standards" (ADA.gov, March 18, 2022).
• DOJ's position is that the ADA still applies online. The same guidance says the ADA's requirements apply to the goods and services public accommodations offer on the web, and points to WCAG as helpful guidance.
• Filings went up in 2025. Plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025, up 27% from 2,452 in 2024, according to the law firm Seyfarth Shaw (Seyfarth, March 25, 2026).
• The count is a floor. Seyfarth counts federal cases only. State court suits and demand letters that never become lawsuits are not in the number.

This is general information, not legal advice. If you have received a demand letter or a complaint, speak to a lawyer licensed in your state before you reply.

What the law actually says

Title III of the ADA bans discrimination on the basis of disability by "public accommodations", which covers most businesses open to the public: stores, restaurants, clinics, law firms, gyms, hotels and many more. The statute was written in 1990 and does not mention websites.

DOJ started work on a Title III web rule with an advance notice in 2010, then withdrew it in December 2017 (82 FR 60932). No proposal has been published since. So for private businesses there is still no rule saying "meet this exact standard by this date".

That is often misread as "no requirement". It is not. DOJ's 2022 guidance says businesses "have flexibility in how they comply" but "must comply with the ADA's requirements", and it names WCAG and the federal Section 508 standards as existing technical guidance.

Do not confuse Title III with Title II

In 2024 DOJ did issue a detailed web rule, but it is for state and local governments under Title II, with WCAG 2.1 AA as the standard and deadlines now set for 2027 and 2028. It does not apply to private businesses directly. It matters to you only if you build or sell services to a public entity. See our guide to the ADA Title II web rule for that.

Why WCAG became the benchmark

With no regulation, everyone needed a measuring stick, and WCAG was the one available. Plaintiffs cite WCAG failures in complaints. Settlements commonly commit the business to WCAG 2.1 AA (or newer). Auditors test against it. The Title II rule adopted WCAG 2.1 AA for governments. None of this makes WCAG law for private businesses, but it is the standard your site will be measured against in practice. We recommend building to WCAG 2.2 AA, the current version.

What courts have said

Courts do not agree on everything, and where a business is sued can change the outcome. The main dividing line is whether a website counts as a "place of public accommodation" by itself, or only when it is connected to a physical location.

• Businesses with a physical location. Courts widely accept claims where the website is tied to a store, restaurant or office. The best known example is Robles v. Domino's Pizza, where the Ninth Circuit held in 2019 that the ADA applied to Domino's website and app because they connected customers to its physical restaurants. The Supreme Court declined to hear the appeal that year.
• Online-only businesses. Here the courts split. Seyfarth's 2026 report notes that federal courts in New York have been more favorable to plaintiffs suing online-only businesses, while California federal courts have generally found online-only businesses are not covered by the ADA.

The geography shows up in the numbers. In 2025, New York had 1,021 federal website suits and Florida 961, while California had just 4, according to Seyfarth. That does not mean California is safe. California's Unruh Civil Rights Act allows statutory damages of at least $4,000 per violation, so many California claims are filed in state court, where the federal count does not see them.

What a plaintiff can win

Under federal Title III, a private plaintiff can get an injunction (an order to fix the site) and attorney's fees, but not money damages. Money damages come from state laws such as California's. This is one reason many cases settle early: the business pays the plaintiff's legal fees, agrees to fix the site to a WCAG level, and sometimes pays damages under a state claim. The settlement amounts are usually private.

How many lawsuits are filed

Seyfarth Shaw has counted federal website accessibility lawsuits every year since 2017, by searching federal court filings and reviewing each one by hand. It is the most widely cited annual count and the one we use.

Seyfarth links the 2025 rebound to new plaintiff law firms entering the area, and notes that these cases are easy to file because the plaintiff does not need to visit a business in person.

For 2026, Seyfarth's mid-year report counted 5,006 federal Title III suits of all kinds in the first six months, up 9% on the same period of 2025 (Seyfarth, September 2026). That report did not give a separate website figure, so we will not guess one.

States are starting to push back

Missouri passed a law aimed at "abusive" website accessibility suits, operative August 28, 2026. According to Seyfarth's summary, it lets a Missouri defendant bring its own action to decide whether a suit is abusive, and creates a presumption of abuse where the business received written notice and made good-faith efforts to fix the problem within 90 days (Seyfarth, May 27, 2026). It only applies in Missouri, and it rewards fast, documented fixes, which is the plan below anyway.

What usually triggers a claim

Most claims describe a blind or low-vision user, often using a screen reader, who could not complete an ordinary task: buying a product, booking an appointment, reading a menu, or finding opening hours. The barriers behind those failures are usually basic.

The WebAIM Million study tests the home pages of the top one million websites every year. Its 2026 report found detectable WCAG failures on 95.9% of home pages, with an average of 56.1 errors per page (WebAIM, 2026). The most common failures were:

On top of those, the problems we most often find on small business sites are:

• Checkout or booking steps that cannot be completed with a keyboard alone
• Pop-ups and cookie banners that trap focus or cannot be closed
• Menus or price lists posted only as images or scanned PDFs
• Videos without captions
• CAPTCHA puzzles with no accessible alternative
• Error messages shown only in red, with no text explaining the problem

Why an overlay widget is not the fix

Overlay widgets are scripts that add a toolbar to your site and promise compliance with one line of code. They do not change the underlying code that screen readers and keyboards rely on, and many disabled users find they get in the way.

Regulators have taken notice. In April 2025 the Federal Trade Commission approved a final order requiring the overlay company accessiBe to pay $1 million, over claims that its product could make any website WCAG compliant (FTC, April 22, 2025). That order is about one company's marketing, not a ruling on every overlay, but it is a clear signal that "install this and you are compliant" is not a claim to rely on. Overlays have not reliably stopped lawsuits either.

A practical fix order

Fix the things that stop people from buying or booking first, then the things that appear on every page, then everything else. That order reduces both real barriers and risk fastest.

1. Your money path. Test the journey that earns revenue: product page, cart, checkout, booking form, contact form. Do it with a keyboard only (Tab, Shift+Tab, Enter, Space, arrow keys). If you cannot finish, a screen reader user cannot either.
2. Forms. Every field needs a visible label tied to it in code, clear error messages in text, and no time limit that kicks people out.
3. Shared templates. Header, navigation, footer, cookie banner and pop-ups appear on every page. One fix here fixes the whole site.
4. Images and icons. Add meaningful alt text to informative images, empty alt to decorative ones, and accessible names to icon buttons and links.
5. Contrast and text size. Body text needs a contrast ratio of at least 4.5 to 1. Check that the page still works when zoomed to 200%.
6. Menus, price lists and documents. Move key information out of images and PDFs into real HTML text.
7. Video. Add captions to any video that carries information.
8. Accessibility statement. Publish what standard you aim for and a phone number and email address for reporting problems. Answer those reports quickly.
9. Keep testing. New content brings new failures. Scan monthly and test by hand after each change to forms or checkout.

Keep a dated record of what you tested, what you found and what you fixed. If you are ever challenged, that record shows good faith, and under laws like Missouri's, speed and documentation can matter.

If you receive a demand letter

• Do not ignore it, and do not respond without a lawyer.
• Do not rely on installing an overlay as your answer.
• Have the site audited against WCAG 2.1 or 2.2 AA so you know the real position.
• Start fixing the barriers in the letter and document each fix with dates.

What fixing it costs

For most small business sites, the cost of fixing accessibility is driven by how the site was built, not by how many pages it has. A site on a modern theme with a few templates is often a short project. A site with years of hand-built pages, a heavily customized checkout, or a theme that is inaccessible at its core may be cheaper to rebuild than to patch. For a typical small business site on a modern theme, our WCAG 2.2 AA remediation usually costs $500 to $2,000; heavily customized sites cost more and are sometimes better rebuilt.

If you are weighing a rebuild, our free website cost calculator gives a USD estimate for your site type, and our guide to small business website costs explains what drives the number. Building accessibility in from the start adds about $500 to $2,000 to a new build; retrofitting later always costs more.

Next steps

Start with a scan of your home page and your checkout or booking page using our free accessibility checker. Then do the keyboard test on your money path yourself. Those two steps take under an hour and will tell you whether you have a small job or a big one.

For the fundamentals behind all of this, read our web accessibility guide and our plain-language WCAG 2.2 checklist. When you want help, contact us.

Not legal advice. Laws and court decisions vary by state and change over time.