Do accessibility overlays work? Not as a route to compliance. An overlay can adjust colors, enlarge text and patch a handful of predictable issues, but it can't rewrite how your site is built. Missing form labels, broken keyboard navigation, inaccessible checkouts and images described by guesswork all stay in your source code. If you want a site that people with disabilities can actually use, and a stronger position under the ADA, the European Accessibility Act or the UK Equality Act, the fix has to happen in the code and content itself.

What an accessibility overlay actually is

An overlay is a third-party JavaScript snippet you paste into your site. When a visitor loads a page, the script runs in their browser and tries to modify what they see. Most products combine two things:

• A toolbar or widget. The familiar floating icon that opens controls for contrast, text size, cursor size, reading guides and similar settings.
• Automated "repair". Scripts, often marketed as AI, that scan the page and inject attributes such as image descriptions, ARIA labels or heading roles after the page has loaded.

Nothing changes on your server: your theme, templates and content stay exactly as they were. The overlay is a layer of guesses applied to each page view, and if the guess is wrong, or the script loads late or conflicts with a visitor's own software, the original barrier is still there.

What overlays can and can't do

Where they can help a little

The Overlay Fact Sheet, written and signed by accessibility practitioners, accepts that some fixes can be applied when the page loads. Overlays may improve conformance with a few individual WCAG provisions.

What they can't reliably fix

The same fact sheet identifies the areas where automated repair is unreliable, and they are exactly the ones that tend to block real customers:

• Image text alternatives. Software can describe a photo but can't know what it should communicate in context.
• Form labels and error handling in checkout, booking and contact forms.
• Keyboard access. Menus, filters, modals and date pickers built without keyboard support can't simply be patched from outside.
• Modern dynamic interfaces. Sites built with frameworks such as React, Angular or Vue change content in ways overlays struggle to keep up with.
• Non-HTML content. PDFs, canvas, SVG and media files are out of reach entirely.

The toolbar side has its own problem. The fact sheet calls overlay widgets "unnecessary and are poorly placed in the technology stack", because people who need larger text or higher contrast usually already have those settings in their operating system, browser or assistive technology. The joint statement by the European Disability Forum and IAAP adds that overlays can interfere with assistive technology, override users' own settings, and raise privacy concerns when they detect that a visitor uses a screen reader, which can reveal a disability.

What the evidence says

The FTC's accessiBe order

On January 3, 2025, the FTC announced a proposed order against accessiBe, alleging that claims its accessWidget tool could make any website WCAG-compliant were "false, misleading, or unsubstantiated." The agency also alleged that accessiBe formatted third-party articles and reviews so they looked like independent opinions. The Commission voted 5–0, and on April 22, 2025, it approved the final order. It requires a US$1 million payment and bars the company from claiming its automated products can make a website WCAG-compliant, or keep it compliant, without evidence. Announcing the case, Samuel Levine of the FTC's Bureau of Consumer Protection said: "Overstating a product's AI or other capabilities without adequate evidence is deceptive."

What accessibility professionals think

The Overlay Fact Sheet lists 1,048 named signatories, including WCAG and HTML contributors, assistive technology developers, lawyers and disabled users. It concludes: "No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard." In WebAIM's third survey of accessibility practitioners, with 758 responses, 67% rated overlays, plugins or widgets as not at all or not very effective. Among respondents with disabilities, that rose to 72%, and only 2.4% called them very effective. The EDF and IAAP statement puts it plainly: "Overlays do not make the website accessible or compliant with European accessibility legislation."

What regulators and lawsuit data show

The US Department of Justice's guidance on web accessibility and the ADA says automated checkers and overlays "can be helpful tools" but "need to be used carefully", and recommends pairing them with manual checks. Lawsuit data does not suggest widgets keep owners out of court either. The UsableNet 2025 year-end report reviewed more than 5,000 ADA-related digital accessibility lawsuits and concluded that "accessibility widgets did not slow litigation in 2025". For more on the US picture, see our guide to ADA website lawsuits in 2026.

Overlay vs real remediation: a side-by-side comparison

What to do instead

Real remediation follows a steady pattern:

1. Audit against WCAG 2.2 AA. Combine automated scanning with manual keyboard and screen-reader testing on your most important journeys: home, product or service pages, forms, booking and checkout. The WebAIM Million 2026 found detectable WCAG failures on 95.9% of the top one million home pages and warns that "not all conformance failures can be automatically detected".
2. Fix at the source. Start with template and component fixes that repair many pages at once, such as navigation, buttons and form fields. Then work through content: alt text, link wording, headings and color contrast.
3. Remove or reconsider the overlay. Once the code is fixed, test with the toolbar switched off; it may add little and can get in the way of assistive technology.
4. Publish an accessibility statement. Explain your standard, known limitations and how people can report a problem. For EU sales this is expected; our post on the European Accessibility Act for non-EU businesses explains why.
5. Monitor continuously. New pages, plugins and theme updates reintroduce issues. Regular re-testing keeps the gains you paid for.

This is the work our website accessibility team does every month: an audit from US$690, then monitoring and fixes through the Monitor plan at US$99/month, Care at US$249/month or Care Plus at US$499/month. No provider can promise that you will never receive a complaint or demand letter, and anyone who does is repeating the mistake the FTC acted on. What we can do is help you build a site that genuinely works for disabled visitors and keep it that way.

This article is general information, not legal advice. Please consult a lawyer about your legal obligations under the ADA, the European Accessibility Act, the UK Equality Act or any other law.

Frequently asked questions