What an overlay is
An overlay is a script you paste into your site. It loads after your page does, adds a small accessibility icon in a corner, and offers a panel of toggles: bigger text, higher contrast, a reading guide, sometimes a cursor. Some products also claim to repair your page automatically using machine learning.
The pitch is irresistible if you run a business rather than a development team. One line of code, a monthly fee, and a problem you do not understand goes away. That is why so many small businesses have one installed.
The gap between the toggles and the law
Accessibility is not primarily about font size. It is about whether the code underneath your page communicates correctly to the software disabled visitors already use.
A blind customer is not visiting your site and enabling your contrast toggle. They arrive with a screen reader that has been reading web pages to them for years. What that software needs is a button that announces itself as a button, an image that describes itself, a form field bound to its label, and a checkout that can be completed without a mouse. Those are properties of your markup.
An overlay operates in the browser, after the fact, on a page it did not build. It can guess at what an unlabeled button probably does. It cannot know.
Automated repair works acceptably on the obvious cases and unreliably on everything else — and “everything else” is where real customers get stuck. A widget can add a generic label to a nameless icon. It cannot tell that your “Continue” button silently fails because a required field three steps back was never announced.
The people the law protects have said so publicly
The strongest argument against overlays does not come from competitors. It comes from disabled users and from accessibility practitioners, many of them disabled themselves, who have organised public statements objecting to these products. Their recurring complaint is not that overlays are insufficient. It is that overlays actively interfere: the widget duplicates functions their assistive software already performs, injects controls that get in the way, and sometimes rewrites the page underneath them mid-navigation.
This matters commercially, not just ethically. Accessibility claims begin with a real person having a real bad experience on your site. A product that worsens that experience increases the odds of the phone call you are trying to avoid.
Worth knowing before you renew. Overlay vendors’ compliance claims have drawn regulatory scrutiny in the United States, and sites with overlays installed have still been named in accessibility lawsuits. If your vendor’s marketing promised protection, read the actual contract and see what it guarantees. In most cases it guarantees software, not an outcome.
Why “we installed the widget” is a weak position
Where these matters go, the questions tend to be concrete. Can a person complete this transaction with a keyboard alone? Does the screen reader announce the error when the form rejects an entry? Was anything actually tested with the assistive technology at issue?
A subscription receipt answers none of those. Remediation records do: what was tested, what failed, what was fixed, when. Good faith is demonstrated with a paper trail of work, and a widget produces no such trail.
What actually lowers your exposure
- Find out what is really broken. An automated scan catches roughly a third of WCAG issues. It is the right first step and the wrong last one.
- Test with a keyboard. Unplug your mouse and try to complete your own checkout. Ten minutes, and the most revealing thing most owners ever do.
- Fix the four that matter most: image alternatives, text contrast, form labels, keyboard operability. These cover the bulk of what gets found and cited.
- Test with a screen reader. NVDA on Windows and VoiceOver on Mac are free. No tool replaces this step.
- Write it down. Date the audit, date the fixes, keep the record.
- Re-check when the site changes. A new theme or plugin can undo months of work in an afternoon.
Should you rip the widget out today?
Not as step one. It is doing little either way, and removing it changes nothing about the underlying problems. Fix the site first. Once the real issues are gone, most businesses look at that line on their statement and cancel it themselves — because at that point it genuinely is not doing anything.
Common questions
Does an overlay make my website ADA compliant?
No product does that on its own. Overlays adjust presentation after your page loads; they cannot reliably repair the markup assistive technology depends on. Sites running them have still been named in accessibility claims.
Why do screen reader users object to them?
Their software already does text resizing, contrast adjustment and reading modes — better, and tuned to their preferences. An overlay duplicating those functions while rewriting the page can conflict with the tools they depend on.
What actually reduces the risk of a claim?
Fixing the site: semantic markup, labeled fields, sufficient contrast, full keyboard operability, and manual testing with a screen reader — documented as you go.
How much does real remediation cost?
For a typical small-business site it is a project measured in days, not months, and most of the cost sits in the audit rather than the fixes. Start with a free scan so you know the size of the problem before anyone quotes you.
Vertex Web Co. is not a law firm and this article is not legal advice. Accessibility obligations vary by the type of business you run, the states you operate in, and the customers you serve. For questions about your own liability, consult an attorney.