That Little Accessibility Widget in the Corner? It’s Not Protecting You.

Every week, business owners install an accessibility plugin and feel like they’ve solved a problem. One line of code. A small monthly fee. A floating icon in the corner that signals compliance.

What they’ve actually done is painted a bullseye on their website.

This is the accessibility overlay trap, and it’s costing businesses tens of thousands of dollars in legal settlements, while failing the very people it claims to help.

The Pitch Is Irresistible

The marketing for these tools is designed for exactly the moment you feel most vulnerable. You’ve heard about ADA lawsuits. You know your website isn’t perfect. A salesperson shows up with a solution: add their JavaScript widget, and your site becomes WCAG-compliant in 48 hours, lawsuit-proof, fully inclusive. Prices range from $500 to $2,000 a year. Compared to a full remediation project, it sounds like a bargain.

Products like accessiBe, UserWay, AudioEye, and EqualWeb have built entire industries on this promise.

There’s one problem. The promise is false. In January 2025, the Federal Trade Commission confirmed it.

The FTC Called It What It Is

In April 2025, the FTC finalized a $1 million settlement with accessiBe, one of the largest and most aggressively marketed overlay vendors in the industry. The agency found that accessiBe had misrepresented what its AI-powered tool could actually do, making compliance claims that were not supported by any credible evidence. The order bars the company from making such claims for the next 20 years.

This wasn’t a technicality. The federal government, on the record, said these products cannot do what they advertise.

AccessiBe isn’t an outlier. It’s the industry leader. The others make identical claims.

Why Overlays Fail (Without the Technical Jargon)

Your website has an underlying structure, the actual code that browsers and assistive technologies read. Screen readers used by blind and low-vision users parse that code the moment your page loads.

An overlay widget doesn’t touch that code. It sits on top of it, like a coat of paint over a cracked wall. It runs after the page loads, which means it’s already too late: the screen reader has already encountered the broken structure underneath.

If your building has no accessible entrance, putting up a sign that says “accessible entrance here” with an arrow to a locked door doesn’t make your building accessible. It just makes the problem more obvious.

Automated tools, overlays included, can only detect between 20% and 40% of WCAG issues. The rest require human judgment, contextual understanding, and real-world testing. No AI widget can replicate that. Every accessibility expert working in this field agrees on this point.

The People You’re Trying to Reach? They Hate These Tools.

According to WebAIM’s Survey of Web Accessibility Practitioners, 72% of respondents with disabilities rated accessibility overlays as either “not at all effective” or “not very effective.” Only 2.4% rated them as very effective.

Some blind users have become so frustrated that they’ve installed browser extensions specifically to block overlays from loading at all, because overlays interfere with the professional screen readers they already rely on. Tools like JAWS, NVDA, and VoiceOver are sophisticated, highly configured software. An overlay that attempts to override or layer on top of them can break navigation, scramble audio output, and create an experience that is worse than no overlay at all.

More than 975 accessibility professionals have signed the Overlay Fact Sheet, a public statement declaring that overlays are not an effective means of ensuring accessibility. Signatories include accessibility leads from Google, Microsoft, Apple, Shopify, the BBC, Target, and eBay, as well as researchers from MIT, Carnegie Mellon, and Gallaudet University.

The people who built the standards, work with the standards daily, and live with the consequences of inaccessible websites are aligned: overlays do not work.

The Legal Trap No One Tells You About

In 2024, over 4,000 ADA digital accessibility lawsuits were filed in the United States. Of those, roughly 25% specifically cited accessibility widgets and overlays, not as solutions, but as barriers to access. Plaintiffs’ attorneys are pointing at the overlay as evidence of non-compliance, not protection from it.

Courts have reached consistent conclusions. In Murphy v. Eyebobs, the court allowed a lawsuit to proceed against a site using an accessiBe overlay. In Anderson v. Hy-Vee, a site running UserWay was sued anyway; the court ruled that the source code must be accessible, full stop. In a settlement involving ADP, the agreement explicitly required the company to stop using overlays and achieve genuine WCAG compliance through real remediation.

By the first half of 2025, over 300 new suits had been filed against overlay-equipped websites. Plaintiff firms use tools like BuiltWith to search for websites running specific overlay scripts. Installing an overlay doesn’t just fail to protect you; it makes you findable.

The average ADA website accessibility settlement runs between $15,000 and $50,000. Add $20,000 to $30,000 in legal fees. That’s the cost of a shortcut that typically runs $500 to $2,000 a year.

There’s Also a New Global Dimension

If your business serves customers in the European Union, the stakes just increased further. The European Accessibility Act took full effect in June 2025, requiring digital products and services sold within the EU to meet WCAG 2.1 Level AA standards. The European Commission has explicitly stated that accessibility overlays do not constitute a valid path to compliance under this legislation. Germany’s regulatory bodies have issued the same conclusion independently.

This is no longer a US-only legal risk. It is a global one.

What Actually Works

The businesses with the strongest legal and compliance position share a common approach: they fix the underlying code.

Real accessibility means building it into your website’s source: proper heading structure, form labels that are actually connected to their fields, keyboard navigation that works, images with meaningful alt text, videos with captions. These are structural fixes. They require an audit to identify what’s broken, a remediation plan to fix it, and testing with real assistive technology users to confirm it works.

This is not as complicated or as expensive as overlay vendors want you to believe. Most websites can achieve significant compliance improvements within a defined engagement. The work is concrete, verifiable, and, unlike a subscription widget, actually protects you.

Here’s the practical path:

1. Start with a professional audit. You can’t fix what you haven’t identified. A thorough WCAG audit maps every violation against the legal standard, prioritizes by risk, and gives you a clear remediation roadmap.
   
   
2. Fix the source code. Work with developers who understand accessibility, not a vendor selling a plugin. Structural fixes stay fixed.
   
   
3. Test with real users. Automated tools catch a fraction of issues. Human testing, including people who use assistive technology, catches the rest.
   
   
4. Maintain it. Accessibility isn’t a one-time checkbox. As you add content and features, the standard applies to the new work too.