Why accessibility overlays do not meet BFSG / EAA compliance.
An overlay widget — accessiBe, UserWay, EqualWeb, AudioEye Reach — injects JavaScript that re-renders the page after the page loads. It does not change the source HTML a German civil-society plaintiff or a French enforcement body will actually test. This page collects the citations compliance officers keep asking us for.
The European Accessibility Act (Directive 2019/882) and its German implementation (Barrierefreiheitsstärkungsgesetz, BFSG) put obligations on the underlying digital product. § 12 BFSG requires covered services to be accessible — not to declare themselves so. A runtime widget that rewrites the DOM after page load does not modify the artefact that is tested in an enforcement matter.
Source: BFSG § 12; EAA Directive 2019/882 Art. 4What regulators and courts have already said
FTC consent order against accessiBe — April 2025 ($1M)
The US Federal Trade Commission entered a consent order against accessiBe Ltd. over deceptive marketing of its overlay's WCAG-compliance claims. The settlement included a $1 million monetary judgement and prohibited representing that the product makes websites WCAG-compliant absent competent and reliable testing.
Source: FTC file 232-3023, In re accessiBe Ltd.
Class actions against overlay vendors
Plaintiffs in US ADA Title III matters have repeatedly sued merchants whose sites ran an overlay yet remained inaccessible to screen-reader users. Representative cases include Murphy v. Eyebobs (D. Minn., 2021) and Doe v. accessiBe (S.D.N.Y., 2022), both alleging that the overlay did not cure the underlying accessibility barriers. Courts have not treated overlay installation as a defence on the merits.
German enforcement posture
The Bundesfachstelle Barrierefreiheit and BIK (Barrierefrei Informieren und Kommunizieren) treat BFSG compliance as a property of the underlying product. BIK's BITV-Test methodology evaluates the page as delivered to the user-agent; overlay-modified DOM states are out of scope. Verbraucherzentrale-style civil-society plaintiffs file BFSG-Abmahnungen referencing the static markup, not the post-injection runtime.
Source: BIK BITV-Test methodology (bik-fuer-alle.de); Bundesfachstelle Barrierefreiheit position papers, 2024–2025.
What screen-reader users and the a11y community have documented
Independent accessibility researchers have documented overlay side-effects on assistive technology for years. The most-cited long-form references compliance teams quote:
- Adrian Roselli — Accessibility Overlays Don't Work Yet (multi-year update series, 2020–2025). Documents repeated overlay regressions and screen-reader breakage.
- Karl Groves — co-founder of Tenon.io and long-time overlay critic. Published source-code analyses showing overlays often introduce new failures.
- The Overlay Fact Sheet (overlayfactsheet.com), signed by 700+ accessibility practitioners as of 2025, including screen-reader users, asks vendors to stop claiming overlays achieve compliance.
- NFB (US National Federation of the Blind) 2021 resolution against accessibility overlays.
What a Fachanwalt actually attaches to a BFSG response
A defence to a BFSG-Abmahnung needs evidence that is dated, repeatable, and tied to the source HTML that the regulator can inspect. The elements German IT-Recht counsel routinely requests:
- A scan record produced by a recognised testing engine (axe-core, the same engine Lighthouse and Chrome DevTools use) against the source HTML — not against post-injection DOM.
- A timestamp from a qualified Time-Stamping Authority (RFC 3161), so the date of the test cannot be backdated.
- A hash chain or comparable tamper-evidence so a single PDF screenshot cannot be edited after the fact.
- A history demonstrating ongoing due diligence — German courts have been receptive to an "Organisationsverschulden" defence when the operator can show continuous monitoring, not a one-off audit.
WCAGdesk produces all four. Defense (€299/mo) gives you daily scans with timestamps, hash chain, and a 90-day history; Counsel adds full history retention and procurement-grade exports. None of this is achievable with an overlay — there is nothing to timestamp.
See what an actual compliance record looks like.
Free first scan, no signup. You will see the exact source-code findings a regulator or a Fachanwalt would see — and you will see the timestamped record we generate alongside it.