In January 2025, the FTC ordered accessiBe to pay $1 million for deceptive claims that its AI overlay could make websites WCAG-compliant (FTC, 2025). That fine wasn't an isolated event. It confirmed what disability advocates and accessibility practitioners have argued for years: overlays don't work.
The numbers don't lie. 22.64% of all web accessibility lawsuits in the first half of 2025 targeted websites that already had overlay widgets installed (EcomBack, 2025). That's 456 lawsuits against sites that were supposedly "fixed." Meanwhile, 5,114 ADA digital accessibility lawsuits were filed nationwide in 2025 — a 37% increase over 2024.
This post examines the lawsuit data, the technical limitations, the regulatory actions, and what actually works instead — building on our developer's guide to web accessibility testing. No vendor pitch. Just what the research says.
TL;DR: Accessibility overlays don't prevent lawsuits — 22.6% of accessibility lawsuits in H1 2025 targeted sites with overlays installed (EcomBack, 2025). The FTC fined accessiBe $1M for deceptive compliance claims. Overlays can't modify source code, and automated tools catch only 30-50% of WCAG issues. Fix the code instead.
What Did the Data Reveal?
- Overlays don't stop lawsuits. 456 ADA lawsuits in H1 2025 targeted sites with overlay widgets installed — 22.64% of all filings (EcomBack, 2025).
- The FTC stepped in. accessiBe was fined $1 million in January 2025 for falsely claiming its AI product could make any website WCAG-compliant (FTC, 2025).
- Overlays can't fix source code. Automated testing catches only 30-50% of WCAG violations. Overlays catch even less because they operate as a JavaScript layer on top of broken HTML (Overlay Fact Sheet).
- 600+ experts agree. The Overlay Fact Sheet has been signed by over 600 accessibility professionals, including contributors to WCAG, ARIA, and HTML specs from Google, Microsoft, Apple, and Shopify (Overlay Fact Sheet).
- Lawsuits are accelerating. 5,114 ADA digital accessibility lawsuits filed in 2025 — a 37% increase from 2024. Pro se filings rose 40%, partly fueled by AI tools that help draft complaints (UsableNet, 2025).
- Europe is enforcing too. The European Accessibility Act became enforceable in June 2025 across all 27 EU member states, with fines up to 3 million euros (European Commission).
- Alternatives cost more upfront but work. Shift-left testing reduces remediation costs by up to 80% (BrowserStack, 2025). A $49/month overlay is cheaper than a $3,000 audit — until the lawsuit arrives.
Do Accessibility Overlays Actually Prevent Lawsuits?
No. 22.64% of all web accessibility lawsuits filed in H1 2025 — that's 456 cases — targeted websites that already had overlay widgets installed (EcomBack, 2025). Overlays don't serve as legal shields. In many filings, plaintiffs specifically cited the overlay as an accessibility barrier, not a solution.
The vendor-specific numbers are striking. accessiBe appeared in 258 lawsuits in 2024. UserWay showed up in 187 (UsableNet, 2025). These aren't small companies getting caught off guard — these are websites that paid for a product marketed as a compliance solution.
In 2024, 25% of lawsuits explicitly named overlays as barriers. Plaintiffs argued that overlay widgets interfered with their screen readers, created keyboard traps, or produced confusing focus behavior. Having an overlay installed didn't make these sites safer from litigation. It made them easier targets.
Citation capsule: In H1 2025, 456 ADA web accessibility lawsuits — 22.64% of all filings — targeted websites that had overlay widgets already installed, according to the EcomBack Mid-Year Report. accessiBe alone appeared in 258 lawsuits the prior year. Overlays are correlated with more legal action, not less.
Why do overlays attract lawsuits instead of preventing them?
Plaintiffs and their attorneys have started treating overlays as evidence of known accessibility problems. The logic is straightforward: if you installed an overlay, you knew your site had issues, and you chose a cosmetic fix over a real one.
Beyond that, overlays can actively create new barriers. When an overlay's JavaScript conflicts with a screen reader, it produces unpredictable behavior. Buttons that worked before might stop responding. Focus order can break. ARIA attributes injected by the overlay can clash with existing markup.
Some plaintiff law firms now specifically scan for overlay widgets before filing. It's a signal, not a defense. That's why choosing the right accessibility testing tools matters more than bolting on a widget.
The broader lawsuit trend
The total number of ADA digital accessibility lawsuits hit 5,114 in 2025 — a 37% jump from the prior year (EcomBack, 2025). eCommerce sites accounted for 70% of those filings. But lawsuits are only part of the picture.
An estimated 35,000 to 50,000 demand letters were sent in 2025 — roughly 7 to 10 for every lawsuit filed. Most of these settle quietly. The companies that settle rarely disclose the terms, which means the true financial impact of non-compliance is far larger than the lawsuit counts suggest.
What Can Overlays Actually Fix?
Automated testing tools detect only 30-50% of WCAG violations at best. Overlays miss even more because they can't modify the underlying source code (TestParty). An overlay runs as a JavaScript layer on top of broken HTML — it's patching the surface while the foundation stays cracked.
What overlays claim to do vs. what they actually do
Overlays typically promise to adjust font sizes, modify color contrast, add text labels, and provide keyboard navigation enhancements. Some of these surface-level changes do work in isolation. But they can't address the problems that cause the most real-world barriers for disabled users.
Here's what overlays cannot fix:
- Missing alt text. An overlay can try to generate alt text with AI, but AI can't reliably describe images in the right context. A photo of a team might need "Marketing team at Q3 kickoff" — not "group of people standing indoors."
- Broken ARIA implementations. If your custom dropdown uses
role="menu"incorrectly, an overlay can't restructure the DOM to fix it. - Keyboard traps. When focus gets stuck inside a modal with no escape route, an overlay can't add the missing event handlers to your source code.
- Form labels. Programmatically associating a
<label>with an<input>requires editing HTML. Overlays inject ARIA attributes that sometimes work and sometimes clash. - Semantic structure. Heading hierarchy, landmark regions, and list markup are baked into your HTML. No JavaScript layer can retroactively restructure a page that uses
<div>for everything.
The core problem is architectural. Overlays operate in the presentation layer. Accessibility lives in the markup layer. No amount of JavaScript injection can turn a
<div onclick="...">into a real<button>with proper keyboard handling, role announcements, and focus management. The fix has to happen in the source.
What 600+ experts say
Over 600 accessibility professionals signed the Overlay Fact Sheet at overlayfactsheet.com, a public statement declaring that overlays cannot make websites accessible (Overlay Fact Sheet). The signatories include contributors and editors for the WCAG, ARIA, and HTML specifications — the people who literally write the standards.
Signatories work at Google, Microsoft, Apple, BBC, Shopify, Dell, Lyft, NBC, Squarespace, and ServiceNow. They represent 16+ countries. This isn't a fringe opinion. It's the professional consensus of the people who build and define web accessibility.
Citation capsule: The Overlay Fact Sheet, signed by 600+ accessibility professionals including WCAG and ARIA specification editors from Google, Microsoft, Apple, and Shopify across 16+ countries, states that overlays do not and cannot make websites fully accessible because they cannot alter the underlying source code.
If you're looking for tools that address source code directly, our best accessibility scanning API guide compares the options that actually work at the code level.
What Did the FTC Fine Against accessiBe Reveal?
The FTC ordered accessiBe to pay $1 million in January 2025 as part of Operation AI Comply, an enforcement sweep targeting companies making deceptive AI claims (FTC, 2025). The final order was approved in April 2025. It wasn't just about the product failing — it was about how the product was marketed.
What the FTC found
The FTC's complaint laid out three specific deception claims. First, accessiBe marketed accessWidget as capable of making any website WCAG 2.1 AA compliant within 48 hours. The FTC found that claim to be false — the widget did not make all websites compliant.
Second, accessiBe paid for reviews and articles that appeared to be independent third-party evaluations. The FTC found that these pieces were deceptively formatted to hide the financial relationship. Readers thought they were getting unbiased assessments. They weren't.
Third, there's the scale problem. accessiBe's revenue hit $51.3 million in 2024 with 110,800 customers (GetLatka, 2024). The $1 million fine represents roughly 2% of annual revenue — a rounding error, not a deterrent. The FTC brought this case as part of Operation AI Comply, which targeted multiple companies for overblown AI claims. But the financial incentive to keep selling overlays remains enormous relative to the penalty.
What this signals for the industry: The FTC action established that accessibility compliance claims are subject to the same truth-in-advertising standards as any other product claim. Overlay vendors can no longer market "instant compliance" without risking federal enforcement. That's a permanent shift in the regulatory environment.
Meanwhile, a separate case is working through the courts. In July 2024, flower company BloomsyBox filed a class action against UserWay after being sued for accessibility violations despite using the overlay. The complaint alleges breach of contract, consumer fraud, and negligent misrepresentation (Lainey Feingold, 2025). Companies are now suing their own overlay vendors.
The ripple effect in Europe
The European Commission stated directly: "Overlays, or any other tools which do not ensure the website itself meets the detailed criteria of the standard, are not an appropriate solution. It is best to fix accessibility issues at their source" (Fondazione LIA, 2025). The EAA became enforceable on June 28, 2025, across all 27 EU member states, with fines up to 3 million euros (European Commission).
Within days of the enforcement date, French disability organizations filed legal notices against four major grocery retailers. The European Commission also confirmed that "automatic detection of accessibility issues is only possible for at most 30% of the WCAG Success Criteria" — a statement that directly undermines the core premise of every overlay product.
For companies operating in both the US and EU, the compliance math just changed. An overlay that doesn't satisfy ADA requirements in the US won't satisfy EAA requirements in Europe either.
Citation capsule: The FTC fined accessiBe $1 million in January 2025 for falsely claiming its AI overlay widget could make any website WCAG-compliant. The order, part of Operation AI Comply, also cited deceptively formatted paid reviews presented as independent evaluations. The final order was approved in April 2025.
How Are AI Tools Changing Accessibility Lawsuits?
Pro se ADA filings — lawsuits filed without an attorney — increased 40% in 2025, with 40% of all federal ADA Title III filings now coming from self-represented plaintiffs (Seyfarth Shaw via Accessibility.works, 2025). AI tools like ChatGPT, Copilot, and Gemini are enabling individuals to draft legal complaints and identify accessibility violations without legal training.
What's happening on the ground
Here's the pattern that's emerging. A person with a disability encounters a barrier on a website. Previously, they might file a complaint with the DOJ or contact an advocacy organization. Now, they can ask ChatGPT to draft an ADA complaint, identify which WCAG criteria are violated, and format the filing for federal court.
The quality of these AI-drafted complaints varies, but courts don't dismiss cases for imperfect formatting. And the barrier to filing has dropped from "hire a lawyer" to "have a conversation with a chatbot." That's a structural change in how accessibility enforcement works.
Does this mean we'll see a flood of frivolous lawsuits? Some attorneys argue yes. But most filings are based on real barriers that real people encountered. The underlying accessibility problems are genuine — AI just made it easier to take legal action about them.
Worth considering: We've seen teams scramble after receiving demand letters, only to discover their overlay vendor's "compliance guarantee" explicitly excluded legal indemnification in the fine print. The $49/month price tag looks different when it doesn't include legal defense.
The demand letter problem
Beyond formal lawsuits, an estimated 35,000 to 50,000 demand letters were sent in 2025 — roughly 7 to 10 for every lawsuit filed (EcomBack, 2025). Most companies settle these quietly for $5,000 to $25,000. The settlements rarely make headlines, but they add up fast.
AI tools are lowering the barrier for demand letters too. Templates are everywhere. Generative AI can customize them for specific websites and specific violations in minutes. That volume isn't shrinking.
Citation capsule: Pro se ADA filings increased 40% in 2025, with AI tools like ChatGPT enabling self-represented plaintiffs to identify WCAG violations and draft legal complaints without attorney assistance, according to Seyfarth Shaw analysis. This structural shift in filing accessibility is driving lawsuit volume alongside the 37% year-over-year increase in total ADA digital lawsuits.
What Are the Alternatives to Accessibility Overlays?
Shift-left testing — catching accessibility issues during development rather than after launch — reduces remediation costs by up to 80% (BrowserStack, 2025). The digital accessibility market reached $1,417 million in 2025 and is projected to hit $3,239 million by 2034 (Straits Research, 2025). That growth is driven by tools that actually fix problems, not ones that paint over them.
Option 1: Automated testing in your CI/CD pipeline
Automated scanning tools like axe-core run during development and flag WCAG violations before code ships. They catch the 30-50% of issues that are programmatically detectable — missing alt text, broken form labels, color contrast failures, missing language attributes.
The cost ranges from free (open-source tools like axe-core and Pa11y) to $5,000-$50,000/year for enterprise platforms with dashboards, historical tracking, and API access. That's more than a $49/month overlay. But the tool actually identifies real issues in your source code, where fixes happen.
We've compared the leading options in detail — see axe vs Lighthouse vs WAVE vs Pa11y for the tradeoffs.
Option 2: Manual expert audit
A professional accessibility audit costs $3,000 to $50,000 depending on site complexity, plus $500 to $2,000/year for ongoing reviews (TestParty). An auditor tests with real assistive technology — screen readers, switch devices, voice control. They catch the other 50-70% of issues that automation misses.
Is it expensive? Yes. But a single ADA lawsuit settlement typically runs $10,000 to $100,000 before legal fees. One audit can prevent multiple lawsuits. The math works if you actually implement the findings.
Option 3: The hybrid approach that works
The most effective strategy combines both. Automated scanning catches regressions continuously. Manual audits verify the full experience periodically. Developer training prevents new issues from being introduced.
Here's a practical breakdown of the cost comparison:
Approach | Upfront Cost | Annual Cost | What It Catches |
|---|---|---|---|
Overlay widget | $0 | $490-$950/yr | Surface-level UI adjustments only |
Automated testing (OSS) | $0 | $0 (staff time) | 30-50% of WCAG violations |
Automated testing (Enterprise) | $0-$5,000 | $5,000-$50,000/yr | 30-50% with dashboards and reporting |
Manual audit | $3,000-$50,000 | $500-$2,000/yr | Full WCAG coverage including UX |
Hybrid (automated + audit) | $3,000-$55,000 | $5,500-$52,000/yr | Maximum coverage, continuous + periodic |
The overlay costs $490-$950/year and doesn't fix anything in your code. The hybrid approach costs more but actually achieves compliance. And compliance is the whole point — otherwise, why spend anything at all?
Citation capsule: Shift-left accessibility testing reduces remediation costs by up to 80% according to BrowserStack. While overlays cost $490-$950/year and can't modify source code, a hybrid approach combining automated CI/CD scanning with periodic manual audits addresses the full range of WCAG requirements and provides actual legal protection.
What the WebAIM Million tells us about progress
The WebAIM Million study found that 94.8% of the top one million homepages had WCAG failures in 2025, with an average of 51 errors per page (WebAIM, 2025). In 2026, the trend got worse — average page elements increased to 1,437 per homepage, a 22.5% increase. And increases in ARIA code correlated with more errors, not fewer.
Here's the uncomfortable detail: sites with overlays averaged fewer detectable errors in the WebAIM scan. But WebAIM disabled overlays that manipulated WAVE results during testing. The "fewer errors" finding reflects overlay interference with testing tools, not actual accessibility improvement.
The web isn't getting more accessible through overlays. It's getting more complex, and complexity creates more opportunities for accessibility failures.
Frequently Asked Questions
Are accessibility overlays illegal?
Overlays themselves aren't illegal. But marketing them as WCAG compliance solutions can be. The FTC's $1 million fine against accessiBe targeted deceptive compliance claims, not the product's existence (FTC, 2025). Installing an overlay doesn't violate any law, but relying on one as your sole compliance strategy won't protect you from ADA lawsuits.
Do overlays help screen reader users?
Most screen reader users report that overlays make their experience worse, not better. Overlays inject JavaScript that can conflict with assistive technology, producing unpredictable behavior like broken focus order, clashing ARIA attributes, and unresponsive controls. The 600+ signatories of the Overlay Fact Sheet specifically cite these interference patterns (Overlay Fact Sheet).
How much does it cost to make a website accessible without an overlay?
Costs range from $0 for open-source automated tools like axe-core to $50,000+ for a full manual audit of a complex site (TestParty). A practical starting point: run axe-core in your CI/CD pipeline for free, fix what it catches, then budget $3,000-$10,000 for a manual audit of the issues automation can't detect.
Will the European Accessibility Act affect US companies?
Yes, if you serve EU customers. The EAA became enforceable in June 2025 across all 27 member states, with penalties up to 3 million euros (European Commission). It applies to digital products and services sold in the EU regardless of where the company is headquartered. Overlays don't satisfy EAA requirements any more than they satisfy ADA requirements.
Can AI fix accessibility issues automatically?
Not yet. AI can identify some violations and suggest fixes, but it can't reliably determine context — whether an image needs descriptive alt text or is decorative, whether a heading structure makes semantic sense, or whether a custom widget is keyboard-operable. The FTC's accessiBe case specifically addressed the gap between AI marketing claims and AI capabilities in accessibility.
The Bottom Line
The data is clear. Overlays don't prevent lawsuits — 22.6% of accessibility lawsuits in H1 2025 targeted sites that had overlays installed. They don't achieve compliance — the FTC fined the largest overlay vendor $1 million for claiming otherwise. And they don't satisfy the growing international regulatory requirements now enforceable under the European Accessibility Act.
What works is fixing your source code. Automated testing tools catch 30-50% of WCAG violations during development. Manual audits catch the rest. Shift-left testing reduces remediation costs by up to 80%. The upfront investment is higher than a $49/month widget, but the widget doesn't actually do anything.
If you're currently using an overlay, don't just remove it — replace it with a real testing strategy. Start with automated scanning in your CI/CD pipeline, then invest in a professional audit. The goal isn't passing an automated check. It's building something that works for everyone who uses it. Our accessibility testing tools comparison breaks down where to start.