Website owners are sued over ADA compliance because their websites contain accessibility issues that prevent people with disabilities from using them. Plaintiffs’ law firms file claims under Title III of the ADA, arguing that a public-accommodation business has an inaccessible website. The legal benchmark courts and attorneys point to is WCAG 2.1 AA. When a site has missing alt text, keyboard traps, low contrast, unlabeled form fields, or other common issues, it becomes a target. Most cases settle quickly because litigating is expensive. The result is a steady volume of demand letters and lawsuits aimed at businesses of every size.
| Factor | What It Means |
|---|---|
| Legal basis | Title III of the ADA applied to public-accommodation websites by federal courts |
| Technical standard | WCAG 2.1 AA referenced as the working benchmark |
| Common triggers | Missing alt text, keyboard issues, contrast issues, unlabeled forms, inaccessible menus |
| Who gets sued | Ecommerce stores, restaurants, hotels, healthcare, professional services, nonprofits |
| Typical outcome | Settlement, remediation commitment, attorney fees |
The Legal Foundation Behind These Lawsuits
The Americans with Disabilities Act was signed in 1990, long before websites were central to commerce. Title III prohibits discrimination by places of public accommodation. Federal courts have extended that obligation to websites tied to businesses serving the public.
The Department of Justice has consistently stated that ADA Title III applies to websites. The DOJ has not codified a specific technical standard for private businesses, but it has pointed to WCAG as the working reference. That gap is exactly what plaintiffs’ firms exploit.
Without a federal rule spelling out conformance requirements for private businesses, the courts decide on a case-by-case basis. Most defendants settle rather than litigate.
What Triggers a Lawsuit?
Most ADA website lawsuits begin with an automated scan conducted by a plaintiff’s firm. The scan flags issues like missing alt text, color contrast issues, and unlabeled form inputs. From there, a screen reader user (often the named plaintiff) confirms the site cannot be used.
The complaint then lists specific issues a person with a disability encountered. These often include images without alternative text, keyboard traps in menus or modals, form fields without labels, insufficient color contrast on text and buttons, inaccessible PDFs, dropdown menus that cannot be operated by keyboard, and carousels and sliders that screen readers cannot interpret.
These claims are repeated across hundreds of lawsuits because the same issues appear on most unevaluated websites.
Who Is Getting Sued?
Ecommerce sites lead the volume by a wide margin. Shopify stores, WordPress and WooCommerce sites, and custom-built retail sites are filed against constantly. Restaurants with online menus and ordering, hotels with booking flows, healthcare practices, financial services, education providers, and nonprofits also see steady activity.
Business size does not protect anyone. Small businesses with limited traffic receive demand letters at the same rate as large enterprises. Plaintiffs’ firms work in volume.
How Does the Lawsuit Process Work?
Most cases follow a similar pattern. A demand letter arrives first, citing specific issues and offering to settle. If the business does not respond, a formal complaint is filed in federal court.
Settlement amounts vary, but most cases close in the mid-four to low-five figures once attorney fees are included. The settlement usually requires the business to make the website accessible, often referencing WCAG 2.1 AA, within a defined timeframe.
Litigation costs more than settling, which is why nearly every case settles. Defense attorneys with accessibility experience can sometimes negotiate better terms or push back on weak claims, but the structural incentive favors settlement.
What Can Website Owners Do to Reduce Risk?
The most reliable protection is making the website accessible in the first place. That means conducting a manual accessibility evaluation against WCAG 2.1 AA, fixing the issues identified, and keeping the site maintained over time. Automated scans only flag approximately 25% of issues, so they cannot substitute for a thorough evaluation.
A complete approach typically includes an accessibility audit conducted by qualified auditors, remediation of identified issues, validation that fixes resolved each item, and ongoing monitoring. An accessibility statement on the site demonstrates intent and provides a contact channel for users who encounter issues.
Accessible.org has worked with hundreds of businesses, including many that came in after receiving a demand letter. The pattern is consistent: the sites that were audited and remediated before any legal contact rarely face repeat claims.
The Connection to ADA Title II
While private businesses fall under Title III, public entities (state and local governments) are covered by Title II. A 2024 DOJ rule set WCAG 2.1 AA as the required standard for Title II web content, with compliance deadlines based on population size. That rule has shifted attention toward web accessibility broadly, but it does not change the legal posture for private businesses. Title III lawsuits continue at high volume regardless.
The relevant Title III video below adds useful context on the lawsuit activity.
Frequently Asked Questions
If I get a demand letter, should I settle right away?
Speak with an attorney who has handled ADA website cases before responding. Settling can be the right move, but the terms and the scope of the remediation commitment matter. An experienced defense attorney can help you understand what a fair resolution looks like for your situation.
Will an accessibility statement protect me from a lawsuit?
An accessibility statement alone will not stop a lawsuit. It can demonstrate good faith and provide a contact path for users, but plaintiffs’ firms still file cases against sites with statements. The protection comes from the actual accessibility of the website, not the page describing it.
Can the same website be sued more than once?
Yes. Different plaintiffs can file separate cases, and businesses that settle one case without remediating the site often see additional filings. The settlement typically requires remediation, but if the site stays inaccessible after the deadline, follow-on claims are possible.
How long does it take to make a website ADA compliant?
For most informational and small ecommerce sites, the audit takes two to four weeks and remediation takes another four to eight weeks depending on the development team’s availability. Larger or more complex sites take longer. The path is audit, remediation, validation, then ongoing maintenance.
The lawsuits are not slowing down. Building an accessible website is the way to stop being a target.
Contact Accessible.org to discuss your website accessibility project.
