Myths

Accessibility widgets: what they change on a page, and what an audit counts

7 min read
Mikhail ShaymardanovWeb Quality and Accessibility Expert

An online store owner who installs an accessibility widget adds display settings to the pages without fixing their code. The widget, a small icon that opens a bar to enlarge text or raise contrast, runs on a script from the vendor. Its changes vanish with that script, and the flaws stay in the code of pages that the ADA and the European Accessibility Act cover.

One product page, tested twice


#What an accessibility widget or overlay does on a website?

An accessibility overlay, or widget, is a third-party script that changes how a site looks and behaves in the visitor's browser without changing the site's code. It usually has two layers: a bar of display settings (text size, contrast, spacing) that each visitor opens and sets for themselves, and sometimes an “automatic fix” layer that guesses missing image descriptions or labels while the page loads. Neither changes the HTML the server sends, so the flaws stay in the code. On WordPress, it installs like any other plugin, hence the name “accessibility plugin.” The settings are meant for visitors with low vision, who struggle with the font, size or colors the site chose.

On the product page for a skein of yarn at Willow Spinnery, our demo store, the “Display” button opens four settings. Behind it, the vendor's script, a small program loaded on every visit, changes the display in the browser. Specialists and the European Commission call this an “overlay”: a layer added on top of a site to improve its accessibility.

Screenshot: the Willow Spinnery product page “Merino skein, Lichen colorway” at $18.50, under a green banner “Free hat pattern with 4 skeins”; at the bottom left, an open “Display settings” bar with four switches off, above a “Display” button.Marker 1. The widget's “Display” button, at the bottom left of the page. Marker 2. The open bar and its four display settings, all off.
The “Display” buttonmarker 1 opens a bar of four settingsmarker 2 over the skein's product page: none of them is on yet.

The page's code stays the same: we compared it line by line, widget closed and then open. According to the German authorities that monitor public-sector websites, these changes last only as long as the tool stays on the site. The “automatic fix” script that some vendors add also works only during the visit.

The W3C, which writes the web's standards, points out that a widget changes only the site it sits on. People who need larger or higher-contrast text have usually already adjusted their browser or operating system for every site, the same German authorities note. In most browsers, zoom works by holding Ctrl, or ⌘ on a Mac, and pressing the plus key.


#What an accessibility test shows, with the widget closed and then open?

Closed or open, the widget leaves two flaws in the demo page's code: a button that's too pale and a banner made of an image of text. High contrast mode hides only the first one, and only for the visitor who turns it on.

#What a visitor with low vision sees with the widget open?

With the widget closed, the “Add to cart” button is white text on sage green. We pasted its two colors into our free contrast checker. It puts their contrast ratio, the gap in lightness between the letters and the color behind them, at 3.14:1. At 16 px, the button's text needs 4.5:1, and 3:1 is enough only from 24 px, or 18.5 px bold. The checker flags the failure and suggests three nearby colors that pass.

Screenshot: the Willow Spinnery product page “Merino skein, Lichen colorway” at $18.50, under a green banner “Free hat pattern with 4 skeins”; on the right, the “Add to cart” button in white on pale green, and at the bottom left, a “Display” button.Marker 1. The “Add to cart” button, white on sage green. Marker 2. The promo banner, an image of text.
With the widget closed, the “Add to cart” buttonmarker 1 reaches only 3.14:1, below the 4.5:1 that 16 px text needs; the bannermarker 2 is an image of text.

Let's open the widget the way a visitor with low vision would. “High contrast” turns the page black on white and the button white on black, at 21:1. With “Larger text,” the letters grow from 16 to 24 px.

One line of text doesn't change: the banner “Free hat pattern with 4 skeins,” the most eye-catching text on the page. It's an image of text, letters stored as pixels, and the widget acts only on real text. Enlarged, an image like this pixelates, and its colors are hard to change. At 200% zoom on our screen, the banner's letters go blurry while the text around them stays sharp.

Screenshot: the Willow Spinnery product page in black on white, its text enlarged, the “Add to cart” button in white on black; the green banner keeps its size and colors, and the “Display settings” bar shows “Larger text” and “High contrast” switched on.Marker 1. The “Add to cart” button, now white on black. Marker 2. The promo banner, unchanged.
With the widget open, the “Add to cart” buttonmarker 1 reaches 21:1 and the text grows from 16 to 24 px; the bannermarker 2 keeps its size and colors.

#Does the widget's high contrast mode count in an audit?

Yes, under conditions that the auditor, the person who checks the site, verifies on the widget itself. WCAG, the international accessibility guidelines, accept text below 4.5:1 when a control turns on a higher-contrast version of the page. The W3C describes this route in technique G174, one example of how to meet the rule, and sets three conditions:

  • the control that switches it on has enough contrast itself: 14.26:1 for the demo's “Display” button;
  • the new version keeps all the same information and functionality: in high contrast, the page keeps its text, its price and its eleven links and buttons;
  • the new version meets, on its own, all the other rules at the level the site aims for.

