Accessibility Overlays and Why People Object

What is being sold

A script you add to your site, usually a single line, and a monthly fee.

It typically produces a small icon that opens a panel of adjustments: larger text, higher contrast, a different typeface, sometimes a reading guide or a cursor change.

Some also claim to fix underlying problems automatically, adding image descriptions, labelling form fields, and correcting structure without anybody editing the site.

The offer is compelling: a genuine obligation, addressed in an afternoon, for a predictable subscription rather than a project.

Why it appeals

Worth stating fairly before the objections, because the businesses buying these are not being careless.

Accessibility work is unfamiliar, the standard is long, and the people who explain it often do so in a way that suggests you have already failed.

A small business owner facing that will reasonably prefer a product with a price and a checkout to a project with an unclear scope.

Understanding that is important, because the objections below are not about laziness. They are about whether the product does what it says.

The objections, specifically

These come primarily from disabled users and from accessibility practitioners rather than from competitors, which is the part worth noticing.

• They fix a minority of the issues that matter.
• They can interfere with the tools people already use.
• Automatic descriptions are frequently wrong or useless.
• The underlying code is unchanged, so the site is unchanged.
• The panel itself is sometimes hard to use.
• The claims are broader than the capability.

The second is the one most often overlooked and the most serious in practice.

People already have their own settings

The point that changes how you think about the whole category.

Somebody who needs larger text has set that in their operating system and browser, and it applies to every site they visit.

Somebody using a screen reader has configured it over years and knows it intimately.

A widget offering to change the text size is duplicating a control they already have, and a script that alters how a page is announced can conflict with software that was working correctly before it loaded.

That is why the objections are strongest from people who actually use assistive technology: the layer is not neutral, and when it is wrong they cannot switch it off.

Automatic descriptions are the clearest case

An image description has to convey what the image means in its context, which is a judgement about purpose rather than a description of contents.

Automated recognition can say there is a person standing near a building.

It cannot know that the image is there to show a completed roof repair, that the relevant detail is the flashing, or that the photograph is decorative and should be skipped entirely.

A wrong description is worse than none, because a missing one is obvious and a confident wrong one is not.

Writing forty descriptions yourself takes an afternoon and produces something correct.

A worked example

A retailer installed an overlay after a customer complaint and considered the matter closed.

Three months later the same customer wrote again, more directly, explaining that the widget had made things worse: it interfered with their screen reader's own navigation and the checkout still could not be completed without a mouse.

The underlying problems were unchanged. The form fields still had no labels, the checkout steps still could not be reached with a keyboard, and the contrast still failed.

They removed the widget and spent the equivalent of about eight months of the subscription on fixing the form, the checkout, and the contrast.

That took a developer three days.

The customer completed an order the following week and told them so, which is the only test that actually mattered.

The legal claim

Frequently the reason these are bought, and worth treating carefully.

Overlays are often marketed as providing protection from accessibility complaints or claims.

Whether any product reduces legal risk depends entirely on the jurisdiction, the obligations that apply to you, and the facts, and it is not something a general article can answer.

What can be said is that sites using overlays have continued to receive complaints and claims, and that a widget does not change whether somebody can actually complete a purchase.

This is a general description rather than legal advice. If you have a genuine obligation and are worried about it, that is a conversation with somebody qualified rather than a purchase.

Where a widget genuinely helps

The honest carve-out, because the category is not entirely without use.

Some panels offer things a browser does not easily provide: a reading guide, adjustable line spacing, or a simplified reading view, which some users with dyslexia or attention difficulties find helpful.

Those are preferences rather than accessibility fixes, and offering them is a reasonable addition to a site that is already built properly.

The distinction is what the widget is doing. Adding an optional preference on top of an accessible site is fine. Adding a layer that claims to make an inaccessible site accessible is the thing being objected to.

What the money buys instead

A monthly subscription, over a year, is usually enough to pay for the work that actually fixes the site.

Image descriptions across the site, written by somebody who knows what the images are for.

Form labels, contrast corrections, heading structure, and a visible focus outline, which is typically a day or two.

Testing the main journeys with a keyboard and a screen reader, and fixing what that finds.

The result is permanent, does not require a subscription, and does not sit between your visitors and your content.

The counter-case

There is a position on the other side that deserves acknowledging.

A site with serious problems and no budget at all is not improved by principled inaction, and a business that installs a widget has at least accepted there is a problem, which is more than most do.

Some of the criticism is also aimed at the marketing rather than at every product in the category, and a few of these tools have improved and are more modest about what they claim.

The reasonable position is that a widget is not a fix and may be a small comfort, and that the money is better spent on the five common failures, which are cheap, permanent, and address what people actually report.

If you have already bought one, the useful next step is not removing it in a hurry. It is testing your site with a keyboard to find out what the widget is not doing.

What to do

1. Tab through your own site and complete your own form.
2. List what actually fails, with or without a widget.
3. Fix the common failures in the underlying site.
4. Write image descriptions yourself.
5. Test with a screen reader on the key journeys.
6. Keep a preferences panel only as an addition.
7. Give people a way to contact you when it still fails.

Step one takes ten minutes and tells you whether anything you installed has changed the thing that matters.

The failures worth fixing first are covered in fixing the five most common failures.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.