Accessibility overlays: why a widget does not make a website accessible or compliant

What overlays are

An accessibility overlay is a third-party script added to a website that displays a toolbar or icon offering adjustments such as larger text, higher contrast, stopping animations, readable fonts or a reading guide. Many also claim to scan pages automatically and repair accessibility issues using artificial intelligence, for example by adding missing image descriptions or labels.

They are marketed as a quick, low-cost way to meet standards such as the Web Content Accessibility Guidelines and legal requirements, often with statements about compliance or protection from lawsuits.

Why they cannot deliver compliance

WCAG conformance is a property of the website itself: its HTML structure, semantics, keyboard behaviour, focus management, text alternatives, form labels, error messages, captions and content. Most barriers are created in templates, components and content, and they need to be fixed there.

Automated repair is limited. Software can detect some issues, such as missing attributes or low contrast, but it cannot reliably understand what an image communicates in context, whether a link text makes sense, whether a custom widget behaves correctly for keyboard and screen reader users, or whether a complex checkout can be completed. Automated testing tools themselves catch only a portion of WCAG issues, and automated repair is harder still.

Toolbar features often duplicate what browsers and operating systems already provide. People who rely on assistive technology usually have their own configured tools, such as screen readers, magnification or custom styles, and an overlay’s toolbar does not help them if the underlying site is broken. Some users report that overlays interfere with their assistive technology.

Criticism from users and experts

Criticism of overlays has come from people with disabilities, accessibility practitioners and organisations representing disabled people. In 2021, hundreds of accessibility professionals signed the Overlay Fact Sheet, a public statement explaining why they considered overlays unable to make websites accessible and recommending against their use.

In the United States, businesses using overlays have continued to face accessibility lawsuits, showing that installing a widget does not in itself resolve barriers users encounter.

In January 2025, the US Federal Trade Commission announced action against accessiBe, an overlay provider, alleging that it misrepresented its AI-powered tool’s ability to make websites compliant with WCAG and that it formatted third-party reviews to appear independent. The order, finalised later that year, required a payment of 1 million dollars and prohibited the company from making such claims without sufficient evidence.

The European context

The European Accessibility Act has applied since 28 June 2025 to many consumer-facing products and services, including e-commerce, banking services and certain transport and communication services. National laws implement it, typically referring to the harmonised standard EN 301 549, which incorporates WCAG success criteria for web content.

None of these frameworks treat an overlay as a substitute for accessible design. Authorities and complainants look at whether people with disabilities can perceive, operate and understand the service. Many laws also require an accessibility statement describing conformance and known issues, which cannot honestly claim full conformance on the basis of a widget.

What works instead

Accessible websites come from accessible components, content and processes. The effort is real but manageable when approached systematically.

Audit

Combine automated scans with manual testing using keyboard, screen readers and zoom on key journeys such as navigation, search, product pages, forms and checkout.

Fix components

Repair shared templates and design system components first, so fixes apply across all pages.

Train editors

Teach content teams to write alt text, meaningful link text, headings and captions.

Include users

Test with people with disabilities, who find issues checklists miss.

Build it in

Add accessibility criteria to design reviews, development definitions of done and procurement of third-party tools.

Publish honestly

Maintain an accessibility statement that describes the real status and how users can report problems.

Is there any place for toolbars?

Some organisations keep simple preference controls, such as a dark mode or text size setting built into the site itself, because users appreciate them. Built-in features that do not interfere with assistive technology can be useful additions.

The problem is not user preferences but the promise that a script can replace accessible design and remove legal risk. If an overlay is already installed, evaluate whether it causes problems for assistive technology users, and do not let it delay the audit and remediation work that actually changes the experience. This article is a general overview and not legal advice.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• Digital Growth — The ongoing programme — strategy, content, paid, organic and reporting — run as one thing that answers to pipeline rather than to channel dashboards.
• Quote to cash without re-keying: where the handoffs break
• Product data is the e-commerce growth lever nobody budgets for
• Account deletion in apps and customer portals: Apple, Google Play and GDPR requirements in one design
• Client portals for accounting and tax firms: ending the chase for documents
• All insight articles