Accessibility overlays vs real fixes: what actually works.

What are accessibility overlays?

Accessibility overlays are third-party scripts you add to a website with one line of code. They usually show an accessibility icon that opens a toolbar with options such as larger text, higher contrast, dyslexia-friendly fonts or pausing animations. Many also claim to use AI to detect and repair accessibility problems automatically.

The pitch is appealing: install a widget, become compliant, and move on. For a business worried about accessibility lawsuits, a monthly subscription can look much cheaper than an audit and remediation project.

The problem is that the pitch doesn't hold up. Here are five reasons accessibility overlays fail, and what works instead.

1. Overlays don't fix the underlying code

An overlay runs in the visitor's browser after the page loads. It can change some things on the fly, but the source code, the thing assistive technology and search engines actually read, stays exactly the same.

Many of the most serious accessibility barriers can't be reliably repaired by a script. A form with no programmatic labels, a menu that can't be opened with a keyboard, a modal that traps focus, or a checkout that times out without warning all need changes to the website itself.

2. Automated detection misses most real problems

Overlays rely on automated detection, and automated testing can only identify part of the issues WCAG covers. A script can tell that an image has no alt text. It can't reliably tell whether the alt text it generates is accurate, or whether the image needs a description at all.

The same applies to headings, link text, error messages and reading order. These need human judgement about meaning and context, which is exactly what automated tools lack.

3. Many disabled users find overlays get in the way

People who rely on assistive technology already have it configured the way they need: screen readers, magnifiers, voice control and browser settings. An overlay that adds its own toolbar or changes how the page behaves can conflict with those tools.

Disabled users and accessibility professionals have been among the strongest critics. Hundreds of practitioners have signed the Overlay Fact Sheet (opens in a new tab), which explains the problems in detail and asks vendors to stop claiming overlays make sites compliant.

4. Overlays don't protect you legally

Installing an overlay doesn't stop accessibility complaints or lawsuits. Lawsuit trackers have recorded many cases filed against websites that already had an overlay installed, because the barriers the plaintiff hit were still there.

Regulators have also taken notice. In 2025 the US Federal Trade Commission finalised an order requiring overlay vendor accessiBe to pay $1 million over allegations that it misrepresented its tool's ability to make websites WCAG compliant. You can read the details in the FTC's announcement (opens in a new tab).

This article is general information, not legal advice. Talk to a qualified lawyer about your specific situation.

5. Overlays create ongoing cost without progress

An overlay is a subscription. You pay every month, and when you stop, you're back where you started, because nothing about the website has changed. Meanwhile, the real issues stay in your templates and spread to every new page your team publishes.

Real fixes work the other way. Once a template is fixed, every page built from it benefits, and the cost of accessibility falls over time.

What real accessibility fixes look like

Real accessibility work starts with an audit and ends with a website that's accessible by design. It's less mysterious than overlay marketing suggests.

1. Audit. Automated scans plus manual testing with a keyboard and screen readers, against WCAG 2.2 AA.
2. Prioritise. Rank issues by impact, starting with barriers that stop people completing key tasks such as contacting you or checking out.
3. Fix the source. Repair templates, components, plugins and content, so fixes apply everywhere.
4. Verify. Re-test each fix with the same tools and assistive technology.
5. Maintain. Train editors, test new features, and re-audit periodically so new content doesn't undo the work.
6. Document. Publish an honest accessibility statement that explains your standard, known issues and how to get help.

For a standard 5-10 page website, an audit typically takes us around 2-3 days, and many fixes are quicker than people expect.

Are accessibility overlays ever useful?

Some personalisation features, such as text resizing or contrast modes, can be helpful to some visitors. But modern browsers and operating systems already offer these, and visitors who need them usually have them switched on.

If you do keep an overlay, treat it as a small extra, never as a substitute for fixing the website, and never describe it as making your site compliant. The W3C Web Accessibility Initiative (opens in a new tab) is a reliable, vendor-neutral place to learn what accessibility actually requires.

The short version

Accessibility overlays promise compliance in one line of code, but they don't fix the code, they miss most real problems, and they can make things worse for the people they're meant to help. Fix the website itself, test with real assistive technology, and keep it accessible as it grows.

Frequently asked questions

Are accessibility overlays illegal?

No. Installing one isn't illegal. The problem is relying on one, or claiming it makes your website compliant, when the underlying barriers are still there.

Will an overlay protect me from an ADA lawsuit?

There's no guarantee. Lawsuits have been filed against websites that already had overlays installed, because the barriers people encountered were still present in the code.

What should I do if I already use an overlay?

Start an accessibility audit of the website itself, and fix the issues it finds in your templates and content. Stop describing the overlay as making your site compliant, and decide later whether it still adds any value.

Is there an official ADA certification for websites?

No. There is no official ADA certification for websites. WCAG AA conformance, supported by testing and documentation, is the benchmark most commonly used.

How long does it take to fix accessibility properly?

It depends on the size of the site and what the audit finds. For a standard 5-10 page website, the audit takes around 2-3 days, and many fixes to shared templates are quicker than people expect.