Image generated with AI. Art direction: Grafica.
A small toolbar in the corner of a website, behind a round icon, is sold as the quick way to make a site accessible, and sometimes as the way to make it compliant. My position is simple: an accessibility widget does not make a site compliant. I built hospitality websites to the WCAG standard for years and carried out ADA audits. This is why, and what to do instead.
What a widget is
It is a script added to your pages. It loads after the page does and gives visitors a menu: larger text, higher contrast, paused animations. Some versions also try to repair the page as it loads, by guessing a description for a picture or a name for a button.
Why it cannot be compliance
The standard, the Web Content Accessibility Guidelines (WCAG), is about what the page itself does. Does the description of a photo say what the photo is there to tell you? Does every form field have a name? Can a keyboard reach every button, in a sensible order, with the focus visible? Does a video have captions? Those answers live in the page’s code and content.
A script can change how a page looks. It cannot know what your menu photo is meant to say, which of two buttons books the table, or what is said in your video. Those answers come from the people who made the page. A guess at them is still a guess, and a page that depends on a guess cannot be relied on to meet the standard.
There is a second problem. Many of the people a widget claims to serve already use their own tools, such as a screen reader, a magnifier, the browser’s zoom or the keyboard, set up the way they need them. A toolbar on one site often repeats what they already have.
Not only my view
More than a thousand people have signed the Overlay Fact Sheet, a public statement that says no overlay product «can cause a website to become fully compliant».
In April 2025 the US Federal Trade Commission approved a final order requiring one widget maker to pay $1 million. The FTC’s complaint alleged that the company’s claim, that its tool could make any website WCAG compliant, was false. The order bars the company from making such claims without evidence to support them (FTC press release, 22 April 2025).
How we fix things on our own sites
Neither grafica.group nor this blog loads a widget. When we scanned this blog’s front page and then tabbed through it, we found ten picture links with no name, four slider buttons pointing at an element that did not exist, and ten Tab presses lost on a copy of the header placed off the screen. We wrote about those checks. Each fix went into the site’s code, so it works for every visitor, with every tool, and nothing has to load first for it to work.
If you already have a widget
- Do not count it as your accessibility work, and do not describe your site as compliant because of it.
- Go through your main pages with the keyboard alone, with the widget on and off. Every press should land on something you can see, and the widget should not get in the way.
- Fix the page itself: a description for each picture that carries meaning, a name for each field and button, headings in order, enough contrast, captions on video.
- Publish an accessibility statement with a way to reach a person who can help.
Whether to keep the widget is your decision. What it cannot be is the plan. If you have received a letter about your site, talk to a lawyer; this post is not legal advice.
Accessibility is built into a page from its design, checked by a person, and checked again after every change. If you want your site reviewed that way, talk to us.
Gráfica built this survey as a WordPress plugin, and builds plugins like it for clients. Tell us what your site needs
