Why an overlay widget doesn't fix your theme
Published · 5 min read
If you have searched for "make my store accessible", you have seen the offer: add one line of JavaScript and a toolbar appears on every page, with buttons for bigger text, higher contrast or a "screen reader mode". It sounds like the quickest fix there is. This article explains what these overlay widgets actually change, what they leave in place, what people who work in accessibility say about them, and what to do instead.
What an overlay is
An accessibility overlay is a third-party script that runs in the visitor's browser after your page loads. It usually does two things:
- Adds a toolbar with display options such as text size, spacing, contrast or a reading guide.
- Tries to repair the page automatically, for example by guessing labels for unlabeled buttons or writing alt text for images, often with AI.
Your theme's code stays exactly as it was. Every time a page loads, the script runs again and applies its changes on top.
What it cannot change
Most barriers that stop shoppers live in the structure of the page: the HTML your theme outputs and the JavaScript that drives menus, drawers and forms. A script that guesses after the fact has limits here.
- Keyboard journeys. If the cart drawer cannot be closed with the keyboard, or focus jumps to the top of the page when a filter changes, a toolbar does not rebuild that behavior.
- Names that need context. An icon button that opens the cart and one that removes an item can look the same to a script. Guessing the wrong name is worse than no name, because the shopper hears something confident and wrong.
- Images. Automatic alt text can describe what a photo looks like; it cannot know which detail a shopper needs (the fabric, the size of the pocket, which color is shown).
- Assistive technology users already have their tools. People who use screen readers, magnifiers or voice control set them up the way they need. A second set of controls on your site can get in the way of the ones they rely on.
The shoppers these barriers affect most are the ones an overlay is meant to help: keyboard and screen reader users.
A quick test anyone can do: unplug your mouse and try to buy something with the Tab, Enter and arrow keys only. Where you get stuck, your shoppers get stuck too, toolbar or not.
What practitioners say
In WebAIM's Survey of Web Accessibility Practitioners (conducted January 2021, 758 responses), 67% of respondents rated overlays and similar tools as not at all or not very effective. Among respondents with disabilities, the figure was 72%. The survey notes that its sample was not controlled, so read it as the view of the people who answered, not of every practitioner.
The Overlay Fact Sheet is a statement signed by more than 1,000 accessibility practitioners and advocates, including people who have contributed to web standards. It is an expression of community opinion rather than data, and it is clear about where its signatories stand on overlays marketed as an automated solution.
Advertising claims and the FTC
In January 2025 the US Federal Trade Commission announced a proposed order against accessiBe, an overlay vendor. The FTC alleged that the company made misleading or unsubstantiated claims that its AI product could make any website meet the WCAG guidelines, and that it presented articles and reviews as independent without disclosing its connections to them. In April 2025 the FTC approved the final order, which prohibits misleading claims and requires the company to pay $1 million.
That case was about advertising claims. It is a reason to read any promise of an automated, one-line fix carefully, whoever makes it.
What the law expects, in general terms
This article does not give legal advice, and rules differ by country. Two general points are worth knowing:
- In the US, the Department of Justice's guidance on web accessibility and the ADA (March 2022) says businesses open to the public should make their websites accessible and have flexibility in how they do so.
- In the EU, the European Accessibility Act sets accessibility requirements for many online stores, with an exemption for microenterprises (see our EAA article).
Neither points to a toolbar as the way to get there. Both are about whether people with disabilities can actually use the service.
What to do instead
- Test. Run an automated scan to find the common issues quickly. A scan is not an audit, so have a person test what tools can't: keyboard journeys, screen readers, zoom, forms.
- Fix in the theme. Add the missing labels, names and alt text in your theme's templates and product data, fix focus in drawers and pop-ups, adjust colors in the theme settings. Fixed once in a template, an issue is usually fixed on every page that uses it.
- Check on a preview first. Make changes on a copy of your theme (or a staging site on WooCommerce), test them, then publish.
- Keep checking. Apps and theme updates bring new issues. Regular scans catch the ones automated tests can find, so they don't sit there for months.
If you already use an overlay, removing it is your decision. Fixing the underlying issues in your theme is what makes the difference for shoppers either way.
Sources
- WebAIM, Survey of Web Accessibility Practitioners #3
- Overlay Fact Sheet
- FTC press release, 3 January 2025 and final order, 22 April 2025
- US Department of Justice, Guidance on Web Accessibility and the ADA
- W3C WAI, Involving Users in Evaluating Web Accessibility
This article is general information, not legal advice. For your obligations, talk to a lawyer.