Web accessibility litigation has moved from a niche legal concern to one of the most active areas of ADA enforcement in the United States. In 2025, federal courts processed more than 3,100 website accessibility cases — a 27% jump from the prior year — and industry analysts expect that number to climb again in 2026. The question for businesses is no longer whether this risk is real, but how much exposure they are carrying right now.
⚖️ The Legal Landscape: How We Got Here
The Americans with Disabilities Act (ADA), enacted in 1990, prohibits discrimination against people with disabilities in places of public accommodation under Title III. For most of its history, "public accommodation" meant physical spaces. The explosion of e-commerce and digital services forced courts to answer a harder question: does a website qualify?
Courts have largely answered yes — and with each successive ruling, the plaintiff bar has grown more aggressive. The legal foundation underpinning today's wave of litigation was built case by case over the past decade, and it is now firmly established.
The Governing Legal Standard
Most courts now apply one of two theories to web accessibility claims. Under the "nexus" theory, a website is covered by the ADA when it has a sufficient connection to a physical place of accommodation (a brick-and-mortar store, a restaurant, a hotel). Under the broader "place of public accommodation" theory adopted by some circuits, any website open to the general public may be covered regardless of whether the business has a physical location.
Neither theory requires the plaintiff to have visited the physical location. In most circuits, a disabled user who was unable to use a website — or who encountered barriers in the attempt — has standing to sue.
📋 Landmark Cases That Shaped the Law
The following cases define the current legal environment. Every business operating a website should understand their holdings.
The National Federation of the Blind sued Target Corporation, alleging that its website was inaccessible to blind users who relied on screen readers, blocking them from shopping independently online — a service freely available to sighted customers.
Outcome: Target settled for approximately $6 million into a class fund, plus attorneys' fees. The consent decree mandated WCAG compliance, a three-year NFB monitoring period, and mandatory web accessibility training for Target's developers. This case established that a retailer's website — as a gateway to its goods and services — is a covered "place of public accommodation" under Title III of the ADA.
Significance: Often cited as the case that opened the floodgates for web accessibility litigation. It confirmed that websites serving as commercial storefronts carry the same obligations as physical stores.
↗ Source: WhoIsAccessible — Largest Web Accessibility LawsuitsThe National Association of the Deaf sued Netflix, alleging that the streaming platform's Watch Instantly service lacked closed captions on most of its content — effectively barring Deaf and hard-of-hearing subscribers from accessing what sighted, hearing users enjoyed.
Outcome: Netflix settled, paying $755,000 in attorneys' fees and agreeing by consent decree to add closed captions to 100% of its streaming library within two years. The Massachusetts federal court rejected Netflix's primary argument — that the ADA applies only to physical locations — holding that a digital subscription service may qualify as a place of public accommodation.
Significance: Extended ADA coverage to pure-play digital services with no physical storefront, dramatically broadening the scope of litigation risk for streaming, SaaS, and app-based businesses.
↗ Source: WhoIsAccessible — Largest Web Accessibility LawsuitsHarvard's extensive library of online course videos and educational content lacked accurate, complete captions — rendering it inaccessible to Deaf and hard-of-hearing users. The NAD argued that Harvard's online offerings constitute a place of public accommodation under both the ADA and Section 504 of the Rehabilitation Act.
Outcome: Harvard settled in 2020 for over $1.5 million in attorneys' fees and agreed to caption all university-sponsored online content, implement a formal accessibility policy, and appoint a dedicated accessibility coordinator.
Significance: Confirmed that universities' publicly accessible digital content — not just their physical campuses — must be accessible. Frequently cited in cases targeting EdTech platforms and online course providers.
↗ Source: Level Access — ADA Title III Lawsuits: Companies SuedGuillermo Robles, who is blind, sued Domino's after being unable to use the company's website and mobile app with his screen reader to order a pizza — even after multiple attempts. Domino's argued that applying the ADA to its website was unconstitutionally vague given the absence of DOJ regulations specifying a web accessibility standard.
Ninth Circuit Ruling: The court held that Title III of the ADA applies to Domino's website and mobile app because they function as gateways to the physical goods and services offered at Domino's restaurants. The absence of specific DOJ regulations did not excuse compliance.
Supreme Court: In October 2019, SCOTUS declined to hear Domino's petition for certiorari — leaving the Ninth Circuit's ruling in place and signaling that the Court was not prepared to limit ADA coverage of commercial websites. The case settled in 2022.
Significance: This is the most-cited modern web accessibility case in the country. The Supreme Court's refusal to intervene effectively ratified the Ninth Circuit's "nexus" doctrine and triggered an immediate and lasting surge in filings nationwide.
↗ Source: Law.com — With SCOTUS Declining Domino's Case, Lawyers Expect New Wave of ADA Suits ↗ Full Opinion: Robles v. Domino's Pizza, LLC — Justia 9th CircuitJuan Carlos Gil, who is legally blind, sued Winn-Dixie after being unable to access the grocery chain's website with his screen reader — preventing him from refilling prescriptions and loading coupons online. The trial court found for the plaintiff and awarded $250,000 in damages.
11th Circuit: Reversed the trial court on appeal, holding that Winn-Dixie's website — while beneficial — was not itself a "place of public accommodation" under the ADA because its stores remained physically accessible. The ruling created a circuit split with the Ninth Circuit's Domino's holding, a tension that remains unresolved.
Significance: The 11th Circuit split illustrates that ADA web liability is still not uniform across the country. Businesses operating in Florida, Georgia, and Alabama may face a different legal standard than those in California. Courts in New York, Illinois, and most other circuits continue to apply a plaintiff-friendly standard.
↗ Source: National Law Review — 11th Circuit on Gil v. Winn-Dixie ↗ Source: Know-the-ADA — Gil v. Winn-Dixie: A Landmark CaseThe NFB sued H&R Block after finding that its tax preparation website and mobile apps were incompatible with screen readers, preventing blind users from preparing their own tax returns — services that sighted users could access freely online.
Outcome: H&R Block settled for $100,000 and agreed to bring its website and mobile apps into WCAG 2.0 Level AA compliance, appoint a full-time web accessibility coordinator, and conduct annual accessibility audits for a three-year period.
↗ Source: WhoIsAccessible — Largest Web Accessibility LawsuitsA class action lawsuit alleged that Fashion Nova's e-commerce website was systematically unusable with screen readers, depriving blind and visually impaired users from independently browsing, selecting, and purchasing clothing — a discrimination claim against one of the country's largest online fashion retailers.
Outcome: Fashion Nova settled for $5.15 million — the largest web accessibility settlement in recent reported history — along with injunctive relief requiring comprehensive WCAG remediation across its platform.
Significance: Signals that class action aggregation of web accessibility claims against high-traffic e-commerce sites is fully viable and extremely expensive. Sets a new benchmark for what plaintiffs will seek in demand letters and at negotiation.
↗ Source: WCAGsafe — ADA Lawsuit Statistics 2025–2026Screen reader users sued the LA Community College District over inaccessible websites, databases, and course software that prevented blind and visually impaired students from accessing educational resources on equal terms with sighted peers. A jury found 14 separate ADA violations.
Outcome: The Ninth Circuit reinstated the jury's verdict on appeal in 2026 after a lower-court ruling had vacated it. The District agreed to a $242,500 settlement and a comprehensive remediation plan encompassing websites, learning management systems, and procurement standards for future digital tools.
Significance: A decisive reminder that public educational institutions — including community colleges — carry full ADA web accessibility obligations, and that juries can and will find multiple discrete violations within a single digital environment.
↗ Source: 508 Blueprint — ADA Website Lawsuit TrackerThe Federal Trade Commission took action against accessiBe, a widely-used accessibility overlay vendor that marketed its automated widget as a guaranteed solution for ADA and WCAG compliance. The FTC found these claims to be deceptive, as the overlay frequently failed to remediate the barriers that screen reader users actually encounter.
Outcome: accessiBe settled with the FTC for $1 million in 2025 and was required to stop making unsubstantiated compliance guarantees.
Critical Warning for Businesses: The FTC action confirms what accessibility experts have said for years — overlay widgets do not provide legal protection and may actually increase litigation exposure. accessiBe appeared in 258 federal lawsuits in 2024 alone. Websites using overlays as their primary accessibility strategy should reassess immediately.
↗ Source: WCAGsafe — ADA Lawsuit Statistics 2025–2026 ↗ Source: DarrowEverett LLP — ADA Web Accessibility Litigation InsightsMary Conner, who is blind, sued Parkwood Entertainment — the company behind Beyoncé's official website — alleging that beyonce.com lacked image alternative text, had inaccessible navigation menus, and included purchase functions that could not be operated via keyboard alone, preventing her from buying merchandise independently.
Outcome: Settled within months of filing. The case drew wide media attention and underscored that no brand — regardless of size, profile, or consumer goodwill — is immune from accessibility litigation.
↗ Source: Level Access — ADA Title III Lawsuits🏛️ The Regulatory Push: DOJ's Final Rule
⚠️ DOJ Final Rule — ADA Title II Web Accessibility (2024)
In April 2024, the Department of Justice finalized a rule requiring all state and local government entities to make their websites and mobile apps conform to WCAG 2.1 Level AA — the globally recognized web accessibility standard. Compliance deadlines vary by entity size, with larger governments required to comply first.
In April 2026, DOJ issued an interim final rule extending compliance dates for smaller governmental entities due to implementation costs — but explicitly noted that litigation risk and court enforcement obligations remain unchanged in the interim.
The Title II rule applies directly to government; it does not mandate WCAG compliance for private businesses under Title III. However, courts and plaintiffs routinely cite WCAG 2.1 AA as the de facto benchmark in private litigation, and DOJ's adoption of that standard in the regulatory sphere significantly strengthens those arguments.
↗ ADA.gov — Fact Sheet: New Rule on Web Content Accessibility (2024) ↗ Federal Register — Extension of Compliance Dates (April 2026)📊 2025–2026 Litigation by the Numbers
The scale of web accessibility litigation has transformed it from a specialty practice area into a mainstream enforcement mechanism. These are the numbers driving that transformation:
Total Federal ADA Filings
Federal courts processed 8,667 ADA Title III lawsuits in 2025 — a figure that represents a tripling of the 2,722 cases filed in 2013, and that has remained broadly stable in the 8,000–8,800 band since the 2021 peak of 11,452 cases. Of those, 3,117 specifically targeted web accessibility — a 27% increase from 2024's 2,452 web cases, and representing 36% of all ADA Title III federal filings.
↗ ADA Title III Blog — Federal Lawsuit Filings: 8,667 in 2025 ↗ ADA Title III Blog — Web Accessibility Filings Bounce Back in 2025Geographic Hotspots
Litigation is concentrated in a handful of states. In the first half of 2025 for web cases, New York led with 637 cases (31.6%), followed by Florida with 487 cases (24.2%) — nearly double its 2024 total. Illinois saw a dramatic 746% year-over-year increase in web accessibility filings, attributed to plaintiff attorneys migrating from New York courts that have imposed more rigorous standing requirements.
↗ DarrowEverett LLP — ADA Web Accessibility Litigation Insights 2025What a Lawsuit Actually Costs
🔍 The Six Violations That Drive 96% of Failures
Web Accessibility In Mind's (WebAIM) annual analysis of the top one million homepages found that 96% of homepages fail at least one WCAG 2 criterion. More strikingly, the vast majority of failures are attributable to just six categories of defect — the same defects that appear again and again in court complaints:
These are not obscure edge cases. They are elementary, well-documented requirements that appear in WCAG 2.0 and 2.1 Level A and AA. Plaintiffs' counsel scan for these defects in minutes using automated tools — the same tools your team can run before anyone files a demand letter.
↗ WCAGsafe — WCAG Violation Statistics🏭 Which Industries Are Being Targeted?
Web accessibility lawsuits are distributed unevenly across industry sectors. In H1 2025, four industries accounted for more than 90% of all web accessibility filings:
| Industry | H1 2025 Cases | Share of Total | Risk Level |
|---|---|---|---|
| Restaurants & Food & Beverage | 614 | 30.5% | 🔴 High |
| Fashion & Apparel | 580 | 28.8% | 🔴 High |
| Beauty & Skincare | 179 | 8.9% | 🔴 High |
| Healthcare | 144 | 7.1% | 🔴 High |
| E-Commerce (General) | Broad | Significant | 🟡 Medium-High |
| Education / EdTech | Growing | Growing | 🟡 Medium-High |
The Shopify platform accounted for 32.4% of all web accessibility lawsuits filed in H1 2025 — making it the single most-targeted technology stack. If your store runs on Shopify or a similar e-commerce platform, your exposure is statistically significant.
↗ DarrowEverett LLP — 2025 ADA Web Accessibility Litigation Insights ↗ WCAGsafe — Platform & Industry Breakdown 2025⚠️ The "One-Click Fix" That Keeps Landing Companies in Court
Picture this. A blind user opens your website with their screen reader — the software they depend on every single day to browse the internet, fill out forms, and make purchases online. They're greeted by a small floating button that announces "Accessibility Mode Enabled." They activate it. And then... nothing works. The checkout button still has no label. The product images still have no descriptions. The navigation still can't be reached by keyboard. The form fields are still invisible to their screen reader.
The widget promised a fully accessible experience. What it delivered was a floating button, a reassuring animation — and an inaccessible page underneath. The blind user leaves. Then they file a complaint. Then a lawyer sends a demand letter.
This is not a hypothetical. This is exactly what happened to businesses that bought into the promise of automated overlay widgets — JavaScript add-ons that claim to make any website accessible by running on top of the existing code without touching the underlying structure. The FTC called it deceptive. Plaintiffs called it a lawsuit. Courts called it not a defense.
In 2025, the Federal Trade Commission fined accessiBe — the largest overlay vendor in the country — $1 million for making compliance claims its product could not support. The agency's findings were unambiguous: the widget did not reliably make websites accessible to users of assistive technologies. accessiBe simultaneously appeared in 258 federal lawsuits that same year. UserWay, the second-largest overlay vendor, appeared in 187 additional federal lawsuits in 2024.
Plaintiffs' attorneys now specifically scan for overlay-dependent sites, because they know the compliance defense is weak and the cases settle fast. An overlay installed on a broken website is still a broken website — and courts know the difference. Genuine WCAG conformance requires fixing the underlying code: the HTML structure, the ARIA labels, the keyboard paths, the color contrast values. A client-side JavaScript layer applied on top of non-compliant code cannot repair what wasn't built right in the first place.
If your current accessibility strategy relies on an overlay widget as its primary or only layer of protection, you should treat that as an open risk — not a closed one.
↗ WCAGsafe — Overlay Widget Litigation Data → See What's Actually Broken on Your Site — WCAGScan.net✅ What Your Organization Should Do Right Now
The litigation environment is not going to soften. Every credible forecast for 2026 and beyond projects continued growth in web accessibility filings. The good news: the most common violations are fixable, and proactive remediation is far less expensive than reactive legal defense.
The first and most actionable step is knowing where you stand. A comprehensive WCAG scan identifies every barrier on your site before a plaintiff's attorney does — giving you the roadmap, the timeline, and the documentation to demonstrate good-faith compliance effort, which courts have consistently treated favorably even when full compliance is not yet achieved.
Remediation priorities should address the six high-frequency violation categories first: contrast ratios, image alt text, form labels, link and button text, and the HTML lang attribute. These are also the easiest fixes — most can be deployed in days by any front-end developer without a site redesign.
Beyond automated scanning, businesses should establish an Accessibility Statement, designate an internal accessibility point of contact, and build WCAG review into the QA gate for every new feature deployment. Courts look favorably on organizations that demonstrate ongoing, structured accessibility programs — even imperfect ones — versus organizations with no program at all.
🔎 See Where Your Site Lines Up — Free, No Commitment
Before you can fix anything, you need to know what's broken. WCAGScan will crawl up to 5 pages of your site at no charge — starting from your homepage and following its links — and show you exactly where your site stands against the WCAG 2.1 AA standard that courts and regulators use as the benchmark for ADA compliance.
📄 The POUR Report: Your Accessibility Scorecard
Every WCAGScan audit produces a POUR Report — a structured breakdown of your site's compliance organized around the four core principles that define the WCAG standard. POUR is not just an acronym; it is the architectural foundation on which every WCAG success criterion is built, and it is the framework courts and auditors use to evaluate whether a digital experience is genuinely accessible.
Perceivable
Information and UI components must be presentable in ways all users can perceive — including those who cannot see images, hear audio, or distinguish colors.
Operable
Every control, link, and navigation element must be fully operable by keyboard alone — because many disabled users cannot use a mouse at all.
Understandable
Content and UI behavior must be predictable and clear — readable by screen readers, free of jargon traps, and consistent in how controls respond.
Robust
Content must be structured so that current and future assistive technologies — screen readers, voice control, braille displays — can reliably interpret it.
📊 What the POUR Report Shows You
Rather than a raw list of hundreds of violations, the POUR Report gives you a per-principle score for each scanned page — so you can see at a glance which pillar is letting you down and where. A site that scores poorly on Perceivable has image and media problems. One that fails Operable almost certainly has keyboard-accessibility issues that are among the most litigated defects in ADA complaints. Understandable failures often surface in forms and error messages. Robust failures indicate structural HTML problems that break screen readers entirely.
Sample POUR Report output from a 5-page free scan. Your results will vary based on your site's structure and current code.
The POUR breakdown is the document you share with your development team, your compliance auditor, or your attorney when you need to demonstrate that you have identified your gaps and are working systematically to close them. It gives remediation work a clear priority order — and it is far more actionable than a raw violation dump.
🛠️ The Corrected Code Report: Don't Just Find It — Fix It
Most accessibility scanners stop at the violation. WCAGScan goes one step further: for every barrier we detect, we generate a Corrected Code Report that shows your developers exactly what the broken code looks like today — and exactly what the corrected, WCAG-compliant code should look like instead.
This is the difference between handing your team a citation and handing them the answer key. The Corrected Code Report eliminates the research step — developers don't need to look up the WCAG criterion, interpret what it means for their specific code pattern, or guess at the fix. The compliant replacement is right there, ready to apply.
The Corrected Code Report covers every page in your scan. Each finding includes the WCAG criterion number, the severity level (A, AA, or AAA), the exact line of code responsible, and the compliant replacement. For teams without dedicated accessibility specialists, this report alone can cut remediation time by more than half — because the hard interpretive work is already done.
For organizations that need to document their remediation effort for legal or compliance purposes, the Corrected Code Report also serves as an audit trail: it shows what was found, when it was found, and what corrective action was specified. That kind of documented diligence carries real weight in ADA litigation.
Know Your Accessibility Risk Before a Plaintiff Does
Get a free scan of your website. WCAGScan checks up to 5 pages against WCAG 2.1 AA, generates your POUR Report, and shows you the Corrected Code for every violation we find — no credit card, no setup, results by email in minutes.
Get My Free Scan View a Sample POUR Report📚 Sources & Citations
- ADA Title III Blog — "ADA Title III Federal Lawsuit Filings Fall Slightly to 8,667 in 2025" (February 2026)
- ADA Title III Blog — "Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025" (March 2026)
- DarrowEverett LLP — "The Rising Tide of ADA Website Accessibility Litigation: 2025 Insights"
- WCAGsafe — "ADA Lawsuit Statistics 2025–2026: Data & Trends"
- Level Access — "ADA Title III Lawsuits: Companies Sued Over Web Accessibility"
- WhoIsAccessible — "Top 5 Largest Web Accessibility Lawsuits"
- Law.com / Legaltech News — "SCOTUS Declines Domino's Case; Lawyers Expect New Wave of ADA Suits" (2019)
- Justia — Robles v. Domino's Pizza, LLC, 9th Circuit Opinion (2019)
- National Law Review — "ADA Does Not Require Websites Be Accessible, 11th Circuit Holds" (Gil v. Winn-Dixie)
- Know-the-ADA — "Gil v. Winn-Dixie Stores: A Landmark Case in Digital Accessibility"
- 508 Blueprint — "ADA Website Lawsuit Tracker: Real Cases + Settlements (2026)"
- ADA.gov — "Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps" (2024)
- Federal Register — "Extension of Compliance Dates for ADA Title II Web Accessibility Rule" (April 2026)
- Level Access — "Web Accessibility Lawsuits: 2026 Trends & How to Reduce Risk"
- Accessible.org — "2026 ADA Website Compliance Predictions: More Lawsuits, AI Has Big Impact"
- ADA Quick Scan — "ADA Website Lawsuit News: 8,667 Cases in 2025 & What's Coming in 2026"