You have probably seen them. A small icon in the corner of a website that, when clicked, opens a panel offering to increase text size, change colors, adjust spacing, or “enable accessibility mode.” Maybe you have seen advertisements for AI powered accessibility overlays that promise to make your entire website compliant with the ADA in a single line of code.

These products sound incredibly appealing. They are cheap, fast, and require no changes to your actual website. For organizations that are worried about accessibility lawsuits or want to do the right thing but do not have the budget for a full audit, overlays can feel like the perfect solution.

But there is a problem. Accessibility overlays and widgets do not work the way their marketing claims. In many cases, they make the experience worse for the very users they are supposed to help. Disabled users, accessibility advocates, and even the organizations that create these tools have acknowledged that overlays are not a substitute for real accessibility work.

In this article, we will explain what accessibility overlays are, why they fail, what the disability community and legal experts say about them, and what you should do instead to build a website that is genuinely accessible to everyone.

What Are Accessibility Overlays and Widgets?

Accessibility overlays are third party tools that you add to your website, usually by inserting a single JavaScript snippet into your page templates. Once installed, they scan your page content and attempt to fix accessibility issues automatically, or they present users with a toolbar of options to customize the display.

There are two broad categories of overlay products on the market.

Automated Fix Overlays

These tools run in the background when a user loads your page. They use JavaScript to scan your HTML and attempt to automatically correct accessibility issues. For example, they might:

  • Add alt text to images using AI image recognition.
  • Add ARIA roles and attributes to elements that are missing them.
  • Try to fix heading structures.
  • Attempt to make custom widgets keyboard accessible.
  • Adjust color contrast by modifying your CSS on the fly.

The idea is that the overlay repairs your site in real time so you never have to touch your source code. The reality is that these automated fixes are unreliable, incomplete, and sometimes actively harmful.

User Interface Widgets

These tools present a toolbar or panel that lets users customize how they see your site. Users can typically:

  • Increase or decrease text size.
  • Switch to a high contrast color scheme.
  • Change the font to one designed for dyslexic readers.
  • Adjust line height and letter spacing.
  • Emphasize links and headings.
  • Enable a “text to speech” reader.

These features sound helpful, and some individual users do find value in them. But there are critical problems with relying on them as your accessibility strategy.

Why Accessibility Overlays Fall Short

The core promise of accessibility overlays is that you can achieve compliance without doing the actual work of making your website accessible. This promise is false. Here is why.

1. Overlays Cannot Fix Structural Problems

Many accessibility issues are structural. They are baked into the HTML, the design, the content, and the way the site is built. An overlay running on top of a badly built website cannot fix these problems:

  • If your page has no headings, the overlay can insert some, but it has to guess where they belong. It will often guess wrong.
  • If your forms have no labels, the overlay can try to generate labels from placeholder text or nearby text, but this is unreliable and often produces nonsensical labels.
  • If your custom widgets are built with non semantic elements, the overlay can add ARIA roles, but it cannot add the keyboard interaction logic that makes those roles meaningful.
  • If your page has a confusing reading order due to poor HTML structure, the overlay cannot reorder the content.

Structural accessibility problems require structural fixes. You need to edit your source code, redesign problematic components, and rewrite unclear content. No JavaScript snippet can do this reliably.

2. Overlays Interfere With Assistive Technology

This is one of the most serious problems. Many overlay tools attempt to “help” assistive technologies by adding extra ARIA attributes, modifying the DOM, or injecting new elements. But assistive technologies like screen readers already have their own ways of interpreting web content. When an overlay adds unexpected attributes or restructures the page on the fly, it can break the experience that screen reader users depend on.

For example, an overlay might add aria-label attributes to buttons that already have clear text labels, causing the screen reader to announce redundant or conflicting information. An overlay might wrap elements in new containers that change the reading order. An overlay might inject invisible elements that screen readers pick up and announce, confusing the user.

Screen reader users spend years learning how their software works with standard web pages. When an overlay changes the expected behavior, it can make the page harder, not easier, to use.

3. Overlays Create a False Sense of Compliance

When you install an accessibility overlay, you might feel that you have “done accessibility.” You can point to the widget in the corner of your site and tell yourself, your stakeholders, and your legal team that your site is accessible.

But accessibility is not a widget. It is a property of your website’s design, code, and content. An overlay does not make your site compliant with WCAG or the ADA. It simply adds a layer on top of a site that may still have dozens or hundreds of unresolved accessibility issues.

This false sense of security is dangerous. If a user files an ADA complaint or a lawsuit, the presence of an overlay will not protect you. In fact, as we will discuss below, it may actually draw attention to the fact that you knew accessibility was a concern but chose a shortcut instead of a real solution.

4. Automated Alt Text Is Unreliable

