TL;DR

A website accessibility lawsuit is a legal claim -- usually filed under Title III of the Americans with Disabilities Act (ADA) -- alleging that a website or mobile application contains barriers that prevent people with disabilities from accessing goods, services, or information. These lawsuits typically cite failures like missing alt text, unlabeled form fields, keyboard traps, and insufficient color contrast. Filing volume hit 3,948 federal cases in 2025, a 23.84% increase over 2024, according to EcomBack's annual report. If your site is public-facing and you sell goods or services, you are a potential target.

This article is not legal advice. It is a technical walkthrough of how these lawsuits work, what actually gets cited, and what we have seen produce defensible compliance when we audit and rebuild sites for our clients.

What is a website accessibility lawsuit?

A website accessibility lawsuit is a civil action claiming that a website violates disability rights law -- most commonly Title III of the Americans with Disabilities Act, codified at 42 U.S.C. § 12182(a). The statute says:

"No individual shall be discriminated against on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation."

Plaintiffs are typically people who are blind or have low vision, though claims also come from individuals with hearing disabilities, motor impairments, and cognitive disabilities. The complaint usually describes specific barriers -- a screen reader could not parse the product page, a form had no labels, a modal dialog trapped keyboard focus -- and alleges that these barriers denied the plaintiff equal access.

