Website owners are sued over ADA compliance because their websites contain technical accessibility issues. Plaintiffs’ lawyers claim these issues are tantamount to discrimination under Title III of the ADA.
Title III prohibits places of public accommodation from discriminating on the basis of disability. The lawyers argue that any barrier a screen reader user encounters denies equal access, and denial of equal access is discrimination.
Most businesses settle because defending costs more than settling, so the demand letters and lawsuits keep coming.
| Factor | What It Means |
|---|---|
| The claim | Technical accessibility issues framed as discrimination under Title III of the ADA |
| Technical standard | Informally, WCAG 2.1 AA, referenced in most complaints and settlement agreements |
| Common issues cited | Missing alt text, keyboard traps, contrast issues, unlabeled form fields, inaccessible menus and carousels |
| Who gets sued | Ecommerce stores, restaurants, hotels, healthcare, professional services, nonprofits, and others |
| Typical outcome | Settlement with a remediation commitment plus attorney fees |
The Legal Foundation Being Exploited
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, and federal courts have applied that obligation to websites connected to businesses serving the public.
The Department of Justice has consistently taken the position that Title III applies to websites. What the DOJ has never done is codify a technical standard for private businesses. There is no regulation that says a website must conform to WCAG 2.1 AA. Instead, WCAG 2.1 AA is the reference point that the DOJ, courts, and plaintiffs’ lawyers all point to, which makes it the de facto standard.
That regulatory gap is what plaintiffs’ firms exploit. There is no safe harbor a business can point to, no certification that ends the inquiry, and no bright line. A complaint only needs to allege that a person with a disability encountered barriers and was denied access. Whether a missing alt attribute on a decorative image actually amounts to discrimination is almost never tested in court because nearly every case settles before the question gets answered. The firms filing these cases are counting on that.
What Triggers a Lawsuit?
Most ADA website lawsuits begin with an automated scan run by a plaintiff’s firm. The scan flags issues like missing alt text, contrast failures, and unlabeled form inputs across thousands of websites at once. From there, the named plaintiff, typically a screen reader user, visits the site and documents the barriers encountered.
The complaint then dresses each technical issue up as a denial of access. Missing alt text becomes “plaintiff could not perceive product images.” A keyboard trap becomes “plaintiff could not navigate the site.” An unlabeled form field becomes “plaintiff could not complete a purchase.” Each issue is converted into an allegation that the plaintiff was denied the full and equal enjoyment of the business’s goods and services.
The same boilerplate allegations appear across hundreds of lawsuits, often word for word, because the model is copy and paste. Many named plaintiffs have filed dozens or hundreds of cases, frequently against businesses they had no genuine intent to patronize.
Many filings also pair the Title III claim with state law claims to increase the pressure. California’s Unruh Act provides statutory damages of $4,000 per violation, and New York’s state and city human rights laws add similar leverage. This is a major reason New York, California, and Florida account for the bulk of filings.
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 because the denial-of-access claim is easiest to plead when there are products that supposedly could not be purchased. 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 matter to these firms. Small businesses with limited traffic receive demand letters at the same rate as large enterprises because the scan does not care about revenue and the settlement demand is calibrated to what a business will pay to make the case go away.
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, usually in federal court, sometimes paired with the state claims above.
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, with WCAG 2.1 AA referenced as the measure, within a defined timeframe.
The economics are the whole point. Defending a Title III case through motion practice costs more than settling, and Title III allows prevailing plaintiffs to recover attorney fees, so the longer a case runs the larger the exposure. The firms know this and price their demands accordingly. Defense attorneys with accessibility experience can sometimes negotiate better terms or push back on weak claims, but the structure rewards settlement, and that is exactly why the filings keep coming.
What Can Website Owners Do to Reduce Risk?
The most reliable protection is removing the basis for the claim. If the technical issues are not there, there is no barrier to document and nothing to dress up as discrimination. 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 a scan alone 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. An accessible website is a bad target, and these firms move on to easier ones.
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 confirmed WCAG 2.1 AA as the government’s chosen benchmark, but it did not create a rule for private businesses, and it did nothing to slow Title III filings.
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 these firms file against sites with statements all the time. The claim is built on the technical issues, so 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. Some businesses have been sued repeatedly by different plaintiffs represented by different firms over the same issues.
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 because the playbook still works: scan for technical issues, frame them as discrimination, and collect a settlement. Building an accessible website takes the playbook away.
Contact Accessible.org to discuss your website accessibility project.