Many overlay products use AI to generate alt text for images that are missing it. This sounds great in theory. In practice, AI generated alt text is often inaccurate, vague, or actively misleading.

An AI might describe a photo of a team meeting as “people sitting in a room.” That is technically correct but useless to a screen reader user who needs to understand that this is a photo of the company leadership team at their annual planning retreat. The AI does not know the context, the purpose of the image, or what information the user needs.

Worse, AI might hallucinate details that are not in the image, creating alt text that is factually wrong. A screen reader user who trusts this alt text will form an incorrect mental model of the page.

Good alt text requires human judgment. It requires understanding the context in which the image appears and what information the image conveys to the user. No automated tool can do this reliably.

5. Overlays Add Performance and Privacy Concerns

Overlays are JavaScript heavy. They add extra scripts that run on every page load, which can slow down your site. For users on slow connections or older devices, this performance hit can be significant.

Some overlay products also collect data about your users, including information about what accessibility features they use. This raises privacy concerns, especially since disability related data is sensitive information that may be subject to additional legal protections.

6. Users Do Not Want Them

Perhaps the most compelling argument against overlays comes from the disability community itself. In 2021, a group of over 700 accessibility advocates and organizations, including the National Federation of the Blind and the American Council of the Blind, signed an open letter calling on organizations to stop using accessibility overlays.

The letter pointed out that overlays do not make sites accessible, that they often make sites harder for disabled users to navigate, and that they give organizations a false sense of having addressed accessibility. The advocates asked organizations to invest in real accessibility work instead.

This is not a fringe opinion. It is the consensus of the people who are most affected by these tools. When the users you are trying to serve tell you that a solution does not work, you should listen.

The legal landscape around accessibility overlays is also concerning for organizations that use them.

Overlays Do Not Protect You From Lawsuits

An overlay does not make your website compliant with the ADA or WCAG. If your site has accessibility issues that prevent a disabled user from accessing it, the overlay’s presence does not change that fact. You can still be sued, and the overlay will not serve as a defense.

In fact, there have been cases where organizations with accessibility overlays installed were still sued for ADA violations. The overlay did not prevent the lawsuit, and in some cases, the plaintiffs specifically cited the overlay as evidence that the organization was aware of accessibility concerns but failed to address them properly.

Some Overlay Companies Have Been Sued Themselves

Several companies that sell accessibility overlay products have faced lawsuits alleging that their own products do not comply with accessibility standards. If the company making the tool cannot make its own website accessible, that should give you pause about relying on their product to fix yours.

The Department of Justice Has Weighed In

The Department of Justice has stated that the ADA applies to websites and that organizations need to make their web content accessible. The DOJ has not endorsed accessibility overlays as a compliance solution. Their guidance consistently points to WCAG as the standard, and WCAG compliance requires fixing the underlying issues in your code and content, not slapping a widget on top.

For more on ADA requirements, see our guide on whether all websites have to be ADA compliant.

When Overlays Might Have Limited Value

To be fair, not every feature of every overlay is useless. Some individual features can provide value in specific situations:

  • Text size adjustment can help users with low vision who are not already using browser or system level zoom.
  • High contrast modes can help some users, though most operating systems already provide this feature at the system level.
  • Reading guides and focus indicators can help some users with attention or cognitive disabilities.
  • Text to speech can be useful for users who want content read aloud but do not use a full screen reader.

However, these features are supplements, not substitutes for accessibility. They benefit some users some of the time. They do not make your site accessible to users who depend on screen readers, keyboard navigation, or other assistive technologies that interact with your site’s actual HTML and code.

If you do choose to add a customization widget, it should be in addition to making your site genuinely accessible, not instead of it. And you should test the widget itself for accessibility, because some overlay widgets are not keyboard accessible or screen reader friendly.

What to Do Instead: Building Real Accessibility

If overlays are not the answer, what is? The answer is the one that takes more effort but actually works: make your website genuinely accessible from the ground up. Here is how.

1. Audit Your Current Site

Start by understanding where your site stands. Run an automated accessibility scan to identify technical issues like missing alt text, improper headings, unlabeled form fields, and contrast failures. Then do a manual review to catch the issues that automated tools miss, such as confusing link text, illogical reading order, or custom widgets that do not work with keyboards.

Accessible Metrics can run a comprehensive scan of your site against WCAG 2.1 AA standards and give you a prioritized report of what needs fixing. This is your roadmap for real accessibility work.

For a broader testing approach, see our guide on how to test the accessibility of your website.

2. Fix the Issues in Your Code

Once you know what the problems are, fix them at the source. This means:

  • Adding meaningful alt text to every image that conveys information.
  • Using semantic HTML elements (<button>, <nav>, <main>, <h1> through <h6>) instead of generic <div> and <span> elements.
  • Associating every form field with a proper <label>.
  • Ensuring your heading structure is logical and complete.
  • Writing descriptive link text instead of “click here” or “read more.”
  • Making sure all interactive elements are keyboard accessible.
  • Ensuring your color contrast meets WCAG AA standards.
  • Writing clear, plain content that is easy to understand.

These are not one time fixes. They are changes to the way you build and maintain your website. For a practical checklist, see our complete ADA compliance website checklist.

3. Design With Accessibility in Mind

Accessibility starts at the design stage, not at the development stage. When you design a new page or feature, consider accessibility from the beginning:

  • Choose color combinations that meet contrast requirements before you build.
  • Plan your heading structure before you write the HTML.
  • Design forms with visible labels and clear instructions.
  • Ensure interactive elements have large enough touch targets.
  • Design for keyboard navigation from the start, not as an afterthought.

For more on this approach, see our guide on how to design for accessibility when building a new website.

4. Test With Real Users and Real Tools

Automated scans catch a significant portion of accessibility issues, but they cannot catch everything. Manual testing is essential:

  • Navigate your site with only a keyboard to check keyboard accessibility. See our guide on keyboard accessibility for how to do this.
  • Test with a screen reader like NVDA or VoiceOver to experience your site the way blind and low vision users do.
  • Check your site on mobile devices to ensure it works on every screen size. See our guide on mobile web accessibility.
  • If possible, involve users with disabilities in your testing process. They will find issues that no tool or sighted tester can.

5. Train Your Team

Accessibility is not one person’s job. It is everyone’s responsibility. Train your designers, developers, content writers, and project managers on accessibility principles and WCAG requirements. When everyone on the team understands accessibility, issues are prevented before they are created.

For getting started with team training, see our guide on basic ADA website accessibility training.

6. Make Accessibility an Ongoing Practice

Accessibility is not a one time project. It is an ongoing practice. Every time you add a new page, publish a new blog post, or launch a new feature, you need to check it for accessibility. Build accessibility checks into your content workflow and your development process so that accessibility is part of how you work, not an extra task you add at the end.

For understanding the testing workflow, see our article on automated vs manual accessibility testing.

The Real Cost Comparison

Overlay companies often market their products as a cheaper alternative to real accessibility work. Let us compare the real costs.

An accessibility overlay might cost a few hundred to a few thousand dollars per year, depending on your site size and the provider. In exchange, you get a widget that may help some users customize their experience but does not make your site genuinely accessible or protect you from legal risk.

Real accessibility work costs more upfront. A professional audit, remediation work, and ongoing testing require an investment of time and money. But the return on that investment is significant:

  • Your website actually works for disabled users, not just in theory but in practice.
  • You reduce your legal risk because you are addressing the root causes, not patching symptoms.
  • Your site is better for everyone. Semantic HTML, clear content, and good contrast benefit all users, not just those with disabilities.
  • Your SEO improves. Search engines reward well structured, semantic, accessible content. See our guide on web accessibility and SEO for more on this connection.
  • You build trust and goodwill with the disability community and your broader audience.

When you frame it this way, the question is not whether you can afford to do real accessibility work. The question is whether you can afford not to.

Signs an Overlay Is Not Enough

If you already have an overlay installed, how do you know whether it is actually working? Here are some warning signs:

  • Your automated accessibility scan still shows dozens of issues. The overlay may claim to fix them on the fly, but the underlying issues are still in your code.
  • Screen reader users complain about your site or report that it is confusing to navigate. The overlay is interfering rather than helping.
  • Your site loads slowly, especially on mobile devices. The overlay’s JavaScript is adding performance overhead.
  • Keyboard users report that they cannot reach or operate the overlay widget itself, or that it traps focus on certain elements.
  • You are relying on the overlay’s dashboard to tell you your site is “compliant.” No overlay company can guarantee compliance. Only a real audit against WCAG can tell you where you stand.

If any of these sound familiar, it is time to move beyond overlays and invest in real accessibility.

The Bottom Line

Accessibility overlays are appealing because they promise something for almost nothing: compliance, inclusivity, and legal protection without changing a single line of your website’s code. But that promise is not real. Overlays cannot fix structural problems, they often interfere with the assistive technologies they claim to support, and they give organizations a false sense of security while leaving the real work undone.

The disability community has spoken clearly on this issue. Overlays are not a substitute for accessibility. Real accessibility means building your website so that it works for everyone, from the ground up, using semantic HTML, clear content, proper design, and thorough testing.

It takes more effort. It takes more time. But it is the only approach that actually works. And when you get it right, you create a website that is better for every single person who visits it.

Ready to find out where your site really stands on accessibility? Do not settle for an overlay that promises compliance without delivering it. Run a free accessibility scan with Accessible Metrics and get a detailed report against WCAG 2.1 AA standards. You will see exactly what needs fixing and get a clear roadmap for making your site genuinely accessible to every user.