Can I Be Sued If My Website Isn't ADA Accessible?

A plain-language answer for business owners who are worried about accessibility lawsuits and demand letters—who gets sued, why disclaimers and overlays don't protect you, and the practical steps that actually lower your risk.

Yes. In the United States, businesses are regularly sued or sent demand letters because their websites are not accessible to people with disabilities. Courts in most circuits treat a business's website as a "place of public accommodation" under Title III of the Americans with Disabilities Act (ADA), and thousands of web-accessibility lawsuits and demand letters are filed every year — most targeting small and mid-sized businesses, not just large ones. You don't get a warning; the first contact is usually a demand letter or a filed complaint.

The good news: this is a manageable risk. The businesses that fare best are the ones that fix the real barriers in their code and keep a dated record of doing so — long before any letter arrives. Below is what the risk actually looks like and what to do about it.

Why websites get sued under the ADA

Title III of the ADA prohibits discrimination against people with disabilities by "places of public accommodation" — businesses that serve the public, such as stores, restaurants, medical offices, hotels, and service providers. The statute was written in 1990, before the modern web, so it does not mention websites by name. That gap is exactly why litigation exists.

Over the past decade, federal courts in most circuits have concluded that a business's website is covered by Title III, either as a public accommodation itself or because it is closely connected to a physical location. The U.S. Department of Justice has likewise stated that the ADA applies to the websites of public accommodations. Because the law itself sets no technical rulebook, courts and plaintiffs have adopted the Web Content Accessibility Guidelines (WCAG), published by the W3C, as the de-facto standard. WCAG 2.1 Level AA — and increasingly WCAG 2.2 Level AA — is the benchmark almost every demand letter and complaint references.