The demo fails on that last condition. The high contrast page serves as that conforming alternate version, and the banner is still on it. It's an image of text that carries information (the promotion) and that styled real text could replace. No setting in the widget makes that swap. The auditor therefore flags the banner under WCAG success criterion 1.4.5, Images of Text, widget open or closed. The page fails to conform.

#Why a widget can block an audit verdict in Germany?

At the labs that use BIK BITV-Test, a private German audit procedure, a widget on the page is enough to block any verdict. For now, these labs don't say whether such a site conforms to WCAG or the European standard EN 301 549. The site gets no published result and can't display the labs' seal.

Their procedure gives two reasons. A widget can interfere with assistive technologies such as a screen reader, which reads the page aloud or in braille, even when nobody has touched the widget. Each visitor's settings also produce a different display, and none of them is marked as the version that conforms. At these labs, a widget bought for compliance makes compliance impossible to establish.

How to check the contrast ratio of text in Chrome DevTools

#What to ask the widget vendor, and what to fix for ADA and EAA compliance?

Before signing or renewing, get the vendor's guarantees in writing, then put the budget into fixing the pages.

#What to ask the vendor, in writing?

Two vendors answer whether a widget makes a site compliant. On the page for its toolbar, AudioEye writes that a toolbar supports compliance by giving visitors control over their experience. No toolbar or widget, it adds, “can make a website fully compliant on its own.” True accessibility, it says, takes automated and manual testing, expert review and ongoing fixes. EqualWeb's widget page says the same about ADA compliance. We reread both pages on November 6, 2026.

In the US, the compliance promise of one vendor, accessiBe, ended up before the FTC, the federal agency that protects consumers. The agency's order, approved in April 2025, bars the company from claiming, without evidence, that its automated tools can make any website WCAG compliant or keep it compliant over time. The company agreed to pay $1 million, without admitting or denying the allegations.

Get the vendor's compliance claim and supporting audit in writing.

#What to fix in the pages?

The law asks for the pages themselves to be accessible. In the US, the Justice Department's position is that the Americans with Disabilities Act (ADA) applies to everything a business open to the public offers, online included. No regulation spells out technical rules for business websites, and the department's guidance points to WCAG. In the EU, the European Accessibility Act covers what an online store provides to consumers after June 28, 2025. A business is covered once it employs at least ten people, or once its annual turnover and its balance sheet total both exceed €2 million.

That's where the budget belongs: finding the page's non-conformities, where it fails the standard, then fixing them in its code. An audit measures its conformance. In our three-year cost scenarios, a widget subscription comes on top of the cost of those fixes.

On the demo page, we made two fixes in the code. The “Add to cart” button, at 3.14:1, gets the darker green our contrast checker suggested, which reaches 4.55:1. The promo banner, an image of text, becomes real styled text with the same design.

Avoid

Screenshot: the top of the product page “Merino skein, Lichen colorway,” with the green banner “Free hat pattern with 4 skeins” and the “Add to cart” button in white on pale green.Marker 1. The “Add to cart” button, white on sage green. Marker 2. The banner, an image of text.

Correct

Screenshot: the top of the product page “Merino skein, Lichen colorway,” with the green banner in the same design and the “Add to cart” button in white on a darker green.Marker 1. The “Add to cart” button, white on the darker green. Marker 2. The banner, rebuilt as real text.
After the fix, the “Add to cart” buttonmarker 1 goes from 3.14:1 to 4.55:1 on the green #537F6B, and the bannermarker 2 keeps its design with real letters that grow with the text.

Both flaws are gone for every visitor, widget open or closed, even after the vendor's script stops loading. The banner follows the display settings too: with “Larger text,” its letters grow from 18 to 27 px, like the rest of the page. On these two points, the verdict now depends only on the store's own code.

Website accessibility audit: cost, quotes and how to choose an auditor

Once the widget decision is made, each page gets fixed the way the skein's page was, in its code. Includdy lists a page's non-conformities, then suggests a code fix for each one, to be checked before it goes into the site's code.


Share this article

Frequently asked questions

They can be. The European Disability Forum and the International Association of Accessibility Professionals said so in a joint statement on May 17, 2023. An overlay, they wrote, can interfere with a person's assistive technology and override the settings that person chose.

The German authorities that monitor public-sector websites reach the same conclusion: adding an overlay often makes a site harder to use for people who rely on assistive technology, such as a screen reader.

The Commission calls them an inappropriate solution when the site itself falls short of the standard, and the Justice Department advises using them with care. The European Commission writes that overlays, or any tools that don't make the website itself meet the detailed criteria of the European standard EN 301 549, are not an appropriate solution. It is best, it adds, to fix accessibility issues at their source.

In its guidance on web accessibility and the ADA, the Justice Department calls automated checkers and overlays that find or fix problems helpful tools that need to be used carefully. A clean report, it warns, does not necessarily mean everything is accessible.

No. In their joint statement of May 17, 2023, the European Disability Forum and the International Association of Accessibility Professionals write that no technology, artificial intelligence included, can so far instantly fix an inaccessible website.

Overlays that try to repair problems automatically while the site is in use aren't always reliable, they add, and they can interfere with assistive technology.