There's a widget that promises to make your website accessible. Usually runs about $49 a month. You paste one line of JavaScript into your site, a small icon appears in the corner, and you're covered.
That's the pitch, but does it work?
The widget adjusts things users can already adjust through their own browser or operating system. Font sizes. Contrast. Cursor size. It cannot fix missing alt text on your images. It cannot fix forms with unlabeled fields. It cannot fix keyboard traps, broken navigation, or the structural problems buried in your code.
Those are exactly the things that trigger accessibility lawsuits.
In early 2025, the Federal Trade Commission settled with accessiBe, one of the largest overlay providers, for $1 million. The charge was deceptive marketing. The company had been telling businesses their product would make any website fully compliant within 48 hours. The FTC said those claims were false, misleading, and unsubstantiated.
Meanwhile, roughly a quarter of all web accessibility lawsuits now target websites that already have one of these widgets installed. Not protected by them. Targeted anyway.
Federal courts have been consistent on this. Installing an overlay is not a good-faith compliance effort. The underlying code still has the problems. The widget just sits on top of them.
More than 800 accessibility practitioners and disability advocates have signed a public statement saying overlays don't work as marketed. The National Federation of the Blind said the same about accessiBe specifically. These aren't fringe opinions.
None of this means accessibility is out of reach. It means there is no shortcut.
Real accessibility work happens in the code: proper heading structure, labeled form fields, keyboard-navigable menus, text alternatives for images. It takes someone who knows what they're doing. But once it's done correctly, it holds.
A widget is not that.