So a claim typically works like this: a plaintiff (or an automated tool acting for a plaintiff's firm) finds barriers on your site — missing image descriptions, form fields with no labels, poor color contrast, content that can't be reached with a keyboard — and frames those barriers as a Title III violation measured against WCAG.

Who actually gets sued

A common misconception is that only large corporations are targets. In reality, the opposite is closer to the truth. The businesses most frequently on the receiving end include:

• Small and mid-sized businesses. Because a smaller business is more likely to settle quickly rather than pay to litigate, it can be a more attractive target.
• E-commerce and online-ordering sites. A checkout flow that a screen-reader user can't complete is one of the most commonly cited barriers.
• Businesses in high-filing jurisdictions. Certain federal districts see a disproportionate share of website accessibility filings.
• Any site with obvious, automatically detectable barriers. High-volume plaintiff firms and "demand-letter mills" use automated scanners to identify targets at scale, then send letters to many businesses at once.

Traffic volume does not protect you. A single person who encounters a barrier can bring a claim, and many claims originate from automated scanning rather than an actual customer complaint.

What a claim looks like

There are two main forms the risk takes:

The demand letter

Most matters begin with a pre-suit demand letter from a plaintiff's attorney. It alleges that your website fails WCAG/Title III, lists barriers, and typically asks you to remediate and pay a monetary settlement within a short window. A demand letter is not a lawsuit — but ignoring it commonly leads to one.

The filed lawsuit

A complaint filed in federal (or sometimes state) court raises the stakes: you now face litigation deadlines, defense counsel, and potential exposure to the plaintiff's attorney's fees, which the ADA allows a prevailing plaintiff to recover.

Costs vary widely by jurisdiction, by the firm involved, and by how far the matter proceeds. In general terms, a demand letter often resolves through a negotiated settlement plus a remediation commitment, while a litigated lawsuit can cost meaningfully more in defense fees. Because real numbers swing so much from case to case, be skeptical of any specific dollar figure you see quoted online, and get an attorney's read on your own situation. This page is general legal information, not legal advice.

Does a disclaimer or overlay protect me?

No. Two of the most common "quick fixes" do not work the way vendors imply:

• Accessibility statements or disclaimers — a page saying you're "committed to accessibility" or inviting users to email you — do not resolve underlying barriers and do not stop a claim.
• Accessibility overlays and widgets — third-party scripts that promise to make a site compliant automatically — have been repeatedly rejected in practice. Courts have declined to treat an installed overlay as ADA compliance, and many lawsuits have been filed against sites that already had an overlay running. Overlays frequently fail to fix the real WCAG problems and can even introduce new barriers for assistive-technology users.

The reality of overlay marketing was underscored when the U.S. Federal Trade Commission fined the largest overlay vendor $1,000,000 over deceptive claims about its product. The lesson: a widget is not a defense. Real fixes live in your site's code.

How to lower your risk

You can substantially reduce your exposure without waiting for a letter:

• Fix real WCAG 2.1 / 2.2 AA barriers in the code. Add meaningful alt text, label every form field, meet color-contrast ratios, ensure full keyboard operability, use proper heading structure, and confirm your checkout or contact flow works with a screen reader.
• Test with an audit, not a widget. Scan your site to see exactly which success criteria you fail, then remediate the highest-severity issues first.
• Keep a dated, good-faith remediation record. Save timestamped before-and-after audit reports. Courts and plaintiff's counsel treat documented, genuine remediation as a material factor. A dated, itemized record is one of the clearest forms of that evidence.
• Make accessibility part of ongoing maintenance. Re-test when you redesign, add pages, or change your platform, so new barriers don't creep back in.

Scan your site free to see which WCAG issues a plaintiff's automated tool would find first — and start your remediation record today.

What to do if you already got a letter

Do not ignore it, and do not panic. In short: preserve the letter, run an audit to create a timestamped baseline of your site's current state, begin remediating the highest-severity issues, and consult a licensed attorney before you respond to plaintiff's counsel. Do not contact the plaintiff's attorney directly or post about the letter publicly without legal guidance, and do not assume an overlay resolves anything.

For a step-by-step walkthrough of the first 48–72 hours, see our guide on how to respond to an ADA website demand letter. To understand where filings are concentrated, see ADA website lawsuits by state.

Frequently asked questions

Can a small business really be sued over its website?

Yes. Small and mid-sized businesses are the most common targets of website accessibility claims, not large corporations. Because filing or sending a demand letter is inexpensive for plaintiffs, high-volume plaintiff firms often send letters to hundreds of businesses at a time. Being small does not exempt you and, in practice, makes you a more attractive target because smaller businesses are more likely to pay a settlement quickly to avoid litigation costs.

Do I have to be ADA compliant if I'm not a government site?

In most cases, yes. Title III of the ADA applies to private businesses that are "places of public accommodation"—a category that courts in most circuits have applied to business websites. The 2024 Department of Justice rule requiring WCAG 2.1 AA applies specifically to state and local government sites, but private businesses are still exposed to Title III lawsuits and demand letters that use WCAG 2.1/2.2 AA as the practical benchmark.

Will an accessibility widget or overlay stop a lawsuit?

No. Courts have rejected the argument that installing an overlay widget satisfies the ADA, and many accessibility lawsuits have been filed against sites that already had an overlay installed. In 2025 the Federal Trade Commission fined the largest overlay vendor $1,000,000 over deceptive claims about its product. Overlays do not reliably fix underlying WCAG barriers and can introduce new ones. Genuine, code-level remediation is what lowers your risk.

How much do these lawsuits cost?

Costs vary widely and depend on the jurisdiction, the plaintiff's counsel, and how far the matter goes. Many businesses report that pre-suit demand letters resolve through a negotiated settlement plus a commitment to remediate, while a filed lawsuit that is litigated can cost substantially more in legal defense fees. Because figures vary so much by case, treat any specific dollar amount you see online with caution and get a licensed attorney's assessment of your own situation.

What accessibility standard do I need to meet?

There is no single ADA statute that names a version number for private websites, but WCAG 2.1 Level AA—and increasingly WCAG 2.2 Level AA—is the widely used benchmark. The Department of Justice and courts have treated WCAG as the practical measure of accessibility, and plaintiff attorneys routinely reference WCAG success criteria in demand letters. Building and testing to WCAG 2.1/2.2 AA is the most defensible target.

Do I get a warning before I'm sued?

Usually not. There is no government notice or grace period. The first contact is almost always a demand letter from a plaintiff's attorney or a complaint that has already been filed. That is why proactively fixing WCAG barriers and keeping a dated remediation record matters before any letter arrives.

Does having a small number of website visitors protect me?

No. Liability under Title III does not turn on how much traffic your site receives. A single individual who encounters a barrier can bring a claim, and plaintiff firms frequently identify targets through automated scanning rather than actual customer complaints. Low traffic does not remove your exposure.

This article is general legal information, not legal advice. For guidance on your specific situation, consult a licensed attorney.