Why 800+ Businesses with AccessiBe Were Still Sued

AccessiBe promised automated ADA compliance. The reality: over 800 businesses using AccessiBe and similar overlay widgets were sued in 2023-2024. The FTC fined AccessiBe $1 million in April 2025 for deceptive marketing claims about their product's ability to make websites accessible. Courts have consistently rejected overlay installation as evidence of ADA compliance.

Understanding why overlays fail isn't about vendor criticism—it's about protecting your business from the same outcome. The technical limitations are fundamental, not fixable through better execution.

Key Takeaways

The data reveals a pattern that should concern any business relying on accessibility overlays.

• 800+ overlay users sued in 2023-2024—more than 25% of all digital accessibility lawsuits
• $1 million FTC fine against AccessiBe for "false, misleading, or unsubstantiated" claims
• <1% of TestParty customers sued while using source code remediation
• Courts reject overlay defenses in multiple documented rulings
• NFB and 700+ experts formally oppose overlay tools
• Overlays don't fix code that screen readers actually parse

The Problem: Overlays Fail at the Source Code Level

The failure of accessibility overlays isn't about AccessiBe specifically—it's about the fundamental approach. All overlay widgets share the same technical limitation.

How Overlays Work

Overlay widgets inject JavaScript that runs after your page loads. The script attempts to modify your website by adding a toolbar for user preferences, injecting ARIA attributes, modifying CSS properties, and applying automated "fixes" to detected issues.

These modifications happen in the browser's rendered DOM. They don't change your actual source code.

Why Screen Readers Don't See the Fixes

Screen readers like JAWS, NVDA, and VoiceOver interact with your HTML source code. They parse the Document Object Model to build an accessibility tree—a structured representation of your page's elements, relationships, and states.

This parsing happens when the page loads. Overlay JavaScript executes after the page loads. By the time the overlay attempts its modifications, screen readers have already built their understanding of your page. The timing is fundamentally wrong.

Even if timing weren't an issue, certain problems can't be fixed through JavaScript injection at all.

What Overlays Cannot Fix

Some accessibility violations require actual source code changes that overlays fundamentally cannot provide.

Form label associations require proper HTML structure: ```html <!-- This requires source code change --> <label for="email">Email address</label> <input type="email" id="email">

<!-- Overlays can only inject aria-label, which is inferior --> <input type="email" aria-label="Email address"> ```

The aria-label injection doesn't create the programmatic association screen readers need. It doesn't provide a visible label for users with cognitive disabilities. It's a band-aid, not a fix.

Semantic structure requires proper heading hierarchy throughout your templates—not JavaScript that attempts to reorder elements after the fact.

Keyboard navigation requires actual code fixes to tab order, focus management, and interactive component behavior. If a modal traps keyboard focus, no overlay can repair the underlying navigation logic.

Color contrast cannot be reliably fixed by JavaScript CSS modifications that may conflict with your existing styles and break visual design.

The Evidence: 800+ Lawsuits

The lawsuit data comes from TestParty research based on Court Listener records. The findings are conclusive.

The Numbers

Over 800 businesses using overlay widgets like AccessiBe, UserWay, and EqualWeb were sued in 2023-2024. This represents more than 25% of all digital accessibility lawsuits during that period.

Installing an overlay provided no legal protection. Businesses with overlays were sued at rates equal to or exceeding businesses with no accessibility solution at all.

Repeat Lawsuits

Many overlay users were sued multiple times. Levain Bakery experienced this directly—they were sued while AccessiBe was installed, settled, and then were sued again while still using the overlay.

VP of Technology Gustavo Cardona explained: "We had a couple lawsuits with AccessiBe... a temporary solution. We know overlays aren't permanent fixes."

Why Lawsuits Continue

Plaintiff attorneys know overlays don't work. When they scan potential lawsuit targets, an overlay provides zero deterrent. The underlying accessibility violations remain detectable because they remain unfixed in the source code.

A business with AccessiBe installed and fundamental accessibility violations is just as viable a lawsuit target as a business with no accessibility solution at all.

The Evidence: Court Rulings

Courts have directly addressed overlay effectiveness in multiple cases.

Rejection as Compliance Evidence

Defendants have argued that their AccessiBe installation demonstrates good faith compliance efforts. Courts have rejected this argument repeatedly.

The rationale is consistent: installing software that claims to fix accessibility issues doesn't demonstrate actual accessibility. When expert testing shows continued barriers, the software's marketing claims are irrelevant to the legal question of whether the website is accessible.

Settlement Requirements

Settlements in accessibility lawsuits routinely require removal of overlay widgets. This isn't coincidental. Plaintiffs' accessibility experts document that overlays interfere with assistive technologies rather than helping.

Levain Bakery's settlement required human auditors—not overlay widgets. As Cardona noted: "As part of our settlement, we have to retain human auditors. The solution? For me to remove AccessiBe is better, truthfully."

The Evidence: FTC Enforcement

Federal regulatory action confirmed what the accessibility community had documented for years.

The $1 Million Fine

In January 2025, the Federal Trade Commission announced action against AccessiBe for making "false, misleading, or unsubstantiated" claims about their product's ability to achieve ADA compliance.

The final order, approved in April 2025, required AccessiBe to pay $1 million. The FTC specifically found that AccessiBe's marketing claims "were not supported by competent and reliable evidence."

What the FTC Found

The complaint documented AccessiBe claiming their overlay could make websites ADA compliant and WCAG conformant when evidence showed it could not. The enforcement action addresses the core deception: promising compliance that the technology cannot deliver.

Samuel Levine, Director of the FTC's Bureau of Consumer Protection, stated: "Overstating a product's AI or other capabilities without adequate evidence is deceptive, and the FTC will act to stop it."

The Evidence: Expert Opposition

The accessibility community has been clear and consistent in opposing overlay tools.

National Federation of the Blind

The NFB's 2021 resolution stated that AccessiBe "currently engages in behavior that is harmful to the advancement of blind people in society."

The resolution specifically addressed overlay providers making "misleading, unproven, and unethical claims which falsely inflate the value and effectiveness of their technology."

The NFB also noted that overlays "may actually make navigation more difficult" for users with disabilities—the tools sometimes interfere with assistive technologies rather than helping.

Overlay Fact Sheet

Over 700 accessibility professionals signed the Overlay Fact Sheet opposing overlay tools.

Signatories include experts from Google, Microsoft, Apple, Shopify, BBC, eBay, Target, CVS Health, Dell, and Lyft. Academic signatories come from MIT, Carnegie Mellon, Syracuse, and Gallaudet University.

The statement is direct: overlays "do not repair the underlying problems with inaccessible websites."

Disability Rights Attorneys

Lainey Feingold, a prominent disability rights attorney, has documented overlay failures extensively. Her analysis shows overlay installation provides no legal protection—courts evaluate actual accessibility, not installed software.

The Solution: Source Code Remediation

While overlays attempt surface modifications, source code remediation fixes actual code—the code screen readers interact with.

How Source Code Remediation Works

TestParty provides source code remediation through a structured process.

Scanning: Spotlight crawls your entire website daily, testing against WCAG 2.2 AA criteria. This identifies all violations—missing alt text, form label issues, contrast failures, keyboard navigation problems.

Analysis: Accessibility experts review scan findings. They understand e-commerce context—checkout flows, product catalogs, promotional content. Expert judgment determines how to implement fixes correctly.

Remediation: Experts create actual code fixes. For Shopify, that's Liquid template modifications. For custom sites, appropriate HTML/CSS/JavaScript changes. These are permanent changes to your source code.

Delivery: Fixes arrive via GitHub pull requests. Your team reviews the changes, understands what's being modified, and merges when ready. You maintain control.

Verification: Expert audits confirm fixes work correctly. Screen reader testing and keyboard navigation verification catch issues automated tools miss.

The Track Record

<1% of TestParty customers have been sued while using the platform. This represents over 250 months of collective customer engagement across e-commerce brands.

The difference is the approach: TestParty fixes actual source code. Screen readers encounter genuinely accessible HTML. There are no violations to sue over because the violations are fixed.

Businesses That Made the Switch

Multiple businesses switched from AccessiBe to source code remediation after experiencing overlay failures.

Levain Bakery

Levain used AccessiBe when they received lawsuits—multiple times. Their settlement required human auditors.

After switching to TestParty, Levain went from 1,708 accessibility errors to zero. Ongoing maintenance requires just 15 minutes monthly. No subsequent legal issues.

"We had a couple lawsuits with AccessiBe... a temporary solution. We know overlays aren't permanent fixes."

UNTUCKit

