The Overlay Problem: Why a Widget Will Not Protect You From an Accessibility Warning Letter

Legally and technically, it does not work that way. Since Germany's Market Surveillance Body for Accessibility entered its active enforcement phase in early 2026, exactly these quick fixes have moved into focus. Relying on an overlay alone still leaves you exposed to a warning letter, because authorities and courts are looking much more closely now.

What an accessibility overlay actually is

An overlay is an additional script that providers usually let you add with a single line of code. It displays a control panel where visitors can adjust contrast, font size or spacing, sometimes combined with automatically generated alt text or retrofitted ARIA labels. It is often marketed as a complete solution that works without touching the source code and is ready within minutes.

That exact promise is the problem. A script layered on top of a finished page cannot reach many of the structural causes of barriers, because it never changes the underlying code, it only intervenes at runtime in the browser.

Why overlays hit a technical ceiling

Missing form labels, an illogical focus order, menus that cannot be reached by keyboard, or an incorrect heading hierarchy are all rooted in the markup itself. A script added after the fact can, at best, mask such problems, not fix them. In practice, overlays often introduce new barriers too: they frequently interfere with how screen readers behave, overriding individual settings that people with disabilities have deliberately configured for themselves.

• ✓ Promises like "accessible in minutes", with no prior analysis of the website
• ✓ No access to the source code required, the entire promise rests on a single line of code
• ✓ No mention of manual testing with a keyboard, a screen reader or magnification software
• ✓ No visible history of fixes in the code, only ongoing adjustments inside the script itself

A practical example

An online shop installs an overlay and then advertises its website as accessible. The contrast menu works, visitors can enlarge the text, an automatically generated alt text appears on the product images. In the checkout process, the "Add to cart" button still cannot be reached by keyboard, because it is technically not a real button element but a div styled with JavaScript and never given keyboard focus. The overlay cannot close that gap, because it never changes the HTML structure of the element, it only places an extra control surface next to it.

For screen reader users, nothing changes: the core purchase step stays inaccessible. Gaps like this in business critical user journeys are exactly what surfaces during a market surveillance review or a warning letter, no matter how many comfort features an overlay adds on top.

The accessiBe case, a warning sign beyond the US

How seriously this issue is now taken shows in a case from the United States. In January 2025, the US Federal Trade Commission ordered overlay provider accessiBe to pay one million US dollars. The allegation: the company had claimed its AI powered tool automatically made any website WCAG compliant, which the FTC found to be untrue. accessiBe had also published paid customer reviews without disclosing the business relationship with the reviewers.

An analysis of US court records by the company TestParty found that more than 800 businesses using overlay widgets such as accessiBe, UserWay or EqualWeb were sued in 2023 and 2024 alone, more than 25 percent of all digital accessibility lawsuits recorded in that period. That is a US legal context with its own court system, but the pattern behind it is hard to ignore: in none of these cases did an installed widget prevent a lawsuit.

Legally, a widget is not enough under the EAA

The European Accessibility Act, implemented in Germany through the BFSG, requires websites and online shops to genuinely meet accessibility requirements. The technical benchmark is the harmonised standard EN 301 549, which in turn builds on the WCAG 2.2 success criteria for perceivable, operable, understandable and robust content. These criteria cannot be satisfied by a single script, they require structural changes to the code and, in many cases, manual testing that no automated tool fully replaces.

In Germany, the Market Surveillance Body for Accessibility has been in its active enforcement phase since January 2026, focusing on high reach offerings and providers with a history of violations. Entire user journeys, such as a full checkout process, are reviewed, not just individual buttons or images. Since February 2026, professional warning letters have also been circulating, averaging around 2,700 euros gross per letter, and fines from the authorities can reach up to 100,000 euros depending on the case. An overlay that only masks symptoms changes nothing about that exposure.

Pressure is building at EU level too: in March 2026, the European Commission sent Germany a reasoned opinion over insufficient implementation of the underlying EU directive 2019/882, and a case before the Court of Justice of the European Union is possible if the response remains inadequate. For businesses, that means enforcement is more likely to intensify than ease off, a trend no overlay can soften.

What actually matters: analysis, remediation, monitoring

Effective accessibility does not come from an extra script, it comes from a complete workflow. Several persistent myths about accessibility are still widespread, and the idea that a widget is enough is one of them.

• ✓ Analysis, a combination of automated scanning and manual testing uncovers common barriers that tools alone overlook
• ✓ Remediation, problems found are fixed in the code, not just masked in the browser
• ✓ Monitoring, new content and features are checked again on an ongoing basis, because websites keep changing
• ✓ Documentation, a correctly maintained accessibility statement makes the state of implementation legally traceable

How SiteCockpit helps

SiteCockpit deliberately separates genuine remediation from user comfort. easyMonitoring scans websites continuously, detects barriers and prioritises them by urgency, so your team can work through the actual root causes in a structured way. Where automated scans reach their limits, for example with complex interactions or how a page truly behaves with a screen reader, SiteCockpit's manual audits add human expert testing.

The frontend widget easyVision is deliberately not a replacement for this workflow. It gives visitors additional, optional adjustments such as contrast, font size or a focus mode, while structural accessibility is built in the background through analysis and remediation. easyStatement then documents the current state of that work automatically in a legally sound accessibility statement.

The difference from a pure overlay lies in the approach: instead of masking a symptom in the browser, SiteCockpit works on the root cause in the code and keeps the progress traceable at every step. For businesses that already run an overlay, the answer is usually not to remove it, but to add to it: a full scan shows within minutes which structural gaps remain open behind the comfort layer.

An overlay can be a useful piece of the user experience, but as the sole answer to the EAA and its national implementations it holds up neither legally nor technically. Anyone who wants to be on the safe side combines automated monitoring like easyMonitoring with genuine remediation in the code.