Why Accessibility Overlays Don't Protect You From Lawsuits

If you've been sued for an ADA web accessibility violation - or you're worried about it - you've probably seen ads for overlay widgets. Install a line of JavaScript, they say, and your site becomes accessible in 48 hours. Problem solved.

It's not that simple. And in 2025, the Federal Trade Commission made that official with a million-dollar fine and a final order that changed the industry.

The FTC Case Against accessiBe: Timeline

accessiBe is the largest overlay provider, with over 350,000 websites using their widget. In January 2025, the FTC filed a complaint against them for making false claims that their AI-powered overlay could make websites compliant with WCAG accessibility standards. The FTC ordered accessiBe to pay $1 million.

In April 2025, the FTC approved the final order - making it permanent and enforceable. Here's what the FTC specifically found:

The final order prohibits accessiBe from making compliance claims unless they have "competent and reliable evidence" - meaning real testing by qualified accessibility experts, not their own internal AI. They must also clearly disclose the limitations of their product.

22.6% of Lawsuits Target Sites With Overlays

The lawsuit data tells the story even more clearly than the FTC case. In the first half of 2025, 22.6% of all ADA web accessibility lawsuits were filed against businesses that had an overlay widget installed on their site. That's nearly 1 in 4 lawsuits.

Between 2023 and 2024, over 800 businesses were sued for accessibility violations while actively running overlay widgets. Having an overlay didn't protect them - it made them a target. Plaintiff attorneys have learned to look for overlays specifically, because they know the underlying issues haven't been fixed.

Think about that: you're paying $490-$6,000 per year for a product that makes you more likely to get sued, not less.

Why Overlays Can't Fix Accessibility

This isn't a matter of overlays needing to get better. The fundamental approach doesn't work. Here's why:

They run too late

Overlays are JavaScript widgets that load after your page renders. Screen readers and assistive technologies parse the HTML when the page loads - before the overlay's JavaScript has a chance to modify anything. The overlay is trying to fix a house after the inspector has already walked through it.

They can't change your HTML structure

The most common accessibility violations - and the ones cited in lawsuits - are structural: missing heading hierarchies, unlabeled form fields, buttons built from <div> tags instead of <button>, keyboard traps in interactive components, broken focus management in modals and popups. An overlay widget cannot rewrite your page structure. It can add ARIA attributes after the fact, but it can't make a <div> behave like a real button with proper keyboard handling.

They can't test keyboard navigation

Keyboard navigation failures appear in 61% of ADA web accessibility complaints. Can you Tab to every interactive element? Does focus move correctly when a modal opens? Can you close a popup with Escape? These are behavioral issues that require actual testing and code fixes - not a JavaScript overlay.

They create new problems

Overlay widgets sometimes interfere with the assistive technologies they claim to support. Screen reader users have reported that overlays intercept keyboard shortcuts, change focus unexpectedly, and inject confusing announcements. The National Federation of the Blind issued a statement specifically criticizing overlay products for making websites harder, not easier, to use.

It's Not Just accessiBe

accessiBe got the headline because of the FTC fine, but the entire overlay industry has the same structural problem. UserWay, EqualWeb, AudioEye's widget component, and dozens of smaller overlay products all use the same approach: inject JavaScript after page load and try to patch accessibility issues from the outside.

The accessibility community has been vocal about this. Over 700 accessibility professionals signed an open letter calling for overlay vendors to stop making false compliance claims. The letter specifically named overlays as "actively harmful" to disabled users and noted that they give businesses a false sense of security.

The Real Cost of Overlays

What Actually Works

Real accessibility requires testing the actual accessibility tree - the structure that screen readers navigate, not the visual page you see. It means tabbing through every page with keyboard-only navigation. It means testing every interactive component: dropdowns, modals, forms, carousels, filters.

There are no shortcuts. But the good news is that the fixes are usually straightforward once you know what's broken - adding proper labels, fixing heading structure, making buttons actual <button> elements, ensuring keyboard navigation works. These are code changes, not widget installations.

And unlike an overlay subscription that leaves you exposed, actual fixes make your site genuinely accessible - for real users with real disabilities, and against real lawsuits.

Related Reading