Accessibility Overlays Don’t Work (And the Lawsuits Prove It)

If you’ve searched for a quick way to make your website ADA compliant, you’ve probably come across accessibility overlays. Companies like AccessiBe, UserWay, and AudioEye promise that adding a single line of code to your site will fix your accessibility problems automatically.

It sounds too good to be true. That’s because it is.

In 2025, the Federal Trade Commission fined AccessiBe $1 million for making false and deceptive claims about its AI-powered accessibility tool. The same year, a class action lawsuit was filed against UserWay by a small business that installed the overlay, got sued anyway, and discovered the vendor’s promised legal protection didn’t cover them. And data from UsableNet shows that more than 25% of all web accessibility lawsuits in 2024 targeted websites that were already using accessibility overlays.

Overlays aren’t a compliance solution. They’re a compliance risk. Here’s why, and what to do instead.

What Accessibility Overlays Actually Are

Accessibility overlays (also called widgets or plugins) are JavaScript-based tools that you add to an existing website. They sit on top of your site’s code and attempt to detect and fix accessibility problems in real time, in the user’s browser.

Most overlays offer two things: an AI-driven “auto-remediation” engine that claims to automatically fix issues like missing alt text and color contrast, and a customization toolbar that lets users adjust font size, contrast, and other display settings.

The pitch is simple: one line of code, instant compliance, no developer needed.

The problem is that the pitch is fundamentally misleading. Overlays operate on the visual surface of your website. They don’t touch your underlying source code, which is where accessibility barriers actually live. If the overlay script fails to load, gets blocked by an ad blocker, or is removed, your site instantly reverts to its original inaccessible state. It’s like painting over a crumbling wall. The cosmetic fix hides the problem but does nothing to resolve the structural issues underneath.

Why Overlays Fail WCAG 2.1 AA

The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA is the legal standard for web accessibility under both the DOJ ADA Title II rule and the HHS Section 504 rule. It’s also the standard courts reference in ADA Title III lawsuits.

WCAG 2.1 AA includes dozens of success criteria, and automated tools can only detect about 20-40% of them. The remaining 60-80% require human judgment and contextual understanding. Here are specific criteria that overlays consistently fail to address:

1.1.1 Non-text Content. Overlays can detect that an image is missing an alt attribute, but they can’t write meaningful alt text that accurately describes the image in context. AI-generated alt text is frequently generic, inaccurate, or nonsensical.

1.3.1 Info and Relationships. Visual structure must be programmatically determinable. Overlays can’t reliably fix improper heading hierarchies, missing list semantics, or table structures. A screen reader needs proper HTML tags to navigate, and overlays can only simulate them on the surface.

1.3.2 Meaningful Sequence. In multi-column layouts, the reading order must follow a logical narrative. Overlays often can’t determine the correct reading order, leaving screen readers to read across columns instead of down them.

2.4.4 Link Purpose. Overlays can’t identify and fix generic link text like “click here” or “read more” because the correct link text depends on context that requires human understanding.

4.1.2 Name, Role, Value. Interactive form fields must have accessible names, proper roles, and programmatically determinable states. Overlays frequently mislabel form controls or fail to connect labels to their fields correctly.

Keyboard navigation and focus management. Overlays can actually make keyboard navigation worse, trapping focus, altering tab order, or making focus indicators disappear. For users who rely on keyboard navigation, this doesn’t just fail to help. It creates new barriers.

The Industry Consensus: The Overlay Fact Sheet

This isn’t just our opinion. The Overlay Fact Sheet, signed by hundreds of accessibility advocates, developers, and disability organizations, states plainly that no existing overlay can make a website fully accessible. The signatories include the American Foundation for the Blind, the National Federation of the Blind, the World Institute on Disability, and the Web Accessibility Initiative.

When the organizations representing the users these tools claim to serve unanimously say they don’t work, that’s not a debate. It’s a consensus. The disability community has been clear: overlays create new barriers instead of removing existing ones, and marketing them as compliance solutions is misleading.

If your organization is relying on an overlay, you’re relying on a product that the people it claims to help have formally opposed.

The User Experience Problem

A WebAIM survey found that 72% of users with disabilities rate accessibility overlays as either ineffective or actively harmful to their ability to navigate websites. The reason is straightforward: most users who rely on assistive technology have spent significant time configuring their tools. Screen readers like JAWS and NVDA, screen magnifiers, and voice control software are deeply personalized. Overlays frequently conflict with these tools, overriding user settings, announcing content incorrectly, or breaking keyboard navigation.