These cases are overwhelmingly filed in federal court. Some are filed in state courts under parallel state laws, like New York's Human Rights Law or California's Unruh Civil Rights Act, which can also allow for statutory damages (the ADA itself does not provide monetary damages to private plaintiffs -- only injunctive relief and attorney's fees).

Why does ADA Title III apply to websites?

The short answer: because the Department of Justice (DOJ) says it does, and most federal courts agree. The longer answer involves a circuit split and a 2024 rule.

Title III of the ADA covers "places of public accommodation" -- a list of 12 categories including hotels, restaurants, retail stores, banks, hospitals, and more. The statute was written in 1990, before commercial websites existed. The question courts have wrestled with is whether a website is itself a "place of public accommodation" or whether it only falls under ADA scrutiny when connected to a physical location.

The DOJ's March 2022 guidance on web accessibility (published at ada.gov/resources/web-guidance/) makes the agency's position clear: "The Department of Justice published guidance explaining that web accessibility is covered by Title III of the ADA." The DOJ does not condition this on having a physical storefront.

There are currently three approaches among the federal circuits:

  1. No nexus required -- The 1st, 2nd, 7th, and 11th Circuits have held (or strongly signaled) that a website can be a place of public accommodation on its own, meaning web-only businesses are covered.
  2. Nexus required -- The 3rd, 5th, 6th, and 9th Circuits require a connection between the website and a physical location.
  3. Undecided -- Some circuits have not ruled definitively.

A March 2025 Minnesota District Court decision further reinforced the position that web-only businesses are subject to Title III.

The practical takeaway: if you sell anything online, take orders, provide services, or operate in a state with its own accessibility law (New York, California, Colorado), the question of whether you are covered is effectively settled against you. Even in "nexus" circuits, if you have any physical presence -- an office, a store, a warehouse that customers visit -- the nexus requirement is easily met.

The 2024 DOJ Rule for State and Local Government (Title II)

In April 2024, the DOJ published a final rule under Title II (which applies to state and local government entities, not private businesses) establishing WCAG 2.1 Level AA as the technical standard for government web content. While Title II is a separate statute, this rule signals where enforcement is headed and gives courts a concrete benchmark.

What failures get cited most often in lawsuits?

The recurring technical failures are remarkably consistent across complaints. WebAIM's 2024 analysis of the top one million home pages (webaim.org/projects/million) found that 95.9% of home pages had detectable WCAG failures.

Here are the failures we see repeatedly in complaint filings:

Missing or inadequate alt text

Images without alt attributes, or with meaningless alt text like "image1.jpg" or "photo," are the single most cited barrier. Screen readers cannot convey the purpose or content of these images. Every product image, banner, icon, and infographic needs meaningful alternative text.

Unlabeled or mislabeled form fields

When <input>, <select>, and <textarea> elements lack associated <label> elements or aria-label attributes, screen reader users cannot determine what information a field expects. This affects login forms, checkout flows, search bars, contact forms -- basically every interactive element.

Keyboard traps and missing focus management

Modal dialogs, dropdown menus, carousels, and mega-navigation that cannot be operated with a keyboard alone. A "keyboard trap" occurs when a user can tab into a component but cannot tab out without using a mouse. This is a WCAG 2.1.2 (No Keyboard Trap) Level A failure and is cited frequently because it makes sites literally unusable.

Insufficient color contrast

Text that does not meet the WCAG minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (WCAG 1.4.3, Level AA). Light gray text on white backgrounds is the classic offender. WebAIM found low contrast text on 81% of the top million home pages.

Missing or incorrect page structure

Pages without proper heading hierarchy (<h1> through <h6>), missing landmark regions (<nav>, <main>, <footer>), and empty or duplicate link text ("click here," "read more") repeated dozens of times on a page.

Missing captions and transcripts

Video content without synchronized captions and audio content without transcripts violate WCAG 1.2.2 (Captions) and 1.2.1 (Audio-only and Video-only). This is increasingly cited as video becomes a standard part of product pages and marketing.

Inaccessible pop-ups and overlays

Cookie consent banners, promotional pop-ups, and chat widgets that cannot be dismissed with a keyboard or that are not announced to screen readers. These often block the entire page for assistive technology users.

Failure WCAG Criterion Level How Common (WebAIM 2024)
Low contrast text 1.4.3 AA 81.0% of sites
Missing alt text 1.1.1 A 54.5% of sites
Missing form labels 1.3.1, 4.1.2 A 48.6% of sites
Empty links 2.4.4 A 44.6% of sites
Empty buttons 4.1.2 A 27.2% of sites
Missing document language 3.1.1 A 17.1% of sites

How do demand letters and lawsuits actually work?

Most website accessibility disputes start with a demand letter, not a filed lawsuit. Understanding the lifecycle helps you respond appropriately.

Step 1: The demand letter

A plaintiff's attorney sends a letter to the business (often the registered agent) alleging that the website violates ADA Title III and/or a state accessibility law. The letter typically includes:

  • The specific plaintiff and their disability
  • Screenshots or technical descriptions of barriers encountered
  • A reference to WCAG 2.1 or 2.2 Level AA as the applicable standard
  • A demand for remediation within 30-90 days
  • A demand for attorney's fees and, in some states, statutory damages
  • An offer to settle pre-litigation, typically for $5,000 to $25,000

Step 2: The lawsuit (if no settlement)

If the business does not respond or refuses to settle, the plaintiff files in federal or state court. The complaint mirrors the demand letter but is now a public filing. The business must respond within 21 days (federal) or face default.

Step 3: Discovery and settlement

The vast majority of these cases -- north of 90% based on public court records -- settle before trial. Settlement typically involves:

  • A cash payment ($10,000 to $100,000+ depending on company size and state)
  • A consent decree or settlement agreement requiring the business to achieve WCAG 2.1 Level AA conformance within 12-18 months
  • Ongoing monitoring, often for 2-3 years
  • Attorney's fees for the plaintiff's counsel (often $10,000 to $50,000 on top of the settlement)

Step 4: Repeat exposure

Settling one lawsuit does not immunize you from another. Different plaintiffs can file separate lawsuits. EcomBack's 2025 report noted that 125 defendants in May 2026 alone had been previously sued. Serial plaintiffs and plaintiff firms are a well-documented pattern in this space.

The 37% surge in first-half 2025 filings reflects a litigation model that is scaling, not receding. Plaintiff firms have become more efficient at identifying non-compliant sites and filing at volume.

Do accessibility overlay widgets protect you?

No. Overlay widgets -- JavaScript tools that add a toolbar to your site offering font size changes, contrast adjustments, and other surface-level modifications -- do not make your underlying code accessible. More importantly, they do not protect you from lawsuits.

EcomBack's 2025 report tracked 983 lawsuits filed against websites using an accessibility widget. AccessiBe accounted for 424 of those (43.13%), UserWay for 273 (27.77%), and AudioEye for 88 (8.95%). That is a significant increase from 2024 in nearly every month tracked.

In June 2024, the Federal Trade Commission ordered accessiBe to pay $1 million for misleading claims about its automated remediation tool. The FTC found that the company's marketing suggested its widget could make websites fully ADA compliant, which the FTC determined was deceptive.

The W3C's Web Accessibility Initiative (WAI) does not endorse any overlay product. The WAI's approach, documented at w3.org/WAI/, emphasizes building accessibility into the design and development process -- not bolting it on after the fact.

Overlay widgets can actually create new accessibility problems. They often conflict with the user's own assistive technology settings, introduce unexpected focus changes, and add JavaScript that increases page weight and breaks existing ARIA implementations.

If you currently have an overlay widget installed, it is not protecting you. It may be giving you a false sense of security while actually increasing your legal exposure.

What does defensible compliance actually look like?

"Defensible compliance" means having a documented, ongoing process that a court would find credible if you were sued. It does not mean perfection -- WCAG conformance is a target, not a permanent state, because websites change constantly. It means demonstrating good faith, structured effort, and measurable progress.

Here is what we build for clients, and what we recommend regardless of who does the work:

Conduct a full WCAG 2.2 Level AA audit. Automated scanning (we use axe-core 4.x and Lighthouse) catches roughly 30-40% of WCAG issues. Manual testing with screen readers (NVDA on Windows, VoiceOver on macOS/iOS), keyboard-only navigation, and magnification is required for the rest. An audit should produce a detailed report mapping each issue to a specific WCAG success criterion, page URL, and severity level.

Remediate by severity and legal risk. Level A failures first (these are the ones most often cited in complaints), then Level AA. Keyboard traps, missing alt text, and unlabeled forms are almost always in the complaint -- fix those first.

Publish an accessibility statement. Include the standard you are targeting (WCAG 2.2 Level AA), a contact method for reporting barriers (email and phone), and your remediation timeline. This does not prevent lawsuits, but it demonstrates good faith and gives users an alternative path.

Integrate accessibility into your development workflow. Linting rules (eslint-plugin-jsx-a11y for React, @angular-eslint for Angular), automated CI/CD tests (axe-core in Playwright or Cypress), design system components with built-in ARIA, and PR review checklists. If accessibility is only checked at launch, it degrades within weeks.

Test with real assistive technology users. Automated and manual expert testing cannot replace actual users of screen readers, switch devices, and voice control. Budget for usability testing with disabled participants at least annually.

Document everything. Keep your audit reports, remediation tickets, testing records, and training logs. If you receive a demand letter, this documentation is your primary defense.

We cover this process in depth on our web accessibility compliance service page, including how we handle WCAG 2.2 audits, remediation, and ongoing monitoring for headless and decoupled architectures.

How much does a website accessibility lawsuit cost?

The direct cost of settling a typical demand letter ranges from $5,000 to $25,000 for a small business and $25,000 to $100,000+ for a mid-size or enterprise company. But the settlement payment is only part of the cost.

Cost Component Typical Range
Demand letter settlement $5,000–$25,000
Federal lawsuit settlement $10,000–$100,000+
Plaintiff attorney fees $10,000–$50,000
Your own legal fees $15,000–$75,000
Court-ordered remediation $20,000–$150,000+
State statutory damages (CA Unruh) $4,000 per violation
Ongoing monitoring (2-3 years) $5,000–$15,000/year

California's Unruh Civil Rights Act is particularly expensive because it provides minimum statutory damages of $4,000 per violation per visit. A plaintiff who visited your site multiple times and encountered multiple barriers can stack these.

Compare these costs to proactive compliance. A thorough WCAG 2.2 audit for a mid-size site (50-200 pages, custom components) typically runs $5,000 to $20,000. Remediation depends on the codebase but ranges from $10,000 to $75,000 for a full rebuild of non-compliant components. Ongoing monitoring is $3,000 to $10,000 per year. The math is straightforward.

Which industries and states see the most lawsuits?

Retail and e-commerce lead by a wide margin, followed by restaurants/food service, travel/hospitality, healthcare, banking, and entertainment. This tracks with the types of businesses that have the most public-facing transactional websites.

Geographically, EcomBack's 2025 data shows heavy concentration:

State 2025 Lawsuits Share
New York 1,108 28.06%
Florida 950 24.06%
California 787 19.93%
Illinois 576 14.59%
Minnesota 160 4.05%
Pennsylvania 101 2.56%
All others 181 4.58%

New York and Florida account for more than half of all filings. This is partly due to favorable plaintiff laws in those states, partly due to plaintiff firm concentration, and partly due to court familiarity with these cases leading to faster docket movement.

In the first half of 2025, 36% of sued companies had annual revenue exceeding $25 million, up from 33% in 2024. Plaintiff firms are increasingly targeting larger companies with more resources to settle. But smaller businesses are still hit -- they just make up a smaller share of the total.

These three references come up constantly and are often confused. Here is what each actually is:

ADA Title III (42 U.S.C. § 12181-12189)

The federal law prohibiting disability discrimination by private businesses that are "places of public accommodation." It does not specify a technical standard for websites. Courts and the DOJ have pointed to WCAG as the appropriate benchmark, but the statute itself simply requires "full and equal enjoyment."

WCAG 2.2 (W3C Recommendation, October 2023)

The Web Content Accessibility Guidelines, published by the World Wide Web Consortium's Web Accessibility Initiative (W3C WAI). WCAG 2.2 has three conformance levels: A (minimum), AA (the standard most laws reference), and AAA (aspirational for most sites). WCAG 2.2 added 9 new success criteria on top of WCAG 2.1, mostly addressing cognitive accessibility and mobile interaction patterns. The DOJ's 2024 Title II rule references WCAG 2.1 Level AA, but courts in Title III cases have begun citing 2.2.

Section 508 (29 U.S.C. § 794d)

A federal law that applies to federal agencies and organizations receiving federal funding. The Section 508 refresh of 2017 incorporated WCAG 2.0 Level AA by reference. If you are a private business that does not contract with the federal government, Section 508 does not directly apply to you -- but it is often mentioned alongside ADA Title III because the technical requirements overlap.

Standard Applies To Technical Requirement Enforcement
ADA Title III Private businesses (places of public accommodation) No specific standard named; courts reference WCAG Private lawsuits, DOJ enforcement
WCAG 2.2 Referenced by courts and DOJ Levels A, AA, AAA Not directly enforceable; used as benchmark
Section 508 Federal agencies, federal contractors WCAG 2.0 Level AA Federal procurement, complaints
DOJ Title II Rule (2024) State/local government WCAG 2.1 Level AA DOJ enforcement, private lawsuits

How to build an accessibility compliance program that holds up

This is not a one-time project. Websites change -- new pages, new features, new content, redesigns, third-party widget updates. Compliance degrades unless it is built into how you operate.

1. Start with an honest baseline

Run automated scans with axe-core or Lighthouse on every template and high-traffic page. Then conduct manual testing: keyboard navigation of every interactive component, screen reader testing of every form and checkout flow, color contrast checking of every text/background combination. Document the results.

Not all WCAG failures carry equal weight. A missing lang attribute on your <html> tag is a failure, but it is unlikely to be the centerpiece of a lawsuit. A checkout flow that cannot be completed with a keyboard will be. Prioritize barriers that prevent task completion.

3. Fix the architecture, not just the symptoms

If your React component library has an inaccessible modal component, fixing one instance does not fix the 47 other places that modal appears. Fix the component. Fix the design system token that produces low-contrast text. Fix the CMS template that outputs images without alt text fields. Systemic fixes prevent regression.

4. Automate what you can

Add axe-core assertions to your end-to-end tests in Playwright or Cypress. Run pa11y-ci against your sitemap in CI/CD. Flag contrast violations in your design tool (Figma's Stark plugin, for example). These tools catch about 30-40% of issues automatically, which frees your manual testing budget for the other 60-70%.

5. Train your content team

Developers can build accessible components, but content editors can still create inaccessible pages by uploading images without alt text, embedding videos without captions, or creating links that say "click here." Build guardrails into your CMS -- required alt text fields, caption upload requirements, link text validation.

6. Establish a feedback channel

Your accessibility statement should include a real email address and phone number monitored by someone who can actually triage and fix issues. If a user reports a barrier and you fix it promptly, that interaction can become evidence of good faith rather than evidence of a violation.

7. Schedule recurring audits

Quarterly automated scans, annual manual audits, and user testing at least once a year. Keep records of every audit and every remediation action taken.

If you need help building this kind of program -- particularly for headless architectures on Next.js, Nuxt, or Astro where the CMS, front end, and API layer all need independent accessibility attention -- our web accessibility compliance team does exactly this.

FAQ

Can a website-only business be sued under ADA Title III?

In most circuits, yes. The 1st, 2nd, 7th, and 11th Circuits have held that websites can be places of public accommodation without a physical location. A March 2025 Minnesota District Court ruling reinforced this. Even in "nexus" circuits, most businesses have some physical presence.

Does WCAG compliance guarantee I won't be sued?

No. WCAG conformance reduces your risk significantly and gives you a strong defense, but it does not prevent someone from filing a complaint. The goal is defensible compliance -- documented evidence that you are meeting or actively working toward WCAG 2.2 Level AA.

How long does it take to make a website WCAG 2.2 compliant?

For a mid-size site with 50-200 pages and custom components, expect 8-16 weeks for a full audit and initial remediation. Larger sites or those with legacy codebases can take 6-12 months. Ongoing compliance is indefinite -- it is a continuous process.

Are accessibility overlays a valid legal defense?

No. EcomBack's 2025 report documented 983 lawsuits filed against sites using overlay widgets. The FTC fined accessiBe $1 million for misleading compliance claims. Courts have not accepted overlay usage as a defense.

What damages can a plaintiff recover in a website accessibility lawsuit?

Under federal ADA Title III, plaintiffs can recover injunctive relief (forcing you to fix the site) and attorney's fees, but not monetary damages. Under state laws like California's Unruh Act, statutory damages of $4,000 per violation per visit apply. New York Human Rights Law also allows damages.

Do I need to hire a lawyer if I get a demand letter?

Yes. Demand letters have deadlines and legal implications. An attorney experienced in ADA defense can evaluate the claims, negotiate settlement terms, and ensure any remediation agreement is reasonable. Do not ignore a demand letter -- default judgments are real.

Is Section 508 the same as ADA compliance?

No. Section 508 applies to federal agencies and federal contractors. ADA Title III applies to private businesses. They reference similar technical standards (WCAG), but their scope, enforcement mechanisms, and legal requirements differ.

What is the most common plaintiff complaint?

Screen reader incompatibility. The majority of website accessibility lawsuits are filed by plaintiffs who are blind or have low vision and use screen readers like JAWS, NVDA, or VoiceOver. Missing alt text and unlabeled form fields are the most frequently cited specific barriers.