Skip to main content
Welcoma

Implementation

Accessibility Overlays: Why accessiBe, UserWay & Co. Don’t Provide Real Accessibility

By Alexander Flach Updated 7 min read

Contents

The promise sounds tempting: add one line of code, and the website is automatically accessible and WCAG-compliant. That is exactly what providers such as accessiBe and UserWay claim with their overlay tools.

The reality is different – and this is not merely the opinion of critics. It is the documented assessment of regulatory authorities, more than 900 accessibility professionals, and organizations representing people with disabilities. This article explains what an overlay is technically, why it cannot deliver what it promises, what experts and regulators say about it – and what legal risk it creates under the BFSG.

What an accessibility overlay is and how it works

An accessibility overlay – also called a widget or plug-in – is a JavaScript snippet that you add to your website. When the page loads, it places a layer over your content in the browser that is intended to automatically detect and “fix” accessibility barriers, and it often also displays an accessibility menu for visitors.

The key technical point lies in the word “layer”: an overlay changes the presentation at runtime in the browser – it does not change your source code. The U.S. Federal Trade Commission (FTC) also makes clear that overlays are not designed to permanently modify the code, but only to make temporary adjustments to the user interface. Everything else follows from this one fact.

The promise versus reality

The accessiBe case shows how far the marketing claims can go. The company advertised that one line of code could instantly make a website 30 % WCAG-compliant, that an AI process would handle the remaining 70 % within 48 hours, and that a daily re-scan would maintain compliance.

The FTC reached a different conclusion in its complaint: in numerous cases, the widget failed to make basic elements such as menus, headings, tables, images, and recordings accessible. Websites using the overlay continued to contain barriers – missing or incorrect alternative text, missing focus indicators, keyboard traps, and incorrect heading levels. One illustrative example from the case: a photo of filet mignon was given the alternative text “brown bread on a white ceramic plate” by the overlay. This is exactly the kind of “correction” that automated guessing can produce.

Worse still, an overlay can make the situation worse. If it rewrites ARIA roles, focus order, or page structure, it can conflict with screen readers such as NVDA, JAWS, or VoiceOver. According to surveys, around 72 % of users with disabilities rate overlays as barely helpful or not helpful at all. And if the script fails to load – because of an ad blocker, network error, or JavaScript problem – all accessibility barriers immediately return.

Why overlays do not meet WCAG requirements

The core reason is simple: the source code remains broken. WCAG criteria are met in the code, not in a layer placed on top of it. An overlay cannot repair structural HTML problems, PDFs, or videos, and it cannot make the human judgments that accessibility requires – whether alternative text is meaningful, whether the focus order is logical, or whether text is written in an understandable way.

This is the same fundamental limitation faced by any fully automated solution: only part of the WCAG criteria can be assessed automatically; the rest requires human review – more on this in Automated WCAG Testing and Testing Accessibility. And even full WCAG compliance would not be sufficient, because the relevant EN 301 549 standard goes beyond WCAG.

What experts, organizations, and regulators say

The fact that overlays do not work is not an isolated opinion, but a broad consensus among those who understand accessibility best:

  • The Overlay Fact Sheet (overlayfactsheet.com), launched in 2021 by accessibility professional Karl Groves and the community, has been signed by more than 900 professionals – including contributors to the WCAG, ARIA, and HTML specifications, accessibility experts at Google, Microsoft, Apple, and the BBC, as well as affected users themselves. The core message: overlays are not an effective way to ensure accessibility.
  • The National Federation of the Blind adopted a resolution describing claims made by overlay providers as misleading, unsupported, and unethical, and returned a sponsorship payment from accessiBe.
  • The International Association of Accessibility Professionals and the European Disability Forum jointly oppose the use of overlays for compliance purposes, and the European Commission has also classified overlays as a poor solution.

Overlay providers often portray this criticism as an attack by competitors. That misses the point: the signatories are the people who help write accessibility standards and the disabled users who depend on them – not competitors. In Germany, the same debate appears under headlines such as “Accessibility at the click of a button or a dangerous sham?”

The most prominent regulatory response so far came from the U.S. Federal Trade Commission. In January 2025, it accused accessiBe of advertising that its widget could make any website WCAG-compliant. In April 2025, a final order took effect: a payment of one million U.S. dollars and a ban on continuing to claim that its automated products make or keep a website WCAG-compliant – unless there is reliable evidence to support such claims. The settlement was reached without an admission of wrongdoing. The FTC also objected to paid content being presented as independent reviews. (UserWay has also faced a class action lawsuit elsewhere.)

For Germany, the situation is clear: an overlay does not make you BFSG-compliant. The BFSG requires genuine compliance with EN 301 549 and WCAG – something an overlay does not provide because the source code remains unchanged. Anyone relying on it may have a false sense of security while the risk of fines remains (up to 100,000 euros for websites); the legal framework is explained in the BFSG Guide. And an overlay is not a legal shield: websites using overlays have still been sued elsewhere.

The honest alternative

There is no shortcut, but there is a clear path: find the real problems, fix them in the source code, and test again. The process is described in Testing Accessibility and Making a Website Accessible.

That is exactly what Welcoma is built for: the upcoming WCAG scanner identifies the real problems in the source code so you can fix them and makes progress measurable through repeated scans – instead of hiding barriers behind a layer.

One important distinction at the end, because Welcoma itself offers an accessibility menu: an accessibility menu that gives visitors tools such as text resizing, contrast adjustments, or read-aloud functionality provides genuine added value – but only as an enhancement on a website where accessibility barriers have already been fixed in the code, not as a replacement for doing so. That is the key difference between honest assistance and false compliance: an accessibility menu as the finishing touch can be useful; a widget sold as a compliance solution is exactly the kind of misleading shortcut this article is about.

Frequently Asked Questions

Does an overlay make my website BFSG-compliant?

No. The source code remains unchanged, and the accessibility barriers remain. The BFSG requires genuine compliance with EN 301 549 and WCAG, which an overlay does not provide.

Does that mean all widgets are bad?

It depends on how they are marketed. A widget promoted as a compliance solution is the problem. An accessibility menu used as an honest convenience enhancement on a website whose accessibility issues have already been fixed in the code is not.

Does an overlay protect me from warnings or lawsuits?

No. An overlay is not a form of legal protection. Websites using overlays have still been sued, and authorities do not recognize them as proof of compliance.

Why can’t a tool simply solve everything automatically?

Because a large part of accessibility requirements depends on human judgment. Only about one-third of WCAG criteria can be tested automatically; the rest must be evaluated by a person.

Updated: . This article gives a general overview. Not legal advice.

Written by

Alexander Flach

Updated:

Keep reading.

Free WCAG scan

Reveal real problems instead of hiding them.

Start the honest WCAG scan. It will uncover the real source-code issues and make progress measurable, no checkbox hidden behind a layer.

Start your free WCAG scan.

We scan your website automatically. We take a short look at the report before we email it to you. The automated check covers roughly a third of the WCAG criteria. We use your data only for this, more in the privacy policy.