UNTUCKit founder Chris Riccobono experienced the overlay problem firsthand. "Got the legal complaint while working with an overlay widget," he noted.

After switching to TestParty, UNTUCKit fixed 24,000+ errors. The partnership has continued 18+ months with just 15 minutes monthly maintenance.

Thread

Thread, an 8-figure e-commerce brand, saw overlay costs escalate from $50/month to $1,000/month while accessibility issues remained unresolved.

After switching to TestParty, they achieved WCAG 2.2 AA compliance across all templates. Monthly maintenance requires less than 1 hour. "For me, the big thing with TestParty is just ease and peace of mind."

What to Do If You're Using AccessiBe

If you currently use AccessiBe or another overlay widget, here's the path forward.

Step 1: Understand Your Current State

Run free tools like WAVE or axe DevTools on your site with the overlay disabled. You'll see the underlying violations that the overlay hasn't fixed—because it can't.

Step 2: Remove the Overlay

The NFB noted overlays may make navigation more difficult for users with disabilities. Removing the overlay can improve accessibility immediately for some users.

Your settlement—if you're sued—will likely require overlay removal anyway. Most settlements require source code remediation, not overlay continuation.

Step 3: Engage Source Code Remediation

TestParty connects via GitHub to your codebase. Comprehensive scanning identifies all WCAG violations. Expert remediation begins with priority fixes—checkout, high-traffic templates, critical conversion paths.

Step 4: Achieve Genuine Compliance

Most businesses reach WCAG 2.2 AA compliance in 14-30 days with source code remediation. Cozy Earth fixed 8,000+ issues in 2 weeks. TUSHY achieved compliance in 30 days with a 4-person team.

Daily scanning catches new issues. Monthly audits verify continued conformance.

Frequently Asked Questions

Why were so many AccessiBe users sued?

Over 800 businesses using AccessiBe and similar overlays were sued because the technology doesn't fix actual accessibility issues. Screen readers parse source code before overlay JavaScript executes. Courts evaluate actual accessibility, not installed software. The FTC confirmed AccessiBe's claims about achieving compliance were "not supported by competent and reliable evidence."

Does AccessiBe provide legal protection?

No. Courts have rejected overlay installation as evidence of ADA compliance in multiple rulings. Defendants who argued their AccessiBe installation demonstrated good faith compliance were still found liable. The FTC's $1 million fine specifically addressed AccessiBe's false claims about ADA compliance capability.

Why doesn't AccessiBe fix accessibility issues?

AccessiBe injects JavaScript that runs after your page loads. Screen readers parse your HTML source code when the page loads—before AccessiBe executes. The modifications arrive too late. Additionally, many accessibility issues require source code changes that JavaScript injection cannot provide: proper form label associations, semantic heading structure, keyboard navigation fixes.

What's the difference between overlays and source code remediation?

Overlays inject JavaScript that modifies your rendered page without changing actual code. Source code remediation fixes your actual HTML/CSS to achieve genuine compliance. Over 800 overlay users were sued in 2023-2024; <1% of TestParty customers using source code remediation have been sued. Screen readers interact with source code—this is why only source code remediation works.

How can I tell if AccessiBe is working on my site?

Test your site with the overlay disabled using free tools like WAVE or axe DevTools. The violations you see are the ones screen readers encounter—because overlays don't fix source code. Also test with an actual screen reader (NVDA is free for Windows). If navigation is difficult with the overlay enabled, the NFB's concern about overlays making things worse may apply to your site.

Should I remove AccessiBe immediately?

Yes. The FTC documented that AccessiBe's compliance claims are false. Courts reject overlay installation as legal protection. The NFB notes overlays may make navigation more difficult. Removing the overlay prepares you for genuine compliance through source code remediation, which is what settlements typically require anyway.

Related Resources

For more information on overlay failures and source code remediation:

• The Death of Accessibility Overlays — Industry analysis
• Accessibility Widget Lawsuits: The Truth — Lawsuit documentation
• TestParty vs AccessiBe — Detailed comparison
• Best Alternative to AccessiBe — Alternatives guide
• ADA Lawsuit Defense: Source Code Approach — Legal protection strategy

Humans + AI = this article. Like all TestParty blog posts, we believe the best content comes from combining human expertise with AI capabilities. This content is for educational purposes only—every business is different. Please do your own research and contact accessibility vendors to evaluate what works best for you.