Do accessibility overlay widgets protect you from the Equality Act?

No. An overlay widget, the little accessibility icon in the corner of a page, doesn't make your website meet the Equality Act 2010. The law cares whether disabled people can actually use your service, and overlays leave the barriers in your code where they are.

Last reviewed . About 5 minutes to read.

Written by Anthony Paton, a web accessibility auditor and DHS Trusted Tester.

The short answer

  • Overlays don't change your code. Keyboard traps, broken forms and pop-ups a screen reader can't escape are still there.
  • Their fixes are guesses. Auto-generated labels and image descriptions are often wrong.
  • The duty stays with you. If a customer can't book or buy, the claim is against your business, not the widget supplier.
  • What helps: a manual audit against WCAG 2.2 AA, a fix list, and a retest.

What an overlay actually does

An overlay is a script you paste into your site. It usually adds a toolbar with options such as bigger text, higher contrast, a dyslexia font or pausing animations. Some also try to repair the page automatically, for example by guessing image descriptions or adding labels to buttons.

The toolbar features mostly duplicate settings disabled people already have in their browser, phone or operating system. The automatic repairs are made by software that can't see what your page is meant to do.

What the Equality Act asks of you

If you provide goods or services to the public, the Equality Act 2010 requires you to make reasonable adjustments so disabled people aren't put at a substantial disadvantage. The duty is anticipatory: you're expected to think ahead, not wait for a complaint. Your website is part of your service.

The Act doesn't name a technical standard for private businesses. In practice, WCAG 2.2 at Level AA is the benchmark that regulators and claimants' solicitors point to, which is why an audit against WCAG is the usual way to show you've taken the duty seriously.

If you sell into the EU, the European Accessibility Act has applied to many consumer-facing services since June 2025 and points to the same standards.

Why overlays fall short

  • They can't fix the structure. Confusing focus order, menus that trap the keyboard and checkouts that never announce errors are built into the code. A script layered on top rarely repairs them reliably.
  • They guess. A wrong label can be worse than none, because it actively misleads a screen reader user.
  • They can get in the way. Many screen reader users already have their assistive technology set up exactly how they like it. Overlays that change the page underneath them can cause new problems, and some disabled people install browser extensions specifically to block overlays.
  • They don't move the responsibility. The reasonable adjustments duty sits with the business providing the service.

The regulators have noticed

In April 2025 the US Federal Trade Commission finalised an order requiring overlay provider accessiBe to pay $1 million. The FTC found the company had misled customers by claiming its widget could make any website WCAG compliant, and it is now barred from making that claim.

That's a US case, but the lesson carries over: a product sold as instant compliance was found not to deliver it. In the US, businesses with overlays installed have continued to be named in accessibility lawsuits.

In the UK there's no published court ruling on overlays specifically. Most website accessibility claims here settle before trial, so the lack of case law isn't evidence that overlays work. Hundreds of accessibility practitioners have signed the public Overlay Fact Sheet warning against relying on them.

Could an overlay make things worse?

Possibly. Installing one can look like you knew accessibility mattered but chose a shortcut instead of fixing the site. That isn't a strong position if a disabled customer complains. An audit and a dated fix list show the opposite: that you looked for the barriers and acted on them.

What actually reduces your risk

  1. Get the site tested by a person against WCAG 2.2 AA, including keyboard and screen reader testing.
  2. Fix the high-priority barriers in your key journeys first: enquiries, bookings and checkout.
  3. Publish an honest accessibility statement with a way for people to report problems.
  4. Retest after fixes, and again after major redesigns.
  5. If you already pay for an overlay, don't rely on it. Check the site with it switched off, because that's the experience many assistive technology users get anyway.

If your site was built with an AI tool or a page builder, read why your AI-built site still isn't accessible. For the legal background, see can I be sued for an inaccessible website?

Common questions

Is it illegal to use an overlay?

No. Using one isn't against the law. The problem is relying on it as your accessibility plan.

Are any overlay features useful?

A few toolbar options can help some people, but they duplicate settings already built into browsers and devices. They're not a substitute for an accessible site.

Should I remove my overlay before an audit?

Leave it in place and tell me it's there. I test with it both on and off, so you can see what it does and doesn't fix.

Want to know what your overlay is missing?

Tell me your website address and whether you're using a widget, and I'll tell you honestly what it is and isn't covering.

Email Clearsight Access

This guide is general information, not legal advice. Back to all Web Accessibility Guides.