The wrong answer
Why an Accessibility Widget Does Not Make You Compliant
The FTC fined the biggest overlay vendor $1 million over exactly this claim. Here is what the product can and cannot do.
Part of the Real Estate Website Accessibility guide · Last reviewed 2026-08-09
An accessibility overlay is a widget you add with one line of JavaScript, usually appearing as a small accessibility icon that opens a panel of options such as larger text or higher contrast. Vendors have sold them as instant compliance. In April 2025 the Federal Trade Commission approved a final order requiring accessiBe, one of the largest vendors, to pay $1 million over claims that its accessWidget could make any website WCAG compliant when it did not. The order also covered the company presenting third-party reviews as independent opinions while failing to disclose its connections to the reviewers. That is a federal regulator ruling on the central claim of the category.
Key takeaways
- The FTC approved a final order on 22 April 2025 requiring accessiBe to pay $1 million over deceptive claims about its accessWidget product.
- The order bars representing that an automated product can make any website WCAG compliant, or ensure continued compliance, without evidence to support it.
- The FTC also found the company deceptively formatted third-party articles and reviews to appear as independent opinions without disclosing material connections.
- An overlay runs in the visitor's browser after the page loads and infers what your markup meant, so it cannot supply information that was never there.
- Installing a widget does not stop a lawsuit, and a separate case brought by an overlay customer against its vendor was allowed to proceed in February 2026.
- Fixing the underlying markup serves every visitor and every assistive tool, which is the difference between a repair and a layer on top.
What an overlay actually is
The pitch is appealing, which is why the category grew. Paste one line of JavaScript into your website and an accessibility icon appears in the corner. Click it and a panel offers larger text, higher contrast, a readable font, and sometimes a screen reader mode. The marketing frames this as making your site compliant in minutes with no developer.
Mechanically, the widget loads in the visitor's browser after your page has arrived, inspects the page, and attempts to change it. Some products also try to guess at missing information, such as generating a description for an image using automated image recognition.
The distinction that matters is where the work happens. Your actual website, the HTML your server sends, is unchanged. Every visit re-runs a layer of guesswork on top of markup that still has the same problems underneath.
What the FTC found
This is not an argument between accessibility consultants and vendors. There is a federal enforcement action with a published order.
The Federal Trade Commission approved a final order on 22 April 2025 requiring accessiBe to pay $1 million. The FTC's case was that the company falsely represented that accessWidget could make any website compliant with the Web Content Accessibility Guidelines when the product did not make all customer websites WCAG compliant.
The order carries a second finding worth knowing, because it explains why the category looked so well reviewed. The FTC found the company deceptively formatted third-party articles and reviews so they appeared to be independent opinions, while failing to disclose its material connections to those reviewers. So some of the favourable coverage a buyer would have found while researching was not independent.
The order bars the company from representing that its automated products can make any website WCAG compliant, or ensure continued compliance, without evidence to substantiate it, and from misrepresenting endorsements as independent opinions.
Why the mechanism cannot deliver what was promised
The enforcement action tells you the claim was deceptive. The reason is more useful, because it tells you which parts of the problem an overlay can genuinely help with and which it cannot touch.
An overlay can adjust presentation. Increasing text size, raising contrast, or changing the font are visual changes to what is already there, and a widget can make them.
It cannot supply meaning that was never in the page. Consider a photograph of a kitchen with no alt text. A screen reader needs a description. The overlay does not know what is in the photograph. Automated image recognition can guess at generic content, and on a real estate site the useful description is specific: which room, what condition, which features. A guess produces plausible text that may be wrong, which is arguably worse than silence because the visitor cannot tell.
The same limit applies to structure. If your headings were chosen for size rather than hierarchy, the correct structure is a judgment about what the page means, and a script cannot recover an intention that was never expressed. If a form field has no label, the widget does not know what belongs in the box.
There is a further practical issue reported by screen reader users: an overlay that alters the page can interfere with the assistive technology the visitor already uses and has configured. Someone who relies on a screen reader daily has it set up the way they want, and a widget imposing its own behaviour on top can make a site harder to use than leaving it alone.
A widget is not a legal defence
The commercial argument for an overlay is usually risk rather than access: buy it so you do not get sued.
The evidence does not support that. There is litigation running in the other direction, brought by an overlay customer against its vendor. BloomsyBox, an online florist, subscribed to UserWay's overlay in July 2023 and was then sued in December 2023 by a blind user who could not access its website. It sued UserWay in federal court in Delaware over the vendor's advertising claims, and in February 2026 a magistrate judge recommended the case proceed.
Set that beside the FTC order and the position is clear. A business bought the product, was sued anyway, and is now suing the vendor about what the product was said to do. Buying the widget did not prevent the outcome it was purchased to prevent.
Where an overlay is not entirely useless
Being fair to the category, since the argument is stronger when it is accurate.
The presentation controls are real. A visitor with low vision who wants larger text and higher contrast on your site can get it from the panel, and that is a genuine improvement for that visitor. Some products bundle a scanning report that shows you the errors on your pages, which is useful information even if the automatic remediation is not.
The problem is what the tool is sold as. As a small convenience layer on top of a site that has been genuinely fixed, an overlay is a defensible extra. As a substitute for fixing the site, it is what the FTC took action over.
So the test to apply before buying is what the vendor claims. If they claim compliance, automatic conformance, or protection from litigation, the FTC order tells you how to read that. If they describe presentation adjustments accurately and are clear that underlying issues need fixing, you are looking at a modest tool honestly described.
What to do instead
The alternative is not necessarily expensive, and most of it is on the checklist page in this hub.
- Run a free scan and the keyboard test first, so you know the size of the problem before buying anything to solve it.
- Fix contrast, alt text, and form labels directly. These are content edits on most platforms, and they are the majority of what automated testing finds.
- Write alt text yourself for listing photos, because you know which room it is and a recognition model does not.
- Publish an accessibility statement with a phone number, so a visitor who hits a barrier can reach a person. That is the honest version of the reassurance an overlay is sold as providing.
- Ask your IDX vendor about their component, since it is the part you cannot fix and an overlay cannot fix it either.
- If the barriers are structural, treat it as a platform decision rather than something to paper over. Markup you cannot edit is the case where a rebuild resolves the underlying cause instead of layering a guess on top of it.
| Accessibility problem | Can a widget fix it? | Why |
|---|---|---|
| Text contrast too low | Partly | Presentation can be adjusted for a visitor who opens the panel |
| Text too small | Partly | Same, a visual adjustment to existing content |
| Missing alt text on a listing photo | No | The tool does not know which room it is or what condition it is in |
| Form fields with no labels | No | Nothing in the page states what belongs in the field |
| Headings used for size, not structure | No | The intended hierarchy was never expressed in the markup |
| Filters that cannot be keyboard operated | No | The controls are not real controls, and a script cannot reliably infer intent |
| Listings that only load via JavaScript | No | The content is still absent from the delivered page |
Based on the FTC's April 2025 findings about automated remediation claims and on how client-side overlays operate. Individual products differ, so judge a specific vendor by what it claims it can do.
Frequently asked questions
Do accessibility overlay widgets actually make a website ADA compliant?
No. In April 2025 the Federal Trade Commission approved a final order requiring accessiBe to pay $1 million over claims that its accessWidget could make any website WCAG compliant when it did not. The order bars representing that an automated product can make any website compliant without evidence to back the claim. An overlay adjusts presentation in the browser and cannot supply information the page never contained.
What exactly did the FTC order accessiBe to do?
The FTC approved a final order on 22 April 2025 requiring the company to pay $1 million. The order bars accessiBe from representing that its automated products can make any website WCAG compliant or ensure continued compliance without substantiating evidence, and from misrepresenting endorsements as independent opinions by impartial users or organizations, after the FTC found it had formatted third-party reviews to appear independent.
Will installing an accessibility widget stop me being sued?
There is no evidence it does. BloomsyBox subscribed to UserWay's overlay in July 2023 and was sued in December 2023 by a blind user who could not access its site, then sued UserWay over its advertising claims, with a magistrate judge recommending in February 2026 that the case proceed. A business bought the product, was sued anyway, and ended up litigating against the vendor.
Can an overlay write alt text for my listing photos?
Some products attempt it with automated image recognition, and the output is unreliable for real estate. Useful alt text on a listing photo names the room and what is notable about it, which requires knowing the property. A recognition model can identify a generic kitchen and cannot tell your visitor it is the renovated one with the island. A confident wrong description is worse than none, because the visitor cannot tell it is wrong.
Are accessibility widgets ever worth using?
As a small extra on a site that has genuinely been fixed, the presentation controls are real and some visitors will use them. The problem is buying one as a substitute for fixing the site, which is what the FTC took action over. Judge a vendor by what it claims: promises of compliance or litigation protection should be read against the April 2025 order.
Do overlays interfere with screen readers people already use?
Screen reader users have reported that overlays can conflict with the assistive technology they already run and have configured to their preferences. Someone who uses a screen reader daily has it set up deliberately, and a widget that alters the page or imposes its own reading behaviour can make a site harder to use rather than easier. This is a recurring complaint from the users the products are said to help.
What is the difference between an overlay and actually fixing the site?
An overlay runs in each visitor's browser after your page loads and tries to infer what your markup meant, leaving the underlying HTML unchanged. Fixing the site changes the HTML your server sends, so every visitor and every assistive tool gets correct information without needing to click a panel. One is a repair, the other is a layer of guesswork re-run on every visit.
My web provider included an accessibility widget. Is that enough?
Treat it as a starting point rather than a resolution. Run a free scan and the keyboard test yourself to see what remains, since the widget does not change the markup being tested. Ask your provider specifically what they fixed in the underlying code as opposed to what the widget adjusts in the browser, because those are different pieces of work and only one of them is durable.
How much should I budget for accessibility instead of buying a widget?
Start by spending nothing. Run WAVE on three pages and press Tab through your contact form, which costs an hour and tells you whether your problems are content or structure. Contrast, alt text, and form labels are usually content edits you can make in your site editor. Only after that do you know whether you need paid help, and what for.
Does Saige use an overlay widget on rebuilt sites?
No. The rebuild changes the underlying structure so pages are readable as delivered, which is the same property that lets search engines and AI assistants read them. That approach addresses the cause rather than adding a layer that guesses at it in the browser. The rebuild preview is free, so you can see the resulting structure before discussing anything else.
Related pages in this guide
Related reading
Sources
Every claim on this page that could be checked against a primary source is linked below. Where something is not publicly documented by a vendor, the page says so rather than filling the gap with an estimate.
- FTC Approves Final Order Requiring accessiBe to Pay $1 Million for Deceptive Claims (Federal Trade Commission (order approved 22 April 2025))
- BloomsyBox v. UserWay: Overlay Lawsuit (Law Office of Lainey Feingold)
- How to Meet WCAG 2.1 (Quick Reference) (World Wide Web Consortium (W3C))
- The WebAIM Million: An annual accessibility analysis of the top 1,000,000 home pages (WebAIM, Utah State University (published February 2026))