Accessibility Overlay Widgets: Do They Make Your Site Compliant?
Can an accessibility overlay make your website compliant? What overlays can and cannot do, the FTC's accessiBe order, and what real fixes involve instead.
No, an accessibility overlay will not on its own make your website compliant. An overlay is a script or plug-in that adds a toolbar or automated adjustments on top of your existing site, but the barriers disabled people meet are usually in the site itself: its structure, forms, images, colours and keyboard behaviour. The US Federal Trade Commission ordered one major vendor, accessiBe, to pay $1 million over claims that its widget could make any website compliant with the Web Content Accessibility Guidelines. The reliable route is to test the site and fix the code.
Key takeaways
- An accessibility widget sits on top of your pages; it does not rebuild the underlying code where most barriers live.
- In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million and barring claims that its automated products can make any website WCAG-compliant without evidence.
- The W3C says evaluation tools cannot determine accessibility on their own, and that human judgement is required.
- In the UK, the Equality Act 2010 applies the duty to make reasonable adjustments to service providers, and for many businesses the website is one of the ways they provide a service.
- Real fixes start with an audit against WCAG 2.2, then changes to templates, components and content.
What is an accessibility overlay?
An accessibility overlay, sometimes sold as an accessibility widget or accessibility plugin for WordPress, is a piece of third-party code you add to your site, often with a single line or a plug-in install. It usually shows an icon that opens a panel of options such as larger text, higher contrast or a readable font, and some products also claim to detect and repair problems automatically.
The appeal is obvious. It is quick, it is cheap compared with a development project and the sales pitch often promises compliance. For an owner who has just been told the site has accessibility problems, a one-line fix sounds like the answer.
The trouble is where the problems are. A missing form label, a menu that cannot be used with a keyboard, a button that is really an image or a heading structure that makes no sense to a screen reader are all part of the page's code and content. A layer on top can try to patch some of them, but the source stays the same, and every new page or update can bring the same problems back.
Do accessibility overlays make a site compliant?
The clearest answer comes from a regulator. In January 2025 the FTC announced a proposed order against accessiBe, and in April 2025 it approved the final order. According to the FTC's press release, the agency alleged that accessiBe claimed its accessWidget plug-in could make any website compliant with WCAG, and that those claims were false, misleading or unsubstantiated because the product did not make all user websites WCAG-compliant.
The final order requires accessiBe to pay $1 million. It bars the company from claiming that its automated products can make any website WCAG-compliant, or keep it compliant over time, unless it has evidence to support the claim. The FTC also alleged that accessiBe had formatted third-party articles and reviews to look like independent opinions without disclosing its connections to the reviewers, and the order bars that too.
That case is American and concerns one company. But it is a useful warning for any UK owner reading an accessiBe review or any overlay sales page: a claim that a widget alone makes a site compliant is the kind of claim a regulator has already challenged.
Why automated fixes fall short
The World Wide Web Consortium (W3C), which publishes WCAG, is direct about automated tools in its guidance on choosing evaluation tools. It says tools "can not determine accessibility, they can only assist in doing so", that some checks cannot be automated and need manual work, and that tools can produce false or misleading results. If a tool cannot reliably tell you whether a page is accessible, it cannot reliably fix that page either.
Consider what judgement is needed. Whether alt text describes an image usefully, whether a link's text makes sense out of context, whether an error message tells someone how to correct a form field: these need a person who understands the content.
Overlay vs real fixes: a side-by-side comparison
| Question | Overlay widget | Fixing the site |
|---|---|---|
| Where does the change happen? | A layer added on top of the page | In the templates, components and content |
| Does it fix keyboard and screen reader problems at source? | Not at source; any repair depends on the script working | Yes, the code itself is corrected |
| Can it judge content, such as alt text and link wording? | Limited; the W3C says human judgement is required | Yes, a person reviews and rewrites |
| Do new pages stay accessible? | Depends on the script handling each new problem | Yes, if templates and editor guidance are fixed |
| Can it support a compliance claim? | A regulator has challenged a vendor's compliance claims | Supported by an audit against WCAG |
None of this means every feature in a widget is useless. Some visitors may like a text-size control. The problem is relying on the widget instead of fixing the site.
What does UK law expect from a business website?
For private businesses, the main law is the Equality Act 2010. Section 29 says a service provider must not discriminate against a person requiring the service by not providing it, and section 29(7) applies the duty to make reasonable adjustments to service providers. If customers book, buy, enquire or get information through your website, treat it as part of the service you must make accessible.
WCAG is the W3C's set of web accessibility guidelines. Its current version is WCAG 2.2, first published in October 2023 and updated in December 2024, with success criteria at levels A, AA and AAA. We recommend working to level AA. Our guides to website accessibility and UK law and the WCAG checklist for business websites go into the detail.
What decides your own position is your situation: what the site does, who uses it and what is reasonable for a business of your size. If you have received a complaint or a legal letter, take advice from a solicitor rather than relying on a widget or a blog post.
What real accessibility fixes involve
Fixing a site is less mysterious than overlay marketing suggests. Most work falls into a handful of areas.
- Audit first. Test key pages and journeys against WCAG 2.2 AA with automated tools and manual checks: keyboard only, a screen reader, zoomed-in text and colour contrast.
- Fix the templates. Headers, menus, footers and page layouts appear on every page, so one fix there repairs every page that uses it. Good website navigation is a big part of this.
- Fix the components. Forms, buttons, sliders, pop-ups, tabs and accordions need proper labels, focus handling and keyboard support.
- Fix the content. Headings in order, meaningful link text, alt text that describes images, captions for video and readable PDFs or HTML alternatives.
- Check third-party code. Booking widgets, chat tools, cookie banners and plug-ins can each add barriers. Review them as you would any plug-in for security: is it maintained and does it do what you need?
- Train editors. Give the people who add content a short guide so new pages stay accessible.
- Retest. Check again after fixes and after major changes.
Where to start if budget is tight
Prioritise the journeys that matter most: the homepage, your main service or product pages, the contact form, the booking or checkout process. A barrier on the checkout can stop someone buying at all.
A five-minute keyboard test you can do yourself
Before paying for anything, try this on your own site. Put the mouse aside and press Tab repeatedly from the top of the homepage. Can you see where you are on the page at every step? Can you open the menu, reach every link and button, and fill in and send the contact form using only the keyboard? Do pop-ups let you close them and carry on? If you get stuck or lose track of where the focus is, a keyboard-only user will too. It is not a full audit, but it shows quickly whether there is real work to do.
Should you remove an overlay you already have?
Not necessarily straight away, but stop relying on it. Get an audit of the site with the widget switched off, so you see the real state of the code. Then fix the issues found. Once the site works well with assistive technology on its own, decide whether the widget still adds anything for your visitors. If it adds nothing, removing it is one less script to load and maintain.
Also look at what the vendor's contract and website say. If you were sold the product on a promise of compliance, ask the vendor what evidence supports that claim, in light of the FTC's order against accessiBe.
Frequently asked questions
Is accessiBe banned in the UK?
No. The FTC order is a US action against accessiBe's marketing. It required a $1 million payment and bars the company from claiming its automated products make any website WCAG-compliant without evidence. It does not stop anyone using the product. The point for UK owners is that a widget should not be treated as proof of compliance.
Can an accessibility plugin for WordPress fix my site?
A well-chosen plug-in can help with specific tasks while you edit content. That is useful. But no plug-in can rewrite a theme's menus, forms and layouts for you, or judge whether content makes sense. Treat plug-ins as tools that support real fixes, not replacements for them.
Do automated accessibility checkers find every problem?
No. The W3C states that evaluation tools cannot determine accessibility on their own, that some checks cannot be automated and that tools can produce false or misleading results. Automated checks are a good first pass for things like missing labels and contrast, but keyboard, screen reader and content checks need a person.
Which WCAG level should a small business aim for?
We recommend level AA of WCAG 2.2 as the working target for a business site. WCAG has three levels, A, AA and AAA. Because WCAG 2.2 is backwards compatible, meeting it also meets earlier versions. Meeting AA means meeting every level A criterion as well as the AA ones.
How long does it take to fix an inaccessible website?
It depends on the size of the site and how it was built. Fixing shared templates and components can resolve many issues across a site quickly, while content fixes depend on how many pages you have. An audit gives a list of issues ranked by impact, which is the basis for a realistic plan and quote.
Fix the site, not the symptoms
An overlay can look like a quick answer, but the dependable answer is a site whose code and content work for everyone. Our web development team can audit your site against WCAG 2.2 AA and fix the templates, components and content that cause problems. Start your project with a quote or contact us. You can read the FTC's announcement on accessiBe and the W3C's guidance on the limits of evaluation tools.
