Straight answers
Accessibility widget, or a real fix?
A widget is a script that adds a toolbar and adjusts your pages in the visitor's browser. It does not change your store's code. Here is what that means in practice, and what the US Federal Trade Commission, the European Commission and disability organisations have said about it, with a link to each.
What a widget is
An accessibility widget, also called an overlay, is a line of JavaScript added to a site. It usually shows a toolbar with options such as larger text or higher contrast, and tries to adjust the page automatically as it loads. The FTC described it like this in its complaint against one vendor:
"Accessibility overlays are not intended to permanently alter web code or design, but to permit temporary modifications to the user interface that may impact accessibility while visiting a web page."FTC complaint against accessiBe, paragraph 4
That is the whole difference. The problems a customer runs into in a checkout, such as a form field with no label or a pop-up the keyboard cannot leave, are in the code. A widget works on top of it.
Side by side
| Question | Widget | Fixing the code |
|---|---|---|
| Where it changes things | In the visitor's browser, each time a page loads | In your store's templates and code, once |
| Menus, headings, tables, images | The FTC alleged that one widget failed to make these compliant on sites using it (complaint, paragraph 9) | Fixed in the template, so every page built on it is fixed |
| Keyboard traps, missing focus, wrong image descriptions | Listed by the FTC among barriers on sites running the same widget (paragraph 77) | Found by testing with a keyboard and a screen reader, then fixed |
| The visitor's own screen reader and settings | Can interfere with them and override user settings (EDF and IAAP, 2023) | That combination is exactly what gets tested |
| Third-party parts of the purchase, such as a hosted payment page | Not reached unless they run the widget too; the FTC order requires accessiBe to tell buyers this (Provision V) | Not ours to change either. We find them and name them in the report, so you can take it up with the provider |
| Position of the European Commission | "Not an appropriate solution" | "It is best to fix accessibility issues at their source" |
| How it is paid for | A subscription. accessiBe advertised compliance "for only $490 per year", as quoted by the FTC (paragraph 37) | An audit and the fixes, then optional maintenance so a new release does not undo them |
What the FTC said
On 3 January 2025 the US Federal Trade Commission announced a proposed order against accessiBe, which sold a widget called accessWidget. The order was made final on 22 April 2025, by a 3–0 vote. It is a settlement: accessiBe neither admitted nor denied the allegations.
- The claim. That installing "one line of code" made a website compliant with 30% of WCAG's requirements immediately, and started an AI process that would make it "fully compliant with the remaining 70% of WCAG requirements within 48 hours" (complaint, paragraph 7).
- The allegation. "In a number of instances accessWidget fails or has failed to make basic and essential website components like menus, headings, tables, images, recordings, and more, compliant with WCAG" (paragraph 9). The FTC also alleged that accessiBe presented paid articles and reviews as independent.
- The order. accessiBe must pay $1 million and may not claim that its automated products can make any website WCAG-compliant, or keep it compliant as the content changes, without competent and reliable evidence.
The complaint also records what accessibility experts, including the W3C, say about testing in general: "no automated testing tool alone can determine if a website meets accessibility standards. Rather, manual human testing is required" (paragraph 78).
In the US
There is no federal regulation that requires a private online store to meet WCAG. The exposure is private lawsuits under the Americans with Disabilities Act, and settlements use WCAG 2.1 AA as the benchmark.
A widget does not take a store out of that picture. UsableNet, a company that tracks these cases and, like us, sells accessibility services, counted between 95 and 155 lawsuits every month of 2025 against companies that were using a widget on their site: 1,416 in the year, with data up to mid-December (UsableNet, 2025 year-end report).
In the EU
If you sell to consumers in the EU, the European Accessibility Act has applied since 28 June 2025. Its technical benchmark is the harmonised standard EN 301 549, which points to WCAG 2.1 AA. The European Commission's own guidance addresses widgets directly:
"Overlays, or any other tools which do not ensure the website itself meets the detailed criteria of the standard, are not an appropriate solution. It is best to fix accessibility issues at their source."European Commission, Web accessibility, updated 23 June 2026
The European Disability Forum and the International Association of Accessibility Professionals said the same in a joint statement in May 2023: overlays "do not make the website accessible or compliant with European accessibility legislation".
Is a widget ever useful?
For some visitors, yes. The European Disability Forum puts it plainly: "While this can help some people, similar features are already available in today's browsers and devices." A visitor who needs larger text or more contrast can set it once in their browser or device, for every site.
What a widget cannot do is change the code that a screen reader or a keyboard depends on. That part is fixed only by fixing it.
What fixing it involves
- Testing the whole purchase path by hand, with a keyboard and a screen reader, not only with a scanner.
- Fixing the problems in the templates, so every page built on them is fixed.
- A check in your release process, so the next update does not undo it.
Short answers
I already pay for a widget. Should I remove it?
Not before you know what it does on your store. We test the purchase path with the widget switched on and off. If it gets in the way of a screen reader or a keyboard, we recommend removing it. If it does not, it can stay while the code underneath is fixed.
Will fixing the code protect me from a lawsuit?
No technical work makes a store immune, and we do not promise that. What we deliver is the removal of specific, documented WCAG 2.1 AA failures: the benchmark that US settlements use and that the European standard points to.
Is this legal advice?
No. We are developers. Whether a law applies to your business is a question for your lawyer. We are responsible for the technical state of the store.
Do you install widgets?
No. We fix the store itself.