Acute SEO Team 
Written by Derrick Tulali — SEO Expert with 9+ Years Experience
If you run a business website and someone told you that a single line of JavaScript could make your site ADA compliant, you probably felt relieved. That pitch is exactly what accessibility overlay companies have been selling for years. In 2026, those tools are more popular than ever — and more controversial than ever.
This post breaks down what overlays actually do, where they fall short, and what courts and regulators actually look for when a complaint lands on your doorstep.
What an Accessibility Overlay Actually Is?
An accessibility overlay is a third-party script you add to your website. Once loaded, it injects a widget — usually a small icon in the corner of the page — that gives users options like increasing font size, switching to high contrast mode, or enabling a “screen reader” mode. The pitch is that this widget detects and fixes accessibility problems automatically, without requiring any changes to your underlying code.
Popular overlay products include AccessiBe, UserWay, AudioEye, and EqualWeb. Some of these companies market directly to small businesses, billing their tools as instant compliance with the Web Content Accessibility Guidelines (WCAG) 2.1 and ADA requirements. Prices typically run anywhere from $49 to a few hundred dollars per month, depending on site size.
The appeal is obvious. A manual accessibility audit followed by remediation work can cost thousands of dollars and take weeks. An overlay is cheap, fast, and comes with a compliance certificate you can point to if anyone asks.
Why Overlays Keep Getting Sued?
Here is the problem: courts have not been kind to overlay defenses. Multiple lawsuits filed against businesses using overlay products have proceeded even after the business pointed to the widget as proof of compliance. In several cases, plaintiffs demonstrated that the overlay failed to fix the actual barriers that prevented them from using the site.
The DOJ’s 2024 web accessibility rule set a clear standard for state and local government entities under Title II of the ADA, and it explicitly uses WCAG 2.1 Level AA as the technical benchmark. Private businesses under Title III are held to the same standard in practice, because that is what courts consistently reference when evaluating whether a site is accessible.
An overlay does not rewrite your HTML. It does not fix broken ARIA labels baked into your template. It does not correct a form that has no programmatic label, which means a screen reader user hears “edit text” with no context about what they are supposed to type. It does not repair keyboard navigation flows that skip interactive elements or trap focus inside a modal. These are structural problems. A widget sitting on top of your code cannot reach inside and fix them.
The National Federation of the Blind and other disability advocacy groups have published open letters specifically calling out overlay tools as inadequate. Researchers at Search Engine Journal and accessibility-focused publications have documented cases where overlays introduced new barriers rather than removing existing ones — for example, by conflicting with the actual assistive technology a user already had running.
What WCAG 2.1 Level AA Actually Requires?
WCAG Level AA covers about 50 individual success criteria across four categories. Many of those criteria require things that happen at the code level: proper heading structure, sufficient color contrast ADA standards (a minimum ratio of 4.5:1 for normal text), descriptive link text, ARIA labels on interactive elements, focus order that follows the visual layout, and captions on video content.
A color contrast checker widget can tell a sighted user to switch to high contrast mode. But a user who relies on a screen reader and never sees the visual interface at all gets no benefit from that. The underlying contrast failure in the code is still there. The WCAG requirement is that the content itself meets the standard — not that a workaround exists.
Keyboard navigation is another area where overlays consistently fail. A user who cannot use a mouse should be able to tab through every interactive element on your page in a logical order, activate buttons with the Enter or Space key, and never get stuck in a focus trap. If your site was built without those behaviors coded in, an overlay cannot add them reliably. Overlays try to script their way around these issues, and the results are inconsistent across different browsers and assistive technologies.
What Actually Works?
Real compliance comes from fixing the source code. That means an audit that identifies specific failures — not just a scan report — followed by development work to address each one. The most durable approach builds accessibility into the site architecture from the start, including semantic HTML, proper heading hierarchies, descriptive alt text, labeled form fields, and tested keyboard behavior.
Automated scanning tools catch roughly 30 to 40 percent of WCAG failures, according to research published at Deque Systems and cited widely in the accessibility community. The rest require human judgment. A tool can tell you that an image is missing alt text. It cannot tell you whether the alt text you wrote is accurate or useful.
Acute SEO AI combines automated scanning with structured remediation through its AI accessibility service, which identifies failures at the code level and supports actual fixes rather than cosmetic workarounds. That distinction matters enormously if you ever need to demonstrate compliance to a plaintiff’s attorney or a federal agency. You can also see what our clients say about working with a team that treats accessibility as a technical problem with real solutions.
The Honest Risk Calculation
Some business owners decide the lawsuit risk is low enough that an overlay is an acceptable stopgap while they budget for real remediation. That is a business decision, and it is not entirely unreasonable for very small sites with limited resources. But you should make that decision with accurate information.
An overlay does not make you compliant. It gives you something to point at, which is not the same thing. If a blind user files a complaint and their attorney can demonstrate that the site remained unusable despite the overlay, the widget becomes evidence of awareness rather than a defense. Courts have ruled this way.
If you are serious about protecting your business and serving all of your users, the path forward is a real audit and real fixes. For a closer look at what that process involves, explore our accessibility tools or schedule a consultation with our team to talk through your specific situation.
