Accessibility overlays: what they can do and what they can't

Add one script tag, an icon appears in the corner, and the website counts as accessible: that is the pitch behind accessibility overlays, and it lands especially well now that the European Accessibility Act and Germany's BFSG are enforced. The pitch is convenient, cheap and demonstrably false. It would be just as wrong, though, to dismiss the widgets entirely, because for some visitors they genuinely help. This guide draws the line properly: what overlays can do, what they cannot, and why the US consumer protection agency ordered one of the biggest vendors to pay a million dollars.

Why everyone suddenly wants a widget

Since the European Accessibility Act took effect in June 2025 and national authorities began checking, many site owners look for the fastest route to conformance. In Germany, the BFSG even backs the requirements with fines of up to 100,000 euros. Overlays serve exactly this wish: a piece of JavaScript from the vendor's server, a monthly subscription, no developer project. For a manager who first heard about accessibility law last quarter, that sounds like the answer.

The catch: conformance is not measured by whether a settings panel floats above the page. It is measured by whether code and content meet the criteria of the WCAG, from alternative text and keyboard operation to labelled forms. What conformance levels A, AA and AAA require in detail is covered in our dedicated guide. Here we look at how much of that an overlay actually covers.

The technology behind it

An overlay is a JavaScript file loaded from the vendor's server while the page renders. It shows a settings panel where visitors adjust the presentation: font size, contrast, line spacing, a read-aloud function. Some products promise more and claim to detect and repair source-code errors at runtime, for example guessing missing alternative texts with AI. The key point: an overlay never changes your website itself, only its rendering in the visitor's browser, and only while the script loads. The unlabelled form field stays unlabelled in the code.

What a widget honestly does for visitors

Let's be fair: for part of your audience, adjustment widgets are real help. Someone whose eyesight has declined with age and who has never touched their system settings gets larger text and stronger contrast in two clicks. That is comfort a website may happily offer.

• Text and layout: larger fonts, more line spacing, a more readable presentation.
• Contrast modes: stronger contrast or a dark mode at the click of a button.
• Reading aids: a reading mask, highlighted links, paused animations.
• Read aloud: simple speech output for people who do not use a screen reader.

The limit of these helpers is reached with people who rely on assistive technology permanently. A blind user brings his own screen reader, a user with a motor impairment her own keyboard controls. Those tools do not need a panel with font-size sliders. They need clean code underneath: correct headings, labelled fields, a working focus order. And that is exactly where overlays achieve the least.

Where the limits are hard

The field is unusually united on this. The Overlay Fact Sheet, an open statement by practitioners, has been signed by 1,031 professionals, W3C contributors among them. Its core claim: no overlay product on the market can make a website fully conformant with any existing accessibility standard or remove legal risk.

The reason is not a technical detail but a principle: automated repairs lack context. Image recognition may see 'woman with laptop' in your photo. Whether that image shows your founder, is pure decoration or acts as the link to the customer account is known only to someone who knows the page. The German social organisation Aktion Mensch criticises precisely this lack of context and rates overlays as a stopgap at best. Its verdict is short:

Germany's federal monitoring body for IT accessibility (BFIT-Bund) and the German blind and visually impaired association DBSV reach the same conclusion in their joint assessment of overlay tools: by the current state of technology, overlays cannot make a website conformant. That is not an opinion from the consulting scene. It is the position of a regulator.

The FTC's million-dollar order

In the US, the marketing promise has become a legal case. The Federal Trade Commission finalised an order requiring overlay vendor accessiBe to pay 1 million US dollars in April 2025. The charge: the company had falsely claimed its widget makes websites WCAG conformant. What was sanctioned was not the product as such but the promise. And that exact promise still appears in plenty of overlay ads today.

Overlays do not stop lawsuits either. According to reports by the US analytics firm UsableNet, more than 800 companies that had an overlay in place were sued in 2023 and 2024 combined. In May 2025 alone, UsableNet counted 119 defendants with a widget on their site. Whoever buys an overlay for legal safety buys a feeling, not protection.

Overlays and the law: why 'install a widget' is not conformance

The European Accessibility Act and its national implementations, Germany's BFSG among them, point to the European standard EN 301 549, which references WCAG level AA. What gets audited is the actual state of code and content. Germany's market surveillance authority MLBF has been checking actively since 2026, partly with automated scans, and it evaluates the same criteria as any WCAG test: alternative texts, contrast, form labels, keyboard operation. A panel with font-size sliders simply does not register as fulfilment in that audit.

The same logic applies across the EU: every member state has its own implementation of the European Accessibility Act with its own oversight. An overlay that does not count as conformance in Magdeburg counts just as little in Paris or Milan. The Overlay Fact Sheet puts it briefly: no overlay can remove legal risk either.

A word about our own widget

Full transparency: we sell an assistance widget ourselves, with adjustments such as font size, contrast and read-aloud. It is deliberately positioned as what it is: a comfort layer for visitors, nothing more. It does not make your website conformant with the EAA or the BFSG, it does not repair missing alt texts or unlabelled forms, and we will never tell you otherwise.

If you need conformance, you start with a real audit and fix the findings in code and content. Only after that, as an extra for visitors, does a widget make sense. That order holds for every widget on the market, not just ours. If a vendor promises you more, read the FTC section again.

The honest path: repair first, comfort second

1. Measure the status quo: have your website tested automatically against WCAG. The scan produces a list of real violations with code locations instead of a gut feeling.
2. Fix blockers first: keyboard traps, unlabelled forms and invisible focus lock people out completely. These items belong at the top of any work list.
3. Work through the bulk: check colour combinations with the contrast checker and add alternative texts. How good alt text is written is covered in our guide on writing alt text. AI drafts help with volume, checking against the page context stays human work.
4. Document honestly: publish an accessibility statement that describes the real state, known gaps included. An honest statement holds up better than a polished one.
5. Then add comfort: once the foundation stands, nothing speaks against an assistance widget as an extra for visitors. As the finishing touch, not as a substitute for the foundation.

Frequently asked questions about accessibility overlays

An overlay can be the finishing touch of an accessible website, its foundation it never is. So start where the auditors start: with the actual state of your code. The free scan above shows you within two minutes which barriers really sit on your website. After that you know what a widget can do for you and what only real fixes achieve.