Why an accessibility widget will not protect your Shopify store, Gersen Medina

What a widget actually does

An accessibility widget, also sold as an overlay or an accessibility plug-in, is a JavaScript file loaded into every page of the store. It usually does two things. It shows a floating button that opens a panel with settings such as larger text, a high-contrast mode, a bigger cursor, or paused animations. And it tries to patch the page after it loads: guessing alternative text for images, adding ARIA attributes to elements it recognizes, and adjusting some keyboard behavior.

Everything it does happens at runtime, in the visitor's browser, on top of whatever the theme rendered. The theme's code, the app's code and the content you wrote stay exactly as they were.

What it leaves untouched

Variant pickers and color swatches built with elements that ignore the keyboard
Icon buttons with no accessible name: the cart, the search, the menu toggle, the close button on a drawer
Form fields with placeholder text instead of a label: search, newsletter, contact, discount code
Focus order and focus visibility, which come from the theme's markup and CSS
Markup injected by apps: reviews, pop-ups, chat, size guides, upsells
Alternative text on product images, which the widget guesses and often gets wrong, when the real description is in your product data
Color contrast in the theme palette; a contrast mode in the panel does not change the default the plaintiff's tester sees

There is a second problem. Screen reader users already run their own assistive technology. A script that rewrites the page under them can produce double announcements, moved focus and controls that stop working, which is why many of those users disable widgets on sight.

What the numbers say

In EcomBack's report on the first quarter of 2026, 265 of the ADA website lawsuits it tracked, 25.55% of the total, were filed against sites that already had an accessibility widget installed. The widget did not stop the letter, and in many of those cases it was named in the complaint.

On January 3, 2025, the Federal Trade Commission announced an order requiring accessiBe to pay $1 million over claims that its accessWidget product could make any website compliant with WCAG. The FTC's complaint said the product "did not make all user websites WCAG-compliant and these claims were therefore false, misleading, or unsubstantiated." That is the regulator saying, about the best-known widget on the market, what a screen reader test shows in minutes.

What a widget looks like from the plaintiff's side

The tester opens your store with a screen reader and hits the same unlabeled buttons and the same keyboard traps as before, because the code is the same. The widget's floating button is one more unlabeled control on the page in some implementations. And a widget on a store with the failures still in place shows that the merchant knew accessibility was an issue and chose a script over a fix, which is not the argument you want your attorney to have to answer.

What remediation in the theme does instead

Changes the Liquid, HTML, CSS and JavaScript of the theme, so the fix is in the page every visitor gets, with no extra layer
Gives every control an accessible name, every field a label, every image the right alternative text from your product data
Makes menus, drawers, variant pickers and the cart work with a keyboard and a screen reader, tested with the same tools the plaintiff's expert uses
Produces a dated record of what changed, which is what the response to the letter needs to show. The code for the ten most common fixes is in the 10 WCAG failures in almost every Shopify lawsuit.

The full process, the failures that come up in almost every Shopify store, and the deliverables are on the Shopify accessibility remediation service page. If you received a letter, start with how the response window works; if you were already sued, with what happens after a Shopify store is sued.

Frequently asked questions

Is a widget better than nothing?

For the lawsuit exposure, no. The failures a plaintiff's tester finds with a screen reader are in the theme's code, and the widget leaves that code as it is. The money and the weeks spent on a widget are better spent on an audit and on fixing the theme.

Do widgets help some users?

Some features, like larger text or a high-contrast mode, help some people. Operating systems and browsers already provide those, and the users who rely on them usually have them set up. What those users cannot work around is an unlabeled button or a variant picker that ignores the keyboard, and the widget does not fix either.

What about accessibility apps in the Shopify App Store?

If the app injects a toolbar and a script that patches the page at runtime, it is a widget and the same limits apply. Apps that help you write alt text for product images or check content before publishing are a different category and can be useful alongside remediation.

I already have a widget and just received a letter. Should I remove it?

Not on your own and not mid-case. Tell your attorney it is there, get the audit, remediate the theme, and decide with your attorney whether to remove it. Once the code is fixed, the widget has nothing left to do.

Does removing the widget make the store less accessible?

Not if the theme has been remediated. Accessibility comes from the markup, the labels, the focus order and the contrast in the code. When those are right, a screen reader user gets a working store without any extra layer.

Start with the letter

If your store has a widget and a letter arrived anyway, send the letter and your store URL to gersen@gersenmedina.com. Gersen reads every message himself and replies with the scope for the audit and the next step.

Gersen Medina is a Shopify accessibility specialist who remediates ADA and WCAG 2.2 issues on Shopify stores that have received demand letters or lawsuits. Working with U.S. companies since 2014, his remediation work has helped dozens of merchants avoid hundreds of thousands of dollars in accessibility litigation exposure. About Gersen