Why accessibility overlays do not make your site compliant
TL;DR
Difficulty: Beginner
An accessibility overlay is a script that edits your page in the visitor's browser after it arrives. It can change fonts and colours and sometimes guess a missing label, but it cannot know what your images mean, add the keyboard code your widgets lack, or reach your payment page and PDFs.
- The European Disability Forum, the European Commission and over a thousand accessibility practitioners say overlays do not make a site accessible or compliant.
- The US Federal Trade Commission fined one overlay vendor $1 million in 2025 over its compliance claims.
- Under S.I. No. 636 of 2023 and the Equal Status Acts the duty stays with the business that runs the site. Fix barriers in the source, test with real people, publish an honest statement.
A friendly email offers to make your website accessible with one line of code and a monthly fee. It is a tempting offer, and it deserves an honest answer. Here is what an overlay actually does, what the evidence says about it, and a full test of an invented Galway bookshop with and without one.
The offer in your inbox
Sooner or later the email arrives. A friendly company offers to make your website accessible with one line of code, for a monthly fee. Paste the snippet, a small icon appears in the corner of every page, and you are compliant by tomorrow morning. If you run a shop without a developer on call, that is tempting. So why not just buy it?
This article is the honest answer, and the first chapter of a series on one idea: accessibility is built, not bought. An overlay sits on top of a site and cannot change what the site is made of, and the duty to make the site usable stays with the business that runs it. Below are the evidence, the code, and a full test of an invented bookshop with and without an overlay.
If WCAG is new to you, read WCAG 2.1 AA explained first. It covers what the standard asks and how it is tested, so I do not repeat it here.
Example: an offer lands in Sinéad's inbox
Claddagh Books is an invented independent bookshop in Galway with an online shop at claddaghbooks.example. Sinéad owns it. Twelve people work there across the shop floor, the café and the events. Ade is the developer who looks after the website a few days a month.
On a Monday morning Sinéad receives an offer. For €45 a month (an invented figure for this example), a script will "scan and repair" the site every day, add an accessibility toolbar, and "ensure compliance with WCAG and the Accessibility Act". She forwards it to Ade with one line: "Is this the easy way out?"
Ade suggests a test instead of an answer: check the site for barriers, switch the overlay on in a trial, test again, and write down what changed. The rest of this article follows that test.
What an overlay actually is
An accessibility overlay is a piece of third party code, almost always JavaScript, that you add to your website so that it runs on top of every page. It loads after your own page has arrived in the visitor's browser, inspects it, and changes it there and then. Your own files on your server are not touched.
The Overlay Fact Sheet, written and signed by accessibility practitioners and disabled users, traces three generations of these products1. The first add ons date back to the late 1990s. Later products added a control panel, the familiar toolbar with buttons for larger text, higher contrast or a different font. The newest go further and "aim to fix any problems in the site's code"1, some of them marketed as artificial intelligence (AI).
So the word covers two different jobs:
- A preferences toolbar, which lets a visitor change how the page looks.
- An automated repair script, which tries to guess what is wrong with the page and rewrite it on the fly.
Most products sold today do both, and the marketing usually promises the result of the second: an accessible, compliant site.
Example: what happens when a Claddagh page loads with an overlay
Here is the sequence for one visit to a product page, written out in full.
- A customer opens the page for a novel. The browser asks claddaghbooks.example for the page.
- The server sends back the HTML that Ade's templates produce. This is the real page, the same for everyone.
- The browser starts to build the page and finds one extra line near the end, the snippet Sinéad was asked to paste:
<script src="https://widget.overlay.example/v1/loader.js" async></script>
- The browser downloads that script from the vendor's server and runs it. The
asyncattribute means it does not hold up the page, so for a moment the visitor sees the original page. - The script reads the page, applies its rules and changes the page in the browser's memory: it adds attributes, injects a toolbar button and may change colours.
- If the visitor leaves and comes back, steps 1 to 5 happen again. The page on the server is still the original.
That last step is the whole story in miniature. Everything the overlay does is a guess applied after the fact, on each visit, to a page that is still built the same way underneath.
What an overlay can change, and what it cannot
A web page is built from HTML, the markup that says "this is a heading", "this is a button", "this is a field for your email address". Assistive technology reads that markup. A screen reader, the software a blind person uses to hear or feel the page in Braille, does not look at the design. It reads what the HTML says each element is, what it is called and what state it is in. WCAG puts it as a success criterion: every interface component must expose its name, role and value (4.1.2), and structure that is shown visually must also be in the markup (1.3.1)2.
An overlay can only add to that markup from the outside. A bigger font or a colour scheme is harmless. The meaning is where it runs out. The Fact Sheet lists the limits plainly: automated text alternatives for images are "not reliable", automated repair of keyboard access is "not reliable", content in PDFs, canvas, SVG and media files is not repaired at all, and "full compliance cannot be achieved with an overlay"1.
The reason is not lazy engineering. The information is simply not there to be found:
- A script can see that an image has no description. It cannot know the photo shows the signed first edition.
- A script can see a clickable box. It cannot know which book the box adds to the basket.
- A script cannot repair a checkout step that only works with a mouse, because that logic lives in your own JavaScript and on your server.
- A payment form inside your provider's frame, or a PDF programme for an author event, is out of its reach.
There is a second problem. ARIA, the set of attributes that tell assistive technology what an element is, works like a promise. The W3C's ARIA Authoring Practices Guide says it bluntly: "No ARIA is better than Bad ARIA". It also explains that, unlike real HTML controls, an ARIA role does not make the browser add any keyboard behaviour at all3. When a script stamps role="button" on a box, it promises a screen reader user a button. If the box then does nothing when they press Enter, the page has become more confusing than before.
Example: one product card, three versions
Here is a product card from Claddagh Books as Ade's old template produced it. The novel, Salt on the Corrib, is invented.
<!-- Before: what the template sends to the browser -->
<div class="card">
<img src="/covers/salt-on-the-corrib.jpg">
<div class="title">Salt on the Corrib</div>
<div class="btn" onclick="addToBasket(4211)">Add</div>
</div>
Three barriers sit in those five lines. The image has no alt attribute, so a screen reader may read out the file name. The title is a plain div, so it is not a heading and cannot be jumped to. The "Add" control is a div with a click handler, so it cannot be reached with the Tab key and a screen reader does not announce it as a button (2.1.1 and 4.1.2)2.
Here is roughly what an automated repair script might turn it into in the browser. This is an illustration of the kind of patch the Fact Sheet describes, not the output of any named product.
<!-- After the overlay: changed in the browser, on every visit -->
<div class="card">
<img src="/covers/salt-on-the-corrib.jpg" alt="book">
<div class="title">Salt on the Corrib</div>
<div class="btn" onclick="addToBasket(4211)"
role="button" tabindex="0" aria-label="Add">Add</div>
</div>
An automated checker is now happier. In practice:
alt="book"tells a blind customer nothing they did not already know. On a page of 24 books, they hear "book" 24 times.tabindex="0"makes the box reachable with the Tab key, androle="button"makes a screen reader call it a button. But the box only listens for a mouse click. Pressing Enter or Space does nothing, because nobody wrote the keyboard code.aria-label="Add"is the same on all 24 cards. "Add, button" 24 times, with no clue which book.
Here is the version Ade writes in the template itself, so every visitor gets it from the server.
<!-- Fixed in the source: the template now sends this -->
<article class="card">
<img src="/covers/salt-on-the-corrib.jpg"
alt="Cover of Salt on the Corrib: a currach on grey water below a stone bridge at dusk">
<h3>Salt on the Corrib</h3>
<form action="/basket/items" method="post">
<input type="hidden" name="book_id" value="4211">
<button type="submit">
Add <span class="visually-hidden">Salt on the Corrib</span> to basket
</button>
</form>
</article>
Line by line, for anyone new to HTML:
alt="..."describes what the cover shows, written by a person who knows the book.h3makes the title a real heading, so a screen reader user can jump from book to book.formwithmethod="post"means adding to the basket works even without JavaScript.button type="submit"is a native button. The browser gives it keyboard focus, Enter and Space, and the button role for free.- The
visually-hiddenspan is hidden on screen with CSS but still read out, so the button is heard as "Add Salt on the Corrib to basket".
Nothing here is clever. It is ordinary HTML, and it needs no script to rescue it on every page view.
What the evidence says
The Overlay Fact Sheet has been signed by well over a thousand people, among them contributors to WCAG, ARIA and HTML, accessibility consultants and engineers, lawyers who represent disabled people, and many disabled users1. Its sponsors commit never to recommend an overlay that markets automated compliance, and say overlays "cannot eliminate legal risk"1.
In May 2023 the European Disability Forum (EDF), which represents disabled people across Europe, and the International Association of Accessibility Professionals (IAAP) published a joint statement. It says overlays "do not make the website accessible or compliant with European accessibility legislation" and do not "constitute an acceptable alternative or a substitute for fixing the website itself"4. It also warns that an overlay "can interfere with the user's assistive technology and override user settings", and that some overlays detect assistive technology on the visitor's device, which raises a privacy issue because "information about disability is sensitive personal data"4.
The European Commission says the same in its guidance on web accessibility. The legal requirements rest on the harmonised standard EN 301 549, and overlays, "or any other tools which do not ensure the website itself meets the detailed criteria of the standard", are "not an appropriate solution". The Commission's advice is short: "It is best to fix accessibility issues at their source"5.
Practitioners agree in numbers. In WebAIM's January 2021 survey of web accessibility practitioners, about two thirds of respondents rated overlays, plugins and widgets that automate accessibility changes as not at all or not very effective. Among respondents with disabilities the figure was 72%6.
Then there is a regulator acting on the claims themselves. In January 2025 the United States Federal Trade Commission (FTC) announced a proposed order against accessiBe, a company that sells an overlay called accessWidget, which it had said can make any website compliant with WCAG. The FTC alleged that accessWidget did not in fact make all its users' websites compliant with WCAG, that the claims were "false, misleading, or unsubstantiated", and that the company had formatted third party articles and reviews to look like independent opinions7. The final order, approved on 22 April 2025, requires accessiBe to pay $1 million and bars it from claiming that its automated products can make any website WCAG compliant without evidence to back it up8. That is a decision about one company's advertising, not a ruling on every overlay, but it shows how a regulator reads the promise "install this and you are compliant".
Finally, overlays do not keep the lawyers away. UsableNet, a company that tracks digital accessibility lawsuits in the United States, reported that in 2024 more than 1,000 businesses were sued despite having an accessibility widget on their website, more than 25% of the cases it counted9. That is American law, and UsableNet sells accessibility services itself, so read it as a signal rather than a forecast for Ireland: the widget did not stop the claim.
Example: Sinéad reads the sales page again
With those sources open, Sinéad goes back to the offer and checks each promise against them.
- "Scans and repairs your site every day." The Fact Sheet says automated repair of images and keyboard access is not reliable1. So, at best, part of it.
- "Ensures WCAG compliance." The FTC found exactly this kind of claim unsubstantiated for one well known product7, and the European Commission says such tools are not an appropriate solution5. So, no.
- "Protects you from legal action." More than 1,000 US businesses with a widget were sued in a single year9. So, no.
- "Adds an accessibility toolbar for your visitors." True, and the next sections look at what that is worth.
One promise out of four holds, and Sinéad has not spent a cent finding out.
Why the duty stays with you
Here is the part that the one line of code cannot change. In every market I write for, the law places the duty on whoever provides the service, not on whoever sold them a script.
In Ireland, the European Accessibility Act is transposed by S.I. No. 636 of 2023, the European Union (Accessibility Requirements of Products and Services) Regulations 2023. Regulation 14 puts it plainly: "A service provider shall ensure that a service provided by the service provider is designed and provided in accordance with the applicable accessibility requirements"10. That follows the Directive's own wording, that service providers shall design and provide their services in accordance with its accessibility requirements11. Services provided by a microenterprise, fewer than 10 people and a turnover or balance sheet of no more than €2 million, are exempt from those requirements under regulation 5(4)10. Claddagh Books, with 12 people, is not a microenterprise.
The Equal Status Acts add a second duty that has applied for years and has no size threshold. A provider of a service must not discriminate in providing it (section 5), and discrimination includes failing "to do all that is reasonable to accommodate the needs of a person with a disability", where that costs no more than a nominal amount (section 4)1213.
The accessibility requirements are measured on the website itself. The European Commission explains that the EU's legal requirements rely on the technical criteria of the harmonised European standard EN 301 5495, whose chapter on the web follows WCAG 2.1 at Level AA14. A script that changes the page after it arrives does not change what you built. Who exactly is in scope, from when, and who enforces it is covered in the accessibility law article.
Example: who answers when a customer complains
Suppose, before any fixes, a Claddagh customer called Aoife, who is blind and shops on her iPhone with VoiceOver, cannot add a signed copy to her basket. She emails Sinéad to say so.
- The email goes to Sinéad, because Claddagh Books provided the service.
- The duty under regulation 14 and the Equal Status Acts sits with Claddagh Books, the service provider1012.
- The overlay vendor's terms are between Sinéad and the vendor. They do not move the duty.
- What helps Sinéad is what she can show: that the barrier was found, fixed in the site and tested, and that she offered Aoife another way to order in the meantime.
The duty never left the shop. The only question is whether the shop did the work, and fair play to the ones that do.
Preferences built into a good site are a different thing
There is a fair point inside the toolbar idea. Some people want larger text, more contrast or less movement. The question is where that preference should live.
Most of it already lives on the visitor's own device. The W3C notes that people may need to change the size, spacing, font, colour and other properties of text, and that applications "should use the operating system and web browser text settings"15. Every major browser zooms. Every major operating system has settings for larger text, higher contrast and reduced motion, and a website can listen for them. The prefers-reduced-motion media feature, for example, lets a site detect that the visitor has switched on a setting on their device to reduce motion that is not essential16. People who use assistive technology every day have usually set all of this up already, which is why the Fact Sheet calls toolbar features at best "redundant functionality with what the user already has"1.
WCAG asks the site to cooperate with those settings. Text must resize up to 200% without loss of content or function (1.4.4), and the W3C's Understanding document says a site can meet that by making sure its content does not get in the way of the browser's own zoom172.
A site can also offer its own preference controls: a text size switch, a high contrast theme, a reduce motion toggle. That can be a genuine comfort, on one condition: it sits on top of a site already built accessibly, and it is never presented as the thing that makes the site accessible. The accessibility is in the markup underneath.
My own website works this way. It has an accessibility panel built into the site's own code, with text size, high contrast and reduce motion. It is a set of user preferences inside a site that is built accessibly, not a third party overlay, and it does not claim to fix anything. Turn it off, and the site underneath is the same site, with the same headings, labels and keyboard paths. Every chart on the site has a text description and works in light and dark mode, with the panel on or off.
Example: Claddagh's own text size and motion settings
Ade adds two small things to the Claddagh stylesheet so the site honours what customers have already set on their own devices.
/* Text sizes in rem follow the browser's own font size setting */
html { font-size: 100%; }
body { font-size: 1rem; line-height: 1.6; }
h1 { font-size: 2rem; }
/* Respect the visitor's reduce motion setting */
@media (prefers-reduced-motion: reduce) {
*, *::before, *::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
scroll-behavior: auto !important;
}
}
What each part does:
remis a unit relative to the browser's base font size. If a customer has told their browser to use larger text, every size on the page grows with it. Sizes fixed in pixels would ignore that choice.@media (prefers-reduced-motion: reduce)only applies when the visitor has switched on reduce motion in their operating system16. Inside it, animations and transitions finish almost instantly, so the homepage carousel no longer slides and nothing swoops in on scroll.
Bríd, a regular customer with low vision, already has her laptop set to larger text and zooms to 200% on top. The site now simply follows her settings, with nothing to find or switch on.
The test: Claddagh Books with and without the overlay
Now the test Ade promised Sinéad. It is an invented example with invented numbers, written to show the method, not a review of any real product.
Ade tests four journeys: search for a book, open a product page, add it to the basket, and check out as a guest. He uses four methods for each, the mix described in WCAG 2.1 AA explained:
- an automated checker in the browser,
- the keyboard alone, mouse unplugged,
- VoiceOver on a Mac and on an iPhone,
- browser zoom at 200% and a narrow window of 320 CSS pixels, to check that the page reflows into one column (1.4.10)2.
He keeps four regular customers in mind: Aoife, who uses a screen reader, Declan, who navigates by keyboard since a stroke, Bríd, who zooms to 200%, and Ciarán, who has dyslexia.
Example: the first pass, without the overlay
Ade finds 12 barriers, each with the WCAG criterion it fails and the customer it stops.
- Product images with no
alttext (1.1.1). Aoife hears file names. - "Add" controls built from
divelements (2.1.1, 4.1.2). Declan cannot reach them, Aoife does not hear a button. - Product titles that are not headings (1.3.1). Aoife cannot jump between books.
- The search field has a placeholder but no label (1.3.1, 3.3.2). Aoife hears "edit text" and nothing else.
- No visible focus outline (2.4.7). Declan cannot see where he is.
- The "quick view" pop up traps keyboard focus (2.1.2). Declan gets stuck inside it.
- The basket count updates without being announced (4.1.3). Aoife does not know the book was added.
- The delivery options are styled boxes, not real radio buttons (1.3.1, 4.1.2). Declan and Aoife cannot choose one.
- Checkout errors are shown only in red (1.4.1, 3.3.1). Aoife hears nothing.
- Grey text on the cream background is below 4.5:1 contrast (1.4.3). Bríd struggles to read it.
- At 320 pixels the product grid keeps three columns and scrolls sideways (1.4.10). Bríd loses her place.
- The events programme is a scanned PDF. Aoife's screen reader finds no text in it.
The automated checker found five of these (1, 4, 10, and parts of 5 and 9). The other seven only showed up with a keyboard, a screen reader or zoom, which matches the Government Digital Service's 2017 test, where the best automated tool found only about 41% of 143 known barriers18.
Example: the second pass, with the overlay switched on
Ade turns on the trial and repeats every step.
- Barrier 1, images: the overlay added
alttext. Two covers got the book title, which helped. The rest got "book" or "image", which did not. - Barrier 2, the "Add" controls: they got
role="button"andtabindex="0". Declan can now reach them, but Enter does nothing, so he is promised a button that does not work. - Barrier 4, search: the overlay copied the placeholder into an
aria-label. Aoife now hears "Search books, edit text". Genuinely fixed, while the script runs. - Barrier 5, focus: the toolbar has a "highlight focus" option, but Declan has to find it first, and the toolbar button comes last in the tab order.
- Barrier 10, contrast: "high contrast" mode fixes the grey text for anyone who turns it on. The default page is unchanged.
The other seven barriers, the focus trap, the silent basket, the delivery options, the red only errors, the reflow, the scanned PDF and the title headings, were exactly as before. Two new problems appeared: when Aoife's VoiceOver was running, the overlay announced its own instructions on every page load, and the toolbar button covered the "Checkout" link at 200% zoom.
Example: the third pass, fixed in the source
Over three weeks Ade fixes all 12 barriers in the templates, the stylesheet and the content: real alt text written by Sinéad's staff, native buttons and radio buttons, headings, a search label, a visible focus style, a dialog that closes with Escape, an announced basket count, errors in text, a darker grey, a reflowing grid, and the events programme as an HTML page. The same four methods then pass all 12, for every visitor, with no script.
The chart sums up the three passes. These are the invented numbers from this example.
The overlay changed something in five places, truly fixed two, and broke two others. The source fixes cost Ade's time once, and then they are simply part of the site.
Where a barrier gets fixed
Every barrier you find, from a test, a customer email or an audit, raises the same question: where do I fix it? The answer is almost always "where it lives".
Three places cover nearly everything:
- Your templates and code: HTML structure, buttons, forms, focus, CSS. This is where most barriers live, and where a fix helps every page built from that template.
- Your content: image descriptions, headings in articles, link text, PDFs, videos. These are fixed by whoever writes them, with a little guidance.
- Your suppliers: the payment page, a chat widget, an embedded map, a booking tool. You cannot edit their code, but you choose them, and you can ask for their accessibility information or pick another.
Example: one barrier through the flow
Ciarán, the customer with dyslexia, writes to say the returns page is one long block of justified text in capitals and he gives up halfway. Sinéad runs it through the flow.
- A customer found a barrier. Start.
- Patch it with an overlay? The toolbar has a "dyslexia friendly font" button, but Ciarán would have to find it, and the text would still be one long block. No.
- Is it in code or content Claddagh controls? Yes, the returns page is Sinéad's own text, and the capitals and justification come from Ade's stylesheet.
- Fix it in the source: Sinéad splits the text into short sections with headings, and Ade switches the page to left aligned, sentence case text.
- Test again: Ade checks it at 200% zoom and with VoiceOver, which now reads the headings as headings.
- Does it pass for real people? Sinéad sends the new page to Ciarán, who says it reads well. Yes.
- Record it: the fix goes into the list of resolved issues in the shop's accessibility statement.
Seven steps, no subscription, and a permanent fix.
What to do instead of buying an overlay
Take this order of work. The rest of this series fills it in.
- Find out where you stand with an automated checker and a manual pass. See testing accessibility.
- Fix the critical path first: search, product page, basket and checkout. See an accessible checkout.
- Fix templates before pages. One fix to the product card template fixes every product.
- Fix the common building blocks: forms, keyboard and focus, and images, video, colour and motion.
- Honour the visitor's own settings, as in the CSS example above.
- Test with disabled people, not only with tools. The European Commission says it plainly: to ensure that websites are genuinely accessible, "always involve persons with disabilities in testing"5.
- Publish an honest accessibility statement. The W3C recommends at least a commitment to accessibility, the standard applied, and a way to report problems19. See writing an honest accessibility statement.
- Keep it in the build, with automated checks in your tests, so a fixed barrier does not come back with the next redesign.
Example: Sinéad's plan for the next quarter
Sinéad replies to the vendor with a polite no and writes a plan with Ade instead. The figures are invented for this example.
- Weeks 1 to 3: Ade fixes the 12 barriers from the test, starting with the four on the checkout. Sinéad's staff write
alttext for the 40 bestsellers first, then for new titles as they are listed. - Week 4: Ade adds an automated accessibility check to the shop's test suite, so the build fails if a product card loses its label.
- Week 5: two paid sessions with customers who use a screen reader and keyboard navigation, arranged through a local disability organisation. They find one more barrier, a newsletter sign up box that steals focus. Ade fixes it the same week.
- Week 6: Sinéad publishes an accessibility statement that says the site is built to WCAG 2.1 AA, lists the one known issue with the date it will be fixed, and gives a phone number and an email address for anyone who needs help.
The €45 a month she did not spend comes to €540 a year. It does not pay for Ade's three weeks, and it was never going to. The difference is that this money buys a site that works, not a monthly subscription to a guess.
How I build and test to this
I build shops on Solidus and SaaS platforms on Ruby on Rails, and I build them to WCAG 2.1 AA from the first commit. That means native HTML elements wherever possible, real headings and landmarks, a label tied to every form field, a colour palette chosen once to clear the AA contrast ratios, a visible focus style kept rather than removed, and errors named in text.
Automated checks run in the test suite on every build. I run keyboard and screen reader passes by hand on the key journeys, and zoom and reflow checks at 200% and 320 pixels. Where it is warranted, I arrange sessions with people who use assistive technology, and I keep the record of what was tested and fixed, because that is what an independent audit builds on. The honest wording for the result is "built to WCAG 2.1 AA". I never say "guaranteed compliant", and I never sell a badge.
Conclusion: build it in, then keep it in
An overlay is a script that edits your page after it has left your server. It can change fonts and colours, and sometimes it can guess a missing label. It cannot know what your images mean, it cannot write the keyboard code your widgets never had, it cannot reach your payment page or your PDFs, and it can get in the way of the assistive technology your customers already use. The accessibility profession, the European Disability Forum, the European Commission and, in one case, the Federal Trade Commission have all said as much.
The duty sits with the business that runs the site, and so does the fix. Find the barriers, fix them in the templates and the content, test with the people who rely on it, and say honestly where you stand. That is how a site becomes usable by everyone, and it stays that way without a monthly fee for a guess.