Loading...
Legal Guide • EAA & UK Equality Act
Overlay vendors now market their widgets as a shortcut to European Accessibility Act and Equality Act compliance. But every relevant legal test in the EU and UK is outcome-based: it asks whether the service actually works for disabled users, not which scripts the page loads. This guide walks through what the law really requires and where overlays fall short of it.
2026 Lawsuit Defendants
~20%
Had an overlay installed (UsableNet)
FTC Order vs. accessiBe
$1M
Over compliance claims, Jan 2025
The Caen Court's Framing
Obligation of result
Accessibility judged by outcomes
Laws Naming Overlays
0 exemptions
No statute treats a widget as compliance
No. No law in the EU or the UK recognises an accessibility overlay as a route to compliance. The European Accessibility Act tests whether a service meets accessibility requirements. The UK Equality Act tests whether disabled people can actually use the service. Neither test mentions widgets, toolbars, or AI remediation layers, and neither can be satisfied by a tool that leaves the underlying barriers in place.
A quick recap for anyone new to the topic: overlays are third-party JavaScript widgets, from vendors such as accessiBe and UserWay, that promise to detect and fix accessibility problems automatically at page load, usually adding a floating toolbar of display options. Independent testing consistently finds that they fail to fix the barriers that matter and sometimes introduce new ones. Our accessibility overlays guide covers the technical evidence in depth; this page focuses on the legal question for the EU and UK.
The pattern across every jurisdiction examined below is the same: regulators, disability organisations, and courts evaluate outcomes. An overlay changes what a page looks like with a widget menu open. It does not change what the page delivers to assistive technology, and the law cares about the latter.
The European Accessibility Act requires that in-scope products and services, including e-commerce, banking, and transport services, meet its accessibility requirements: the actual service must be perceivable, operable, understandable, and robust for people with disabilities. Conformity is presumed when a service conforms to the harmonised standard EN 301 549, which incorporates WCAG at Level AA for web content. In practice, meeting the EAA means your pages conform to WCAG 2.2 AA.
Here is where overlays run into a structural problem. WCAG conformance is evaluated on the content as delivered. An overlay widget layered on top of a page does not change the page's underlying conformance: a button that is unlabeled in the markup remains unlabeled in the markup, a form without programmatic error messages still has none, and a custom dropdown that traps keyboard focus still traps it. The widget adds its own UI alongside the broken one; it does not repair the code that assistive technology reads.
So a service owner claiming EAA conformity via EN 301 549 has to show that the delivered content conforms, and an overlay contributes nothing to that showing. For how the EAA is enforced in a specific member state, see our EAA in Ireland guide.
This is not just an outside analysis. The European Disability Forum (EDF), the umbrella organisation of persons with disabilities in Europe, has stated publicly that accessibility overlays “do not guarantee compliance” with European legislation (edf-feph.org). That statement matters because EDF is the body that represents the very users the EAA exists to protect, and it is the organisation regulators and standards bodies consult on disability issues.
EDF has also reported the European Commission's position that overlay tools may make a website lessaccessible. That is consistent with what disabled users have said for years: overlay widgets can interfere with the screen readers, magnifiers, and custom settings people already have configured, overriding working assistive technology with the vendor's inferior version. A tool the Commission views as a potential step backwards is a strange foundation for a compliance claim.
In June 2026 the Tribunal judiciaire de Caen ordered Carrefour to make its e-commerce site and app accessible. Two features of the ruling matter far beyond France. First, the court treated accessibility as an obligation of result: the duty is discharged by achieving an accessible service, not by making efforts toward one. Second, the court rejected a partial conformance rate as insufficient; being mostly accessible was not accessible.
To be clear, the Carrefour case did not involve an overlay, and we are not suggesting it did. Its relevance is the principle. An obligation of result is measured by actual outcomes for users: can a blind customer find the product, add it to the basket, and pay? That is precisely the measure on which overlays fail. If courts in EAA member states follow Caen's framing, the question in every case becomes “does the service work for disabled users?”, and installing a widget is not an answer to that question.
An outcome-based standard also cuts off the most common overlay defence, good-faith effort. Under an obligation of result, having bought a tool that promised accessibility is not the same as having delivered it.
The UK is no longer bound by the EAA, but its own law asks a similar question. The Equality Act 2010 places a duty on service providers to make reasonable adjustments for disabled people, and that duty is anticipatory: you must plan for disabled users in advance, not react after someone is excluded. The measure of whether the duty is met is practical: can disabled users actually use the service?
That framing leaves overlays in the same position they occupy under the EAA. If the underlying barriers persist with the widget active, and testing consistently shows they do, then the disabled user is still excluded and the duty is not met by having installed one. The Equality Act does not grade tools; it grades access. A retailer whose checkout is unusable with a screen reader is in the same legal position whether or not a floating accessibility button sits in the corner of the page.
For the wider UK picture, including the public sector regulations that already mandate WCAG-based standards, see our UK accessibility compliance guide.
If overlays worked as a legal shield, companies running them would not get sued. They do, at scale. Per UsableNet's mid-year 2026 reporting, roughly 20% of companies sued for digital accessibility in 2026 had an accessibility widget or overlay installed. Plaintiffs' firms are not deterred by overlays; some treat the widget itself as evidence that the defendant knew about accessibility obligations and chose a shortcut.
The vendors' own compliance claims have also drawn regulatory fire. In January 2025, the US Federal Trade Commission ordered overlay vendor accessiBe to pay $1 millionover claims it misrepresented what its AI-powered product could do for compliance. A regulator formally acting against the flagship vendor's compliance marketing is about as direct a warning as buyers will get.
European enforcement is heading the same way, because it tests outcomes. The Dutch regulator ACM reported in March 2026 that 61% of the largest Dutch webshops fail accessibility requirements, findings produced by examining the services themselves. Market surveillance under the EAA works on the delivered service, which is exactly the thing an overlay does not change.
What satisfies both the EAA and the Equality Act is the unglamorous thing: remediation of the underlying code to WCAG 2.2 AA and EN 301 549, verified by testing. That is the standard the law presumes conformity against, the thing market surveillance measures, and the outcome an obligation of result demands.
No. The European Accessibility Act requires that in-scope services meet accessibility requirements, and conformity is presumed when the service conforms to the harmonised standard EN 301 549, which incorporates WCAG at Level AA. WCAG conformance is evaluated on the content as delivered: if a button is unlabeled in your markup, it remains unlabeled with an overlay widget running on top. No provision of the EAA, EN 301 549, or any national transposition names an overlay as a route to compliance. What satisfies the law is remediating the underlying code and verifying it through testing.
Yes. Installing an overlay does not remove the underlying barriers, so it does not remove the legal exposure. In the US, where the litigation data is most developed, UsableNet's mid-year 2026 reporting found that roughly 20% of companies sued for digital accessibility in 2026 had an accessibility widget or overlay installed. In the EU, enforcement runs through market surveillance authorities, consumer complaints, and the courts, and each of those channels looks at whether the service actually works for disabled users, not at which third-party scripts are loaded on the page.
Installing an overlay is unlikely to discharge the duty by itself. The Equality Act 2010 imposes an anticipatory duty to make reasonable adjustments, and the practical question is whether disabled users can actually use the service. Testing consistently shows that the core barriers on a page, such as missing labels, broken keyboard access, and inaccessible custom widgets, persist with an overlay active. If a blind customer still cannot complete checkout with the widget switched on, the adjustment has not been made, whatever the tool's marketing says.
Because compliance is what they are selling, and the claims have outrun the technology. Vendor marketing has promised automated conformance with WCAG, the ADA, and now the EAA. Those claims have drawn regulatory action: in January 2025 the US Federal Trade Commission ordered overlay vendor accessiBe to pay $1 million over claims it misrepresented what its AI product could do for compliance. Treat compliance guarantees from any overlay vendor as marketing claims, and test the actual service with the widget running before relying on them.
Market surveillance under the EAA tests the delivered service, and an overlay does not fix the markup underneath. An assessment against EN 301 549 examines the content as it is served: the accessibility tree, the labels, the keyboard behaviour, the contrast of the actual pages. The Dutch regulator ACM, for example, reported in March 2026 that 61% of the largest Dutch webshops fail accessibility requirements, a finding based on testing the services themselves. A widget menu offering font resizing does not change what an audit of the underlying pages finds.
Do not panic, but do not treat the subscription as compliance either. First, get an honest picture: run an audit of your key user journeys against WCAG 2.2 AA with the overlay disabled, because that is what your code actually delivers. Second, budget the overlay fee toward real remediation of the issues the audit finds. Third, once the underlying code is fixed and verified, the overlay has no compliance job left to do and most teams remove it. Keeping it while remediating is a commercial choice, not a legal shield.
This page is provided for general educational purposes only and does not constitute legal advice. The European Accessibility Act is transposed and enforced differently across member states, UK equality law continues to develop through the courts, and the analysis here reflects the position at the time of writing. For advice about your specific situation, consult a lawyer experienced in accessibility law in the relevant jurisdiction.
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences