Accessibility overlays and what the law actually requires
An accessibility overlay (also called an accessibility widget, or an automated accessibility widget) is a snippet of JavaScript a site adds to its pages. At runtime it layers on controls (contrast toggles, font resizing) and attempts automated fixes. This page explains, with sources, what regulators and courts require, and where overlays fit.
Sitejar sells accessibility scanning and source-code remediation, so we have a point of view. We’ve kept every factual claim below tied to an official source so you can check it yourself. This is not legal advice.
What the law actually requires
Accessibility law is written around technical conformance, not tooling. The European harmonised standard EN 301 549 (the standard the EU Web Accessibility Directive and the European Accessibility Act point to) adopts WCAG 2.1 Level AA for web content. Conformance means those requirements are satisfied in the site’s own code and design.
The United States: public rules, private case law
The U.S. Department of Justice’s 2024 ADA Title II Final Rule requires state and local government websites to meet WCAG 2.1 Level AA by April 2026–2027. This is a technical conformance standard. Implementation must be present in the site’s own code.
While DOJ’s 2024 Rule applies specifically to public entities, U.S. federal courts have consistently applied ADA Title III to private commercial websites through case law, with the same underlying expectation of actual technical accessibility. Overlay-based approaches are increasingly cited in litigation as insufficient.
Why an overlay cannot substitute for conformance
Because the requirement is conformance of the page itself, remediation has to live in the site’s own code. No automated overlay tool can cover the full set of WCAG 2.1 Level A and AA criteria. Many require human judgement (is this alt text meaningful? is this heading structure correct?) that a runtime script cannot supply. An overlay sitting on top of an unconformant page does not make the underlying page conformant; the criteria it fails are still unmet.
What the litigation record shows
Overlays are often marketed as a way to reduce legal risk. The public record does not bear that out.
The widget did not prevent the claim.
A regulator’s view of overlay marketing
In 2025 the U.S. Federal Trade Commission required an accessibility-overlay vendor to pay $1 million to settle charges that it deceptively claimed its AI product could make any website WCAG-compliant. The FTC found the tool failed on basic components such as navigation menus, form fields, and image descriptions. The vendor is named in the FTC’s filing; we don’t name it here. The point is the regulator’s position on the marketing claim, not the company.
Sitejar’s approach: fix the source, not the surface
Sitejar takes the approach the standards are written around. Our SURE remediation produces changes to a site’s own source code (the same code the WCAG criteria are measured against) rather than a runtime layer on top of it. A regulator or a court evaluating the page evaluates the real, conformant markup, because that is what changed.
Honest statements start with a remediated site
Sitejar’s Statement Builder helps produce a structured accessibility statement referencing your latest scan. But honesty is only meaningful when it reflects a site that’s actually been remediated. A statement built on overlay-based fixes will describe a site that regulators may reject.