Yes. If your website is not ADA compliant, you can be sued. Plaintiffs file lawsuits and send demand letters when a site has accessibility issues that prevent people with disabilities from using it. Most claims target sites that fail to meet the Web Content Accessibility Guidelines (WCAG), which courts and the Department of Justice treat as the working standard for ADA website compliance. The legal risk is real, ongoing, and not limited by company size or industry. Small businesses, ecommerce stores, healthcare providers, financial services, and education sites all face claims. The good news is that risk drops quickly once accessibility work begins.
| Question | Answer |
|---|---|
| Can you be sued? | Yes. Lawsuits and demand letters are filed every day against sites that are not ADA compliant. |
| What law applies? | Title III of the ADA covers private businesses. Title II covers state and local government. |
| What standard is used? | WCAG 2.1 AA is the working standard for most ADA website claims. |
| Who gets sued? | Ecommerce, restaurants, healthcare, financial services, retail, education, and more. |
| How do you reduce risk? | Conduct a manual accessibility evaluation, complete remediation, and document your work. |
Why Websites Get Sued Under the ADA
The Americans with Disabilities Act prohibits discrimination against people with disabilities in places of public accommodation. Courts have applied this to websites, even though the original 1990 statute predates the modern web. Title III applies to private businesses. Title II applies to state and local government entities.
Plaintiffs file claims when they cannot use a website because of accessibility issues. Common examples include images without alt text, forms that cannot be completed with a keyboard, videos without captions, and content that is unreadable with a screen reader. These are not theoretical problems. They are the same issues identified in thousands of complaints each year.
What Standard Is Used to Decide ADA Compliance?
The ADA does not name a specific technical standard for websites in the original law, but the Department of Justice and federal courts consistently point to WCAG. WCAG 2.1 AA is the working standard for most private sector claims. For state and local government, the DOJ’s Title II rule formally requires WCAG 2.1 AA, with set compliance dates.
A site that conforms to WCAG 2.1 AA gives a strong evidentiary position. A site that does not is vulnerable, regardless of intent.
Who Is Getting Sued?
ADA website lawsuits are concentrated in industries with high consumer traffic. Ecommerce stores, including Shopify sites, are the most frequent targets. Restaurants, retail chains, healthcare providers, financial services, hospitality, and education sites also see steady claim volume.
Plaintiff firms use scans to identify candidate sites. They look for the same issues over and over: missing labels, poor contrast, inaccessible menus, broken focus order. A site does not need to be famous to attract a claim. Small businesses receive demand letters regularly.
What Does a Lawsuit or Demand Letter Look Like?
Most cases start with a demand letter from a plaintiff’s attorney. The letter alleges accessibility issues, references the ADA and WCAG, and proposes settlement. If ignored, the matter can move to a filed complaint in federal or state court.
Settlement is the common outcome. The amount varies, but legal fees, settlement payments, and the cost of fixing the site after the fact almost always exceed what proactive accessibility work would have cost in the first place.
How to Reduce the Risk of Being Sued
The path is direct. Get a manual accessibility evaluation of your website. The evaluation identifies the actual issues against WCAG 2.1 AA criteria. Scans alone are not enough because they only flag approximately 25% of issues. A manual evaluation catches what automated checkers miss, including keyboard traps, screen reader logic, and meaningful sequence problems.
From there, the work moves to remediation. Developers fix the issues, an auditor validates the fixes, and the site reaches WCAG conformance. Accessible.org recommends documenting the work with an accessibility statement and keeping audit records on file.
Ongoing monitoring matters too. Websites change. New pages, new templates, and new features can introduce issues. Periodic re-evaluations and tracking through a platform like Accessibility Tracker keep the site in good shape over time.
Does an Accessibility Statement Help?
An accessibility statement on its own does not prevent a lawsuit. What it does is show good faith and provide a contact path for users who encounter issues. Paired with real evaluation and remediation work, it strengthens your position. Without that underlying work, it is just words on a page.
What About Title II for Public Entities?
The DOJ’s Title II rule sets firm dates for state and local government websites and mobile apps. Large public entities, populations of 50,000 or more, must conform to WCAG 2.1 AA by April 2026. Smaller entities have until April 2027. Public entities face a different enforcement environment than private businesses, but the standard is the same.
Frequently Asked Questions
Should I start with an evaluation or wait until I receive a demand letter?
Start with an evaluation. Reactive work after a demand letter is more expensive, more rushed, and gives the plaintiff leverage. A proactive evaluation and remediation cycle costs less and produces documentation you can point to if a claim ever arrives.
Can a small business really get sued for an inaccessible website?
Yes. Plaintiff firms file against businesses of every size. A small ecommerce site, a single-location restaurant, or a regional service provider can all receive demand letters. Revenue and headcount are not shields.
Does WCAG 2.2 AA replace WCAG 2.1 AA for ADA claims?
WCAG 2.1 AA remains the working standard for most ADA website claims today. WCAG 2.2 AA is the newer version and is increasingly requested by procurement teams and some plaintiffs. Either standard moves a site in the right direction.
How long does it take to get a website to WCAG conformance?
Timing depends on site size and the volume of issues. A typical informational site can move through evaluation, remediation, and validation in a few weeks to a few months. Larger ecommerce sites and web apps take longer.
The risk of being sued is real, but the path to lowering that risk is well established. Evaluate, fix, document, monitor. Contact Accessible.org to start an accessibility evaluation for your website.
