Why Accessibility Overlays Don't Work (And What the DOJ Actually Requires)

What Overlays Are and What They Claim

Accessibility overlays are third-party JavaScript widgets that inject themselves into your website and attempt to modify the user interface in real time. They typically appear as a small icon, often a wheelchair symbol or an accessibility badge, fixed to the corner of every page. When clicked, they open a panel of controls that let visitors adjust font sizes, toggle high-contrast modes, highlight links, pause animations, and enable other presentation modifications.

Overlay vendors market these products as comprehensive compliance solutions. The typical sales pitch goes something like this: install one line of JavaScript, and our tool automatically detects and fixes accessibility issues across your entire site. Some vendors specifically claim WCAG 2.1 AA or ADA compliance. Some claim their tools use artificial intelligence to remediate issues in real time.

For a government IT director facing a federal deadline with limited budget and staff, this sounds like exactly the right answer. It is not.

Why Overlays Fail: The Technical Reality

The fundamental problem with overlays is that they do not fix the underlying code. They add a cosmetic layer on top of a broken foundation. Consider the most common accessibility violation on government websites: images without alt text. An overlay cannot know what is in your photos. It cannot determine whether the image on your parks page is a playground, a trail map, or a decorative border. Some overlay vendors claim their tools use image recognition to generate alt text automatically. In practice, this produces descriptions like "photo of building" or "image of people outside," descriptions that fail to convey the information a sighted resident would get from the image.

The same limitation applies to nearly every category of WCAG violation. Overlays cannot fix heading structures baked into your content management system. They cannot make a PDF form fillable and accessible. They cannot add proper labels to form fields that were built without them. They cannot restructure a data table that was coded without proper header associations. They cannot make a custom JavaScript widget keyboard-navigable when the widget was not designed for keyboard interaction.

WCAG 2.1 AA has 50 success criteria. Independent research has consistently found that overlays address, at most, a handful of the Perceivable criteria related to text size and color. The vast majority of Operable, Understandable, and Robust criteria are simply beyond what a client-side JavaScript widget can remediate.

The Accessibility Community Has Been Clear

The National Federation of the Blind, the oldest and largest organization of blind Americans, has taken a formal position against accessibility overlays. Their statement is direct: overlays do not provide effective access and their use can actually make websites harder to navigate for people who rely on assistive technology. Screen reader users frequently report that overlays interfere with the tools they already use, creating new barriers instead of removing existing ones.

Over 800 accessibility professionals, advocates, and organizations have signed an open letter calling on the web community to reject overlay products. The letter details how overlays can break existing assistive technology compatibility, generate misleading compliance claims, and create a false sense of security for organizations that adopt them.

Multiple overlay vendors have themselves been named as defendants in accessibility lawsuits, with plaintiffs arguing that the overlay products failed to provide the access they promised. In the first half of 2025 alone, 456 ADA lawsuits, 22.6% of all web accessibility cases filed, targeted websites actively using overlays or widgets. The overlay was not a shield. It was a flag.

What the DOJ Actually Requires

The DOJ's Final Rule is unambiguous: 28 CFR § 35.200(b)(1) requires web content to "conform to WCAG 2.1 Level AA." The rule evaluates actual HTML, CSS, and JavaScript content, not a presentation layer widget added on top of it.

This distinction is critical. The DOJ evaluates whether your web content itself meets the 50 WCAG success criteria. An overlay that modifies the presentation layer while leaving the underlying code non-conformant does not satisfy the rule. Your site either conforms at the code level or it does not.

This is not a hypothetical scenario. It has played out in multiple jurisdictions across the country. Government entities that relied on overlays have faced enforcement actions despite having paid for a "compliance solution."

What Remediation-First Actually Looks Like

Real accessibility compliance starts with measuring what is actually wrong, then fixing the code itself. This is the approach AuditAble was purpose-built for:

Making the Case Internally

If your council or budget committee is asking "why not just buy an overlay widget for $49 a month," here is how to frame the response: the overlay does not eliminate legal risk. It does not satisfy the DOJ's technical standard. And it does not actually help the residents who need accessible web content. An overlay is spending money to feel compliant without being compliant. If your organization has already purchased one, the conversation is the same: the legal exposure remains until the underlying code is fixed. Real remediation costs more upfront but eliminates the ongoing risk of enforcement, complaints, and the inevitable re-do.

The good news is that understanding your actual compliance posture is free. A scan takes minutes and gives you the objective data you need to make an informed decision. If your site scores well, you may need far less remediation work than you expect. If it does not, you will know exactly what to fix and in what order.