Accessibility overlays, and what the FTC actually found

What an overlay is

An accessibility overlay, sometimes called a widget, toolbar, or plugin, is a small piece of JavaScript you paste into your site. It runs in the visitor's browser and tries to adjust the page on the fly: adding an alt-text guess to an image, resizing text, changing colour contrast, tagging buttons with an accessible name, sometimes adding a floating menu of display options. Vendors typically pitch it as a fast, low-effort alternative to fixing the site's underlying HTML: install a script tag instead of hiring a developer.

That pitch is the whole appeal, and it's also the part regulators and advocates have pushed back on hardest.

The FTC's case against accessiBe

In April 2025, the US Federal Trade Commission issued a final order against accessiBe, one of the best-known overlay vendors, in Docket C-4817. The order was finalised on 21 April 2025 and required accessiBe to pay $1,000,000.

Precisely what was charged matters more than the headline number. The FTC's complaint alleged that accessiBe represented its product would make a customer's website WCAG-compliant, and would "continue to ensure accessibility and compliance with WCAG by automatically remediating any changes" made to the site afterwards, and that these representations were false or unsubstantiated. A second, separate charge concerned accessiBe presenting paid reviews as if they were independent customer opinions, which the FTC treated as deceptive.

Read the FTC's own account of the case: FTC press release, "FTC Approves Final Order Requiring accessiBe to Pay $1 Million".

This is why rule 1 of how we write this whole site is that GotAlt never claims compliance: not "WCAG compliant," not "ADA compliant," not a badge, not a seal. The accessiBe order is the clearest public illustration of what happens when a vendor makes that promise and can't back it up.

Why disability advocates object

Separately from the FTC action, blind, low-vision, and motor-disabled users and their advocacy organisations have raised a more practical objection for years: overlays don't just add features, they can interfere with the assistive technology the visitor already has running. A screen reader user typically arrives with their own screen reader configured the way they like it. An overlay that injects its own ARIA attributes, intercepts keyboard focus, or rewrites the DOM on the fly can conflict with that software rather than help it, producing extra noise, broken navigation, or behaviour the user never asked for, on top of whatever the underlying site already got wrong.

The practical upshot: a tool aimed at helping disabled visitors can, in specific cases, make the page harder to use for the very audience it targets. That's a real and recurring complaint, not a hypothetical one, and it's a large part of why "just add a widget" has become a contested claim rather than an accepted fix.

What an overlay can and can't change

An automated guess at alt text, generated without a human or a model actually looking at the image, has the same weakness whether it comes from an overlay or anywhere else: a plausible-sounding label is not the same as an accurate one. That gap between "sounds right" and "is right" is the reason GotAlt's own tools download the image file and check it, rather than pattern-matching the surrounding text. See how that works on our alt text checker.

The fair conclusion

A widget can add genuinely useful visitor-facing options (larger text, a contrast theme, a pause button), and some visitors will use and appreciate those. What it cannot do is retroactively make a page's underlying HTML accessible, and claiming that it does is exactly the representation the FTC found false or unsubstantiated in the accessiBe order above. If a site's headings are missing, its forms are unlabelled, or its reading order is broken, that has to be fixed in the markup. No script running after the fact changes what actually shipped to the browser.

This isn't legal advice, and nothing on this page should be read as a legal opinion about any specific vendor or website. If you need a compliance opinion for a real dispute or deadline, talk to a lawyer who handles accessibility law.