FTC Fines accessiBe $1 Million: What It Means for Overlay Users

DEFINITION

Overlay Widget

A JavaScript plugin added to a website via a single line of code that attempts to auto-remediate accessibility issues at the browser level without changing the underlying source code. When the JavaScript fails to load due to ad blockers, browser incompatibilities, or network issues, all fixes disappear. Overlays are sold by accessiBe, UserWay, AudioEye, and EqualWeb among others.

DEFINITION

FTC Consent Order

A legally binding agreement between the Federal Trade Commission and a company that resolves an enforcement action without a court trial. The company typically does not admit wrongdoing but agrees to specific conduct requirements and financial penalties. The accessiBe consent order required a $1 million payment and imposed a 20-year compliance mandate prohibiting false marketing claims.

DEFINITION

VPAT

Voluntary Product Accessibility Template. When completed, it becomes an Accessibility Conformance Report (ACR) documenting how a product meets WCAG and Section 508 criteria. VPATs are required for U.S. federal procurement and increasingly demanded by enterprise buyers. No overlay tool generates a reliable automated VPAT - all require manual expert auditing.

DEFINITION

Source-Code Remediation

The process of fixing accessibility issues directly in a website's HTML, CSS, and JavaScript code, rather than applying a runtime JavaScript layer. Source-code fixes persist regardless of third-party services, survive subscription cancellations, and are the standard courts look for when evaluating ADA compliance claims.

The FTC Case: What Actually Happened

On January 3, 2025, the Federal Trade Commission filed an enforcement action against accessiBe Ltd., an Israeli company selling an AI-powered accessibility overlay called accessWidget. The FTC’s complaint alleged that accessiBe made false and misleading claims in its marketing - specifically that its product could make any website WCAG-compliant within 48 hours via a single line of code.

The consent order became final on April 21, 2025 after a unanimous 5-0 Commission vote. The key terms:

• $1 million civil penalty paid to the U.S. Treasury
• 20-year compliance mandate prohibiting accessiBe from claiming automated products achieve full WCAG compliance without competent and reliable evidence
• Annual reports to the FTC for 20 years documenting compliance with the order

AccessiBe’s 2024 revenue was approximately $51.3 million, making the $1 million penalty roughly 2% of annual revenue. Critics noted this may be insufficient as a deterrent for the broader overlay industry.

What the FTC Found

The FTC’s complaint documented the specific claims accessiBe made in marketing:

accessiBe advertised that accessWidget would make a website “30% compliant immediately” with the remaining “70% compliant within 48 hours” through AI processing. The FTC found this claim was false. The complaint stated the widget “fails or has failed to make basic and essential website components like menus, headings, tables, images, recordings, and more, compliant with WCAG.”

The FTC also found that accessiBe paid for reviews formatted to look independent. One blog post endorsing the product cost $1,900.

The case originated from a complaint filed by Haben Girma, a Deafblind lawyer and Harvard Law graduate, who experienced the overlay’s failures firsthand.

What the Order Does Not Do

The consent order does not make overlay products illegal. It does not prohibit accessiBe from selling accessWidget. It prohibits accessiBe specifically from marketing its products as achieving full WCAG compliance through automation alone without evidence to back that claim.

Other overlay vendors - UserWay, AudioEye, EqualWeb - are not directly bound by this order. But the FTC’s factual findings about what AI overlays can and cannot do apply broadly to the category. An overlay that genuinely achieved full WCAG compliance would be a different product than what is commercially available today.

What the Litigation Data Shows

The FTC action confirmed what lawsuit data had already established: overlay widgets do not prevent accessibility lawsuits.

In 2024, 1,023 businesses were sued for web accessibility violations while actively running overlay widgets - representing approximately 25% of all digital accessibility lawsuits that year (UsableNet 2024 Year-End Report). In 2025, the number was 983 cases (EcomBack 2025 Annual Report).

AccessiBe appeared in 258 lawsuits in 2024 specifically. UserWay appeared in 187 (WCAGsafe analysis).

The math is not subtle. A product marketed as a compliance solution that appears in hundreds of lawsuits per year is not functioning as a compliance solution.

Customer Lawsuits: Businesses Suing the Vendors

Beyond disabled users suing overlay-using websites, a second category of litigation has emerged: businesses suing the overlay vendors themselves after being sued while using their products.

Tribeca Skin Center v. accessiBe

In June 2024, Tribeca Skin Center filed a class action against accessiBe in the Southern District of New York. The allegation: Tribeca purchased an accessiBe subscription for $490 per year, received a lawsuit from a blind plaintiff anyway, and when they sought assistance from accessiBe, the company failed to provide the legal protection it marketed. The case represents a direct test of accessiBe’s marketing claims about lawsuit protection.

BloomsyBox v. UserWay

In July 2024, BloomsyBox filed suit against UserWay in the District of Delaware. The sequence: BloomsyBox installed UserWay’s overlay, got sued by a disabled user, contacted UserWay for help, was told to upgrade to a more expensive plan, then had its support ticket closed four days later without resolution. UserWay collected subscription fees, a user was still unable to use the site, a lawsuit followed, and UserWay’s response was to upsell then disengage.

These cases matter beyond their individual outcomes. They expose a gap between how overlay products are marketed - as legal protection and compliance solutions - and what they actually deliver when a lawsuit arrives.

What Courts Have Said About Overlays

Courts have addressed overlays in specific cases long before the FTC acted. The pattern is consistent.

Murphy v. Eyebobs (W.D. Pa., 2021)

A blind plaintiff sued Eyebobs, a retailer using accessiBe’s overlay. An accessibility expert submitted a 35-page declaration documenting failures across the site’s pop-ups, modals, and widgets - all areas where the overlay was supposed to remediate issues automatically.

The consent decree required Eyebobs to abandon the overlay entirely and achieve WCAG 2.1 AA compliance through source-code remediation within 24 months. The court did not accept overlay installation as evidence of good-faith compliance effort.

LightHouse for the Blind v. ADP (N.D. Cal., 2020)

This settlement was notable for explicitly naming overlay vendors. The agreement stated that “overlay solutions such as those currently provided by companies such as AudioEye and AccessiBe will not suffice to achieve Accessibility.” It was the first settlement to name overlay vendors by name as inadequate compliance measures. The ADP case established early precedent that courts and settling parties would treat overlays as insufficient remediation.

The Disability Community’s Position

The accessibility community’s opposition to overlays predates the FTC action and is documented across multiple independent organizations.

The Overlay Fact Sheet

The Overlay Fact Sheet (overlayfactsheet.com), launched in 2021 by accessibility consultant Karl Groves, has collected over 1,000 signatures from accessibility professionals worldwide. Signatories include contributors to W3C WCAG and ARIA specifications and internal accessibility experts at Google, Microsoft, Apple, BBC, Shopify, eBay, Target, and CVS Health.

The core position: “No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard.”

The technical basis: overlays inject JavaScript that manipulates the DOM at runtime. This creates conflicts with screen readers and other assistive technologies that process the DOM independently. WebAIM’s practitioner survey found 72% of disabled respondents rated overlays as “not at all” or “not very” effective. ACM ASSETS 2024 research confirmed overlays “often fail to deliver on their promises and, in many cases, increase existing challenges.”

The National Federation of the Blind

The NFB revoked accessiBe’s convention sponsorship in June 2021 and passed two formal resolutions condemning overlay practices. The NFB’s language was direct: accessiBe “engages in behavior that is harmful to the advancement of blind people in society.”

In January 2025, the NFB filed a formal comment with the FTC supporting the consent order. The NFB’s concern is not just that overlays fail technically - it is that marketing them as compliance solutions diverts attention and resources from genuine accessibility work.

The AudioEye SLAPP Suit

AudioEye sued accessibility expert Adrian Roselli in March 2023 over blog posts criticizing overlay products. The 30-page complaint was itself delivered in inaccessible paper format.

AudioEye dropped the suit in January 2024 as part of a settlement that included a $10,000 donation to the National Federation of the Blind. The outcome validated Roselli’s criticism and drew broad attention to overlay vendors’ use of litigation to suppress expert dissent.

The European Commission

The European Commission issued an official statement that accessibility overlays “are not an appropriate solution” for meeting European Accessibility Act requirements, and that “it is best to fix accessibility issues at their source.” The EAA took effect in June 2025 and applies to businesses selling products or services to EU consumers. The Commission’s position is consistent with U.S. court outcomes.

What Businesses Using Overlays Should Do Now

If your website currently uses an accessibility overlay, the FTC action and the lawsuit data create a clear decision point.

The overlay is not your compliance strategy. Courts have rejected it, the FTC has penalized the largest vendor for claiming otherwise, and 25% of all accessibility lawsuits now target sites with overlays installed. The product may serve as a user preference toolbar (allowing visitors to increase text size or adjust contrast), but that is a different function than achieving WCAG compliance.

Audit your actual source code. Tools like A11yProof scan your site against WCAG 2.1 AA criteria and surface violations in your actual HTML and CSS - not a runtime layer on top of it. A typical SMB site with 10-50 pages can complete a meaningful audit in days. Automated scanning catches 30-57% of WCAG issues by volume; the remainder require developer attention.

Fix the source code. Remediation costs for a typical SMB marketing site run $5,000-$25,000 and take one to four months (TestParty, 2025). That range overlaps with what a single settlement costs. The difference is that source-code fixes eliminate future legal exposure; settlement does not.

Document your compliance work. Keep records of scans, violations found, fixes applied, and dates. This documentation demonstrates good-faith effort - which matters if you do receive a demand letter even after remediation.

Monitor for regressions. Every content update, design change, or new feature can introduce accessibility issues. Scheduled scanning catches new violations before plaintiff attorneys do.

The $29/month A11yProof Starter plan runs automated scans on a schedule and generates violation reports your developers can act on. It is not a one-line compliance solution - the FTC has now made clear that no such thing exists. It is a tool for finding and tracking real problems in your real code.