The pitch is irresistible. Add one line of JavaScript to your website and a small accessibility icon appears in the corner. Click it, and a panel offers larger text, higher contrast, and a dyslexia-friendly font. Behind the scenes, the vendor says, artificial intelligence is quietly fixing everything else, and your site is now compliant.
It is a tidy story. It is also wrong.
Accessibility overlays, the widgets sold by companies such as UserWay, accessiBe and AudioEye, are now common on Australian corporate and government websites, including across the New South Wales government sector. They are marketed as a fast, low-cost route to compliance. In 2025 a regulator finally said in plain terms what accessibility specialists have argued for years: an automated overlay does not make a website compliant.
What an Accessibility Overlay Actually Is
An overlay is a third-party script you paste into your site. It loads a floating toolbar that lets visitors change a few presentation settings, and it runs automated routines that claim to detect and repair accessibility problems on the fly.
The important part is what does not happen. Your website's underlying code and content do not change. The overlay sits on top of the page, adjusting a handful of things in the browser after the fact. The barriers in the source are still there.
What Overlays Can Genuinely Do
It is worth being fair about this, because overlays are not pure snake oil. There are two things they do legitimately:
- They offer a few presentation controls. Text size, colour and contrast, letter spacing, a readable font, a reading mask. For a visitor who does not know how to change these settings themselves, that is a small convenience.
- They flag some machine-detectable issues. Automated scanning can spot certain problems, such as an image with no
altattribute or a control with no accessible name.
That is the honest extent of it: conveniences and detection, not conformance. And even the convenience is thinner than it looks. Most of those toolbar features already exist for free in modern browsers and operating systems. A person who relies on larger text or higher contrast usually has it configured already, system-wide, in a way they trust and control.
What Overlays Cannot Do
The hard parts of accessibility are not about presentation. They are about structure, semantics, meaning and interaction, and a script injected after the page loads cannot reliably supply any of them.
- Meaningful alternative text. A machine can detect a missing
altattribute, but it cannot reliably describe what an image means in context. Auto-generated descriptions are frequently wrong, vague or useless. - Semantic structure. Correct headings, landmarks, lists, tables and form labels have to exist in the markup. An overlay cannot rebuild a page's structure from the outside.
- Keyboard operation. Focus order, focus traps, skip links and custom widgets depend on the underlying HTML and scripting, not a toolbar.
- Complex components. Menus, modals, carousels, date pickers and data tables need correct ARIA and behaviour. An overlay cannot impose that without often breaking what was already there.
- Content quality. Plain language, descriptive link text, captions and transcripts are editorial work that no script can write for you.
The automated engine inside every overlay is the same kind of tooling that catches only a fraction of WCAG success criteria. Independent testing consistently puts automated coverage at roughly a third of the criteria; the rest requires human judgement. We cover this in detail in manual versus automated accessibility testing.
Worse, overlays can actively get in the way. Many people who use screen readers and other assistive technology report that overlays interfere with the setup they already rely on, intercept their keystrokes, or announce controls that simply add noise. A public statement signed by hundreds of accessibility professionals and assistive-technology users documents exactly these problems. The tool sold as a help is, for many of its intended beneficiaries, a hindrance.
In 2025, the Regulator Said It Out Loud
For years the overlay industry leaned on confident marketing while the accessibility community pushed back. Then a regulator stepped in.
In January 2025 the United States Federal Trade Commission filed a complaint against accessiBe, and in April 2025 it approved a final order requiring the company to pay one million dollars. The company had claimed its accessWidget product made a website compliant with 30% of WCAG requirements immediately and then used an automated process to reach full compliance with the remaining 70% within 48 hours. The FTC found these claims false, misleading or unsubstantiated.
The order bars accessiBe from representing that its automated product can make any website WCAG compliant, or keep it compliant over time, unless it has the evidence to back the claim. The FTC also acted against reviews that had been dressed up to look like independent, impartial opinion.
This is one of the strongest regulatory statements yet that an automated overlay cannot, on its own, deliver WCAG or ADA compliance. Note what it does and does not do: it does not ban overlays. It bans the promise.
Why This Matters in Australia
The FTC is a United States regulator, but the principle travels. In Australia, the Disability Discrimination Act 1992 applies to digital services, and government bodies are expected to meet WCAG 2.2 Level AA under the Digital Service Standard and state accessibility policies.
A widget bolted onto the front of a site does not create conformance, and it does not, by itself, satisfy the DDA or those standards. When an overlay appears on a government homepage, it can create a comfortable impression that accessibility has been handled. It has not. The unlabelled forms, the keyboard traps, and the images without meaningful descriptions are still there, waiting for the people who actually depend on assistive technology.
And the legal exposure does not disappear. In the United States, hundreds of accessibility lawsuits have named organisations that had an overlay installed at the time. The overlay was not a defence. It was, at best, irrelevant.
The Real Appeal of Overlays, and Why It Is a False Economy
Overlays are popular for one honest reason: they look like the cheap option. A subscription and a single line of code is far less effort than auditing a site, fixing the code, rewriting content and testing with real users. For a team that does not want to invest in the quality of what it is shipping, an overlay is a way to appear to act without doing the work.
But it is a false economy. You pay the subscription every year. You still carry the legal and reputational risk. You have not removed a single underlying barrier. And the people you were meant to include are still locked out, often more frustrated than before. The shortcut costs more over time than doing the job properly, and it buys you none of the benefit.
This is the heart of it. Accessibility is not a button or an add-on; it is quality assurance. A widget is the opposite instinct: bolt something on at the end and hope it covers the gap. It does not.
What Actually Works
There is no widget for this, but there is a well-understood path:
- Audit the real thing. Test the site against WCAG 2.2 using a combination of automated tooling and manual expert review. See audit and compliance.
- Fix the code and the content. Correct the semantics, labels, focus order, alternative text and structure in the source, not on top of it.
- Test with people who use assistive technology. Nothing substitutes for watching a screen reader user, a keyboard-only user or a voice-input user attempt real tasks. See assistive-technology user testing.
- Prove it for procurement. Capture conformance in evidence a buyer can rely on, such as an Accessibility Conformance Report or VPAT, rather than pointing at a toolbar.
- Embed it so it lasts. Build accessibility into design, development, content and procurement through organisational uplift, so new barriers stop appearing in the first place.
The Question to Ask in Procurement
If you are buying or building a digital product, the useful question is not whether a particular overlay vendor is reputable or still in business. It is whether an overlay-based approach is sufficient. In 2026, the answer from regulators, disability organisations and the overwhelming majority of accessibility experts is no.
So ask vendors for evidence of conformance, not a screenshot of a widget. Ask how they test, who they test with, and what their most recent WCAG 2.2 audit found. A supplier who is confident in their accessibility will have answers. A supplier who points at an overlay is telling you they took the shortcut.
The Bottom Line
An accessibility overlay can adjust a few settings and flag a few problems. It cannot make your website accessible, it cannot make you compliant, and as of 2025 a regulator has fined a vendor for saying otherwise. If accessibility matters to your organisation, and legally, commercially and ethically it does, the work has to happen in the code, the content and the culture, not in a script pasted over the top.