Why an accessibility overlay won't protect you under ADA Title II

Accessibility overlays go by many names: widgets, plugins, toolbars, AI accessibility solutions. The pitch is always similar. Add our script, and your site becomes accessible and compliant automatically. If only it worked that way.

What an overlay actually is

An overlay is third-party code that loads on top of your existing site and tries to adjust it in the browser: changing contrast, resizing text, or attempting to patch the page for screen readers. It never changes the underlying code of your site. It sits on top of the problem rather than fixing it.

That distinction is the whole story. Accessibility conformance is a property of your actual content and code: the headings, labels, focus order, alt text, and keyboard behavior that ship in the page. A layer that runs after the fact cannot reliably rewrite all of that, and it often introduces new problems of its own.

Why it does not hold up

• Many screen reader and assistive technology users report that overlays interfere with the tools they already rely on, and a number actively block these scripts.
• Automated detection catches only a portion of real accessibility barriers. The issues that get people stuck, like an unusable custom form or a confusing flow, usually need human judgment to find and fix.
• Courts in the United States have continued to allow accessibility claims to proceed against sites that had an overlay installed. Adding a widget has not made the lawsuits go away.
• Regulators have taken action against accessibility vendors for overstating what automated tools can do. "It is automatic" is a marketing claim, not a legal shield.

If a tool could make any website compliant with one line of code, accessibility consultants, disabled testers, and the entire field of inclusive design would not exist.

What the Title II rule actually expects

The Department of Justice rule on web and mobile accessibility for state and local governments points at a recognized technical standard (WCAG) and expects your content to conform to it. It is about the experience your pages deliver, not about whether you have purchased a particular product. An overlay does not satisfy that, because it does not make your underlying content conform. For the specific standard and deadlines that apply to your type of entity, see our ADA Title II overview.

Where widgets do help, honestly

This is not an argument that assistive toolbars are worthless. A good toolbar can give visitors useful, optional controls: larger text, a reading guide, contrast preferences, and similar comfort features. That is a genuine enhancement on top of an accessible site. The problem is only when a widget is sold as a substitute for making the site accessible in the first place. Enhancement, yes. Replacement, no.

What a defensible position looks like

• Know your real status. Start with a scan to surface issues, then a human audit to catch what automation misses.
• Fix at the source. Remediate the actual code and content so the page conforms for everyone, with or without a widget.
• Verify with people. Have real assistive technology users confirm that key tasks can be completed.
• Document the work. An accessibility statement and a clear remediation record show good-faith, ongoing effort.

That combination, automation plus human-verified remediation plus documentation, is what stands up to both a real user and a real complaint. A script on top of an unchanged site does not.