Skip to content
wcagc
←Back to blog
ADAoverlayWCAGlitigation

Are accessibility overlays ADA-compliant?

Overlays don't make a website ADA-compliant. What the ADA requires, what the FTC and courts have said, and what actually lowers your risk.

P

Pavel Charkasau

No. Accessibility overlays are not ADA-compliant, and no product can be, because the ADA attaches to your website and the experience a disabled customer gets from it, not to a script you paste in. The Department of Justice has never approved a widget, a vendor, or a badge as satisfying the law. What DOJ does say is that businesses "have flexibility in how they comply with the ADA's general requirements of nondiscrimination and effective communication," and that they "still must ensure that the programs, services, and goods that they provide to the public ... are accessible to people with disabilities," online ones included (ADA.gov). For state and local government the expectation is now written into regulation: WCAG 2.1 Level AA, at 28 CFR 35.200 (ADA.gov). Overlays have been tested against that expectation in real litigation and did not hold. One 2021 ADA class action named a site that was running accessiBe at the time, and a settlement signed later that year says in its own contract text that overlays "will not suffice to achieve Accessibility." Here is what the record shows.

Does the ADA say anything about overlays?

Not a word. The statute predates the commercial web, and neither the ADA itself nor DOJ's regulations name any product category, approved vendor, or certification scheme. There is no register of blessed tools. That cuts both ways: nothing in the law forbids you from installing an overlay, and nothing in it treats having one as evidence that you complied.

The closest thing to a written technical bar is on the public-sector side. DOJ's 2024 Title II rule sets WCAG 2.1 Level AA as the standard for state and local government web content and mobile apps, and in April 2026 the Department pushed the compliance dates back a year, to 26 April 2027 for entities serving 50,000 or more people and 26 April 2028 for smaller ones (Federal Register). Private businesses under Title III have no dated web rule at all. They are judged on outcome, in court, one plaintiff at a time.

What does the ADA actually require of a website?

That a person with a disability can do what everyone else can do on it. Buy the glasses. Book the appointment. Read the menu and complete the order. Courts and DOJ both frame this as effective communication and equal access rather than as a checklist score, which is why a vendor dashboard reading 98% is not the currency anyone is paying in.

WCAG is the yardstick everyone reaches for because it is the only detailed one that exists. DOJ's own guidance points businesses to it, and WCAG 2.1 AA is what the Title II rule adopted. If you want the criteria in a form your team can work through, the WCAG checklist lays them out one by one. The same standard sits behind Section 508 for federal agencies and their suppliers, and behind EN 301 549 in Europe.

Has a court ever accepted an overlay as ADA compliance?

Not that I can find, and one case is worth knowing in detail. In January 2021 Anthony Murphy, who is blind, sued eyebobs in the Western District of Pennsylvania under Title III. The site was running accessiBe. The complaint alleged that "the overlay fails to provide screen reader users, including Murphy, full and equal access" (complaint PDF). Eyebobs argued the widget had made the site accessible and the claim was moot. The case did not end there; it ended in an October 2021 consent decree committing the company to WCAG 2.1 conformance for its US site, an accessibility coordination team, training, audits, and an outside consultant (Law Office of Lainey Feingold).

Then there is the ADP settlement of 16 December 2021, negotiated by Disability Rights Advocates. Its definitions section is unusually blunt for a contract: "For the purpose of this Agreement, 'overlay' solutions such as those currently provided by companies such as AudioEye and AccessiBe will not suffice to achieve Accessibility" (Law Office of Lainey Feingold). That is not an advocate's opinion in a blog post. It is language a defendant agreed to sign.

What did the FTC say about overlay compliance claims?

It fined the biggest vendor for making them. In January 2025 the Federal Trade Commission announced an order requiring accessiBe to pay $1 million over claims that its accessWidget product could make any website conform to WCAG, including the claim that an automated process finished the job within 48 hours. The Commission approved the final order on 22 April 2025 (FTC). The order bars the company from representing that its automated products make a site WCAG-compliant, or keep it that way, without competent and reliable evidence. accessiBe settled without admitting liability.

Read what that order does and does not do. It did not outlaw overlays, and installing one breaks no law. It penalized the sentence "this makes you compliant." If you bought a widget because someone told you it closed your ADA exposure, that exact promise is the thing a US regulator has now called deceptive.

DOJ made a quieter version of the same point in April 2026, in the preamble to the rule that moved the Title II dates. Explaining why entities needed more time, the Department wrote that "advanced technology, such as generative AI, does not yet reliably automate the remediation of inaccessible content at scale," and that "the less public entities can rely on technology to make their web content and mobile apps accessible, the more they will need to rely on manual work instead" (Federal Register). The regulator wrote a slower timetable specifically because automation cannot do this on its own.

Do overlays reduce the chance of being sued?

The litigation data says no. UsableNet's 2026 midyear report tracks suits filed against companies that already had a widget installed and states that its presence "has not proven to be a meaningful deterrent, legally or practically" (UsableNet). The mechanism is not mysterious. A plaintiff's tester opens the site with the screen reader they use every day and tries to check out. A widget that injects guessed ARIA at runtime does not change the <div onclick> in your template that never became a <button>, so the keyboard trap is still there when a human presses Tab.

The people the tools claim to serve say the same thing. In WebAIM's survey of accessibility practitioners, 67% rated overlays "not at all" or "not very" effective, rising to 72% among respondents who have disabilities themselves (WebAIM). The Overlay Fact Sheet, signed by more than a thousand practitioners including editors of the WCAG, ARIA, and HTML specifications, puts the ceiling in one sentence: "No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard and therefore cannot eliminate legal risk."

My honest opinion, and it is why we built the product the way we did: an overlay optimizes for the buyer's peace of mind, not for the blind customer stuck on your payment step. Those are different jobs, and only one of them is what the ADA is about.

What actually lowers your ADA risk?

Evidence about your own code, and a record of what you did with it.

Start by scanning your real markup against WCAG and getting the failures mapped to the success criterion each one breaks, with the element and selector. Fix those in the source so the change ships with the component and survives a redeploy. Then have a person work through your money flows with a keyboard and a screen reader, because automated testing reaches roughly 30 to 57% of issues by volume and stops where judgement starts (Deque). The W3C says it plainly: evaluation tools "can not determine accessibility, they can only assist in doing so" (W3C WAI). Our scanner will not tell you whether your alt text is meaningful or whether an error message makes sense out loud. A tester will.

Last, write it down. An accessibility statement that says what you tested, what you found, and what you are working on documents effort honestly. A badge claiming a result you cannot demonstrate does the opposite, and after the FTC order it is the riskier thing to publish.

Frequently asked questions

Are accessibility overlays ADA-compliant?

No. Compliance under the ADA belongs to your website and the access it gives disabled users, not to any installed product, and DOJ has never approved a vendor or tool as satisfying the law (ADA.gov). Sites running overlays have been sued and have settled.

Are accessibility overlays illegal?

No. Nothing in the ADA prohibits installing one, and the FTC's action against accessiBe targeted the company's marketing claims rather than the product itself (FTC).

Has an overlay ever worked as a legal defense?

Not in the cases on record. In Murphy v. Eyebobs the site was running accessiBe when the Title III suit was filed, and the matter ended in a consent decree requiring WCAG 2.1 conformance, audits, and training (Law Office of Lainey Feingold). The ADP settlement states in its own text that overlay solutions "will not suffice to achieve Accessibility."

Does the ADA require WCAG for private businesses?

Not by regulation. Title III has no dated web rule, so businesses are judged on whether disabled users get equal access, and DOJ points to WCAG as helpful guidance (ADA.gov). Public entities under Title II do have a written standard: WCAG 2.1 Level AA at 28 CFR 35.200.

Should I remove the overlay I already have?

You can, and it is safe to do. An overlay never edits your source, so deleting the script leaves your HTML exactly as it was. The work that changes your position is fixing the underlying markup and reviewing the flows a scanner cannot judge.

See what your own markup says

If a widget has been standing in for evidence, get the evidence. Run a free scan to see the WCAG failures on your pages, each tied to the criterion it breaks and the element a developer needs to open. Fix them in your code, review the rest by hand, and keep the record. That is the thing a plaintiff's tester, an auditor, or a procurement reviewer can actually check, and it is the only version of this that holds up.

Sources

Written by Pavel Charkasau, founder of wcagc.com. Last updated 20 August 2026.