Instead of helping users with disabilities, overlays often make the experience worse. They introduce their own accessibility barriers, including inaccessible toolbar controls, confusing interfaces, and redundant features that duplicate what browsers and assistive technologies already do better.

There’s also a privacy concern. Some overlays detect the presence of assistive technology on a user’s device to trigger certain features. In doing so, they effectively identify the user as having a disability, often without consent. This raises serious questions under data protection laws like GDPR and CCPA.

The Legal Reality: Overlays Attract Lawsuits, Not Prevent Them

The marketing promise is clear: install our overlay, avoid lawsuits. The reality is the opposite.

The numbers. In 2023, over 900 lawsuits were filed against companies using accessibility overlays. In 2024, 25% of all web accessibility lawsuits explicitly cited overlay-equipped websites. TestParty reported that more than 800 businesses using AccessiBe were still sued for ADA violations.

Why overlays make you a bigger target. Plaintiff attorneys use automated tools to scan for accessibility violations. These scanners often don’t recognize overlay “fixes” because the underlying code is still broken. The presence of an overlay can also be interpreted as an acknowledgment that you knew your site had accessibility problems but chose a superficial fix instead of real remediation. In some cases, the overlay itself becomes a specific barrier cited in the complaint.

The FTC action against AccessiBe. In May 2025, the FTC issued a consent order fining AccessiBe $1 million for deceptive marketing. The FTC found that AccessiBe claimed its tool could make websites “ADA compliant” and “fully accessible” when it could not. The order prohibits AccessiBe from making similar claims in the future. This is significant because it undercuts the primary marketing argument of every overlay vendor.

BloomsyBox v. UserWay. In this class action, a small business installed UserWay’s overlay based on promises of ADA compliance and up to $1 million in legal support. Six months later, the business was served with an ADA lawsuit. When they sought the promised legal support from UserWay, they were told their subscription didn’t qualify. The case highlights a critical risk: overlay vendor promises may not hold up when you actually need them.

Tribeca Skin Center v. AccessiBe. Another class action filed by a business owner alleged that AccessiBe misrepresented its product’s capabilities and failed to deliver on compliance promises. These B2B lawsuits represent a shift: the businesses that bought overlays are now suing the vendors.

The Real Cost Comparison

Organizations often choose overlays because they seem cheaper than professional remediation. The math doesn’t hold up.

A typical overlay subscription costs $490 to $1,500 per month, per site. Over three years, that’s $17,640 to $54,000. And at the end, you still have an inaccessible website, a legal liability, and nothing to show for it.

Professional remediation is a one-time investment. An audit identifies the barriers, remediation fixes the source code, and testing with real assistive technology verifies the results. The cost depends on the size and complexity of your site, but once it’s done, it’s done. You own the fix. Your source code is accessible at the foundation, not temporarily patched on the surface.

Add in the legal risk. The average ADA Title III lawsuit settlement ranges from $20,000 to $75,000, not including legal fees. The probability of being sued is higher with an overlay, not lower. The cost calculus shifts quickly.

The Off-Ramp: What to Do If You’re Already Using an Overlay

If your organization is currently using an accessibility overlay, you’re not alone. Thousands of businesses bought these tools in good faith, based on marketing claims that the FTC has now formally rejected. The question is what to do next.

Step 1: Get a real audit. An automated scan is not an audit. A proper accessibility audit combines automated testing with manual expert review, testing across multiple assistive technologies, and a documented conformance report. This tells you exactly where you stand.

Step 2: Don’t just remove the overlay. If you remove your overlay today, your site is still inaccessible. The overlay was masking problems, not fixing them. You need a remediation plan in place before you decommission it.

Step 3: Prioritize by risk. Focus on your highest-traffic pages, your most critical user workflows, and any pages that are frequent lawsuit targets (contact forms, intake forms, scheduling portals). Fix those first.

Step 4: Remediate at the source. Real accessibility fixes happen in your HTML, CSS, and JavaScript. Each barrier is identified, fixed in the code, and verified with assistive technology. This is work that requires expertise, but it produces a permanent, defensible result.

Step 5: Keep the overlay if it helps users. Some users do find the customization features helpful (font size adjustment, contrast controls). If you want to keep the widget as a user preference tool, that’s fine. Just don’t market it or rely on it as your compliance solution.