The Problem With Accessibility Overlays

Accessibility overlays and widgets are marketed as a quick and convenient fix to make websites accessible. For companies under pressure to comply with standards such as ADA and WCAG, this is an attractive proposition. But in reality, they fail to detect many accessibility issues and may not protect organizations from compliance violations and lawsuits. Find out why accessibility overlays are not a viable solution to accessibility.

What do accessibility overlays actually do?

Accessibility overlays are automated website add-ons designed to improve digital accessibility through various means. By adding a JavaScript snippet to a site, overlays can alter the page appearance for the visitor. Typically, a widget is displayed on the website, containing a range of controls that allow the user to customize the website experience — for example, by changing the font size, adjusting contrast and colors, or reducing motion.

For organizations trying to navigate the complexities of accessibility, overlays can look like an obvious shortcut. Fixing accessibility issues means auditing every page, prioritizing a backlog, and coordinating fixes across design, development and QA. An overlay promises to skip that process entirely: just install a script, pay a monthly subscription and your website will be accessible. Why invest in fixing issues in the backlog when a widget for $99 a month claims to fix them automatically? The promise of high speed and low cost appeals directly to teams under regulatory pressure or with limited resources.

It’s important to note that overlays do not alter the website code. Instead, they just place a “one-size-fits-all” interface on top of a faulty foundation. Even custom overlays that are tailored to a specific website do not edit the source code, only the live, in-browser representation that the visitor sees. And this is one of the inherent limitations of accessibility overlays.

Why accessibility overlays are not a viable solution

Accessibility issues can be divided into two categories:

• Objective issues, which can be detected through a fixed set of programmatic rules. Examples include missing alt attributes, insufficient color contrast ratios, unlabeled form fields and missing heading structure. These are the issues automated tools are built to catch.
• Subjective issues, which require human judgment to evaluate. Examples include whether alt text actually describes what's meaningful in an image, whether a page's reading order makes sense to someone navigating by screen reader, whether an error message is understandable, and whether a custom-built menu behaves predictably under keyboard-only navigation.

Overlays can only attempt to address objective issues, often inaccurately. They are structurally incapable of addressing the subjective issues that shape much of the real user experience for people with disabilities. 

From a user experience standpoint, overlays fall short because they impose a generic experience onto a foundation that wasn't built to support it, rather than solving underlying issues. This produces four distinct failures for the people they're meant to help:

1. Interference: Many users already rely on screen readers, switch controls, or other assistive technology they've configured precisely to their own needs. Overlays frequently clash with these existing setups, making screen reader behavior less reliable. 
2. Friction: A well-built site should work the same way for everyone from the moment it loads. Overlays require users to actively locate and activate a separate widget before the site becomes usable. This immediately signals to users that the product wasn’t designed for them and inclusion was an afterthought.
3. Forced disclosure: Using an overlay introduces privacy and civil rights concerns by forcing users to self-identify as having a disability just to access basic functionality. This compromises user privacy and creates an unequal barrier for people who shouldn’t have to reveal personal information simply to browse a website.
4. Incomplete fixes: Complex interface elements, like nested navigation and dynamic forms, are exactly where overlays tend to fail, since these require the kind of contextual repair a script can't perform. The result is a half-fixed website, which in practice can be more frustrating than a site with known issues. 

What do regulatory bodies say about accessibility overlays?

In one prominent case in early 2025, the Federal Trade Commission (FTC) took action against the provider of an AI-powered web accessibility plug-in. The software provider had claimed its tool could make websites WCAG compliant — a claim which the FTC found to be false, misleading or unsubstantiated. The FTC’s complaint further noted that overlays are “not intended to permanently alter web code or design, but to permit temporary modifications to the user interface.”

Legal metrics reflect this reality. Industry tracking and court data shows that roughly a quarter of all ADA digital accessibility lawsuits in 2024 explicitly targeted websites running overlay widgets. Far from offering legal immunity, these tools serve as a public signal to plaintiff attorneys that a site has unresolved, root-level compliance gaps. 

European regulatory bodies have also spoken out against accessibility overlays. The European Commission directly states that “no automated tool can cover all the WCAG 2.1 level A and AA criteria.” Instead, it recommends, “It is best to fix accessibility issues at their source.” Germany's federal accessibility monitoring body BFIT-Bund echoed this sentiment in its most recent assessment, stating that:

“At present, most overlay tools promise an improvement in website accessibility that they often cannot deliver [...] Using an overlay tool does not relieve the responsible parties of the fundamental obligation to design the website to be accessible.”

Source: BFIT-Bund (German)

Alternatives to accessibility overlays

The fact is that there is no “silver bullet” to making digital experiences accessible. Instead, organizations need to adopt a new mindset toward accessibility and combine multiple approaches and tools. These five recommendations can make a meaningful difference:

• Test with real assistive technology users. People who rely on screen readers, switch controls or other assistive technology every day find issues that no simulated test can. Their perspective and lived experience will always provide more insight than an automated tool can.
• Combine automated and manual testing. Automated scanning is useful for catching rule-based issues at scale and continuously, but it needs to be paired with manual testing to catch what it structurally cannot.
• Build in accessibility from the start. A truly accessible product is designed and developed according to accessibility requirements from the outset. This costs less to maintain than retrofitting fixes after launch, and avoids the recurring rediscovery of the same issues.
• Fix issues at the source. Correcting the underlying HTML, CSS and JavaScript — as opposed to patching the rendered output — produces a change that persists independent of any script or subscription.
• Make it continuous. Accessibility testing integrated across the development lifecycle catches issues as they're introduced, rather than treating accessibility as a one-time audit disconnected from ongoing releases.

How accessibility overlays compare with real-world testing

Why real-world accessibility testing is essential

Believing that any single solution can fix a website’s accessibility issues is missing the point of accessibility as a concept. Accessibility should not be viewed as a one-off process or a problem to be ironed out. Instead, it should be seen as an ongoing quality standard to uphold. When organizations bake accessibility into their development process, the resulting product improvements can benefit all users. 

The inherent problem with overlays is that they treat accessibility as something that can be bolted onto a finished product. Real-world testing treats it as a property of the product itself — one that has to be verified by the people it's meant to serve. 

Applause's accessibility testing combines AI-assisted scanning with manual evaluation from people who use assistive technology every day, testing across real devices, browsers and configurations. That combination covers gaps that overlays cannot address, including contextual judgment, subjective experience and usability — delivered continuously rather than as a one-off audit.

Contact our experts to discuss how we can help you meet your accessibility goals.