Last updated: October 5, 2026 · 3 min read · By Ali Raza
Accessibility overlays are widgets that add a toolbar or automatic adjustments on top of a website. They can offer some display options, but they do not fix the underlying code, can conflict with the assistive technology disabled people already use, and cannot guarantee compliance. In 2025 the US Federal Trade Commission finalised an order requiring one overlay provider, accessiBe, to pay $1 million over claims that its tool could make any website WCAG compliant. Fixing the site itself is the reliable approach.
Overlay vendors promise accessibility “with one line of code” for a monthly fee. For a busy business owner worried about lawsuits, that is an attractive offer.
Here is what overlays actually do, why many accessibility experts and disabled users object to them, and what to do instead.
Overlay vs real fix
| Overlay widget | Code remediation | |
|---|---|---|
| Where it works | On top of the page in the browser | In the templates, components and content |
| Missing labels and alt text | Guessed automatically, sometimes wrong | Written correctly by people |
| Keyboard and focus problems | Often not fully fixed | Fixed and tested |
| Screen reader users | Can conflict with their tools | Works with their tools |
| Compliance | Not guaranteed | Measured against WCAG and documented |
What do overlays do?
Most overlays add a toolbar with options like larger text, contrast modes and highlighted links, and run scripts that try to repair problems automatically, for example by guessing alt text or adding labels. Some of these display options can be helpful. But people who rely on assistive technology usually already have these settings on their own devices.
Why don’t overlays make a site compliant?
- Automated repair cannot understand context: it cannot know what an image means to your customers or what a confusing form is asking for.
- Many barriers are structural, such as keyboard traps, missing focus or inaccessible custom menus, and need code changes.
- The original barriers remain in your source code and in what search engines and other tools see.
- Lawsuits have been filed against websites that use overlays.
What did the FTC say?
In 2025, the US Federal Trade Commission finalised an order against accessiBe, requiring it to pay $1 million and stop claiming its product can make any website WCAG compliant unless it has evidence. The case was about marketing claims, but it confirms what accessibility specialists had said for years: no tool alone can promise compliance.
What should you do instead?
- Audit your key pages and journeys with automated and manual testing.
- Fix issues at the source, starting with templates, navigation, forms and checkout.
- Write proper alt text and link text in your content.
- Publish an accessibility statement with a contact route.
- Re-test after changes and train your editors.
Fixing templates means a single change often repairs every page that uses them, so real remediation is usually more affordable than owners expect. Start with our WCAG 2.2 AA checklist or ask our web accessibility team for a free check. For the legal background, see our guides to ADA and the European Accessibility Act.
Frequently asked questions
Do accessibility overlays make a website ADA compliant?
No tool alone can guarantee compliance. Overlays do not fix the underlying code and can conflict with assistive technology.
What did the FTC do about accessibility overlays?
In 2025 the FTC finalised an order requiring accessiBe to pay $1 million and stop claiming, without evidence, that its tool can make any website WCAG compliant.
Are all accessibility widgets bad?
Some display options can help some users, but they should never replace fixing the site's code and content.
Is fixing accessibility in code expensive?
Often less than expected, because most issues come from shared templates and components, so one fix repairs many pages.