What an accessibility overlay can and cannot do

What they actually do

An overlay loads after your page and offers a panel of preferences. Larger text, wider spacing, a high contrast palette, a reading guide, sometimes a cursor change.

Some also attempt automatic repairs. Guessing at missing image descriptions, adding labels where none exist, adjusting contrast on the fly.

The preference panel part works, and some readers like it. The automatic repair part is where the difficulty starts.

It is worth separating the two halves cleanly, because one works and the other is where the argument is. A preference panel is a real feature. Automatic repair is a claim about code the script did not write.

What they cannot reach

An overlay runs in the visitor's browser, after your page has loaded. It cannot change how your page was built, only how it appears once it arrives.

So a menu that only opens on hover still traps a keyboard reader. A popup with no reachable close button still strands them. A form field with no real label still leaves the software guessing.

And a guessed image description is a sentence generated by a machine looking at a picture. It may be plausible and wrong, which is worse than nothing for a reader who has no way to check.

• A menu that only opens on hover
• A popup with no reachable close control
• A form field with no real label
• Heading levels that skip, or a page with no headings at all
• Whether an image description is true
• A keyboard trap anywhere in your own code

The part many users dislike

People who rely on assistive technology have usually configured it carefully. Their own software already handles magnification, contrast and reading preferences across every site they visit.

An overlay that changes those settings for them, or that announces itself loudly on arrival, can conflict with the setup they depend on.

Surveys of screen reader users have consistently found low enthusiasm. That is worth knowing before buying one on their behalf.

The objection is practical rather than ideological. Somebody who has spent years configuring their own magnification, contrast and speech settings does not want a website overriding them on arrival.

Why regulators took an interest

The issue was never that the tool exists. It was what was claimed for it. Several vendors marketed a single script as making a site meet the accessibility standard.

In a well publicized action, the Federal Trade Commission reached an order with one such vendor over claims that its product could make websites comply with the standard. The order included a substantial payment and ran for twenty years.

The lesson is narrow and clear. Selling a preference widget is lawful. Claiming it delivers compliance is the thing that drew the action.

How to think about it

If you like the preference panel and your readers use it, there is nothing wrong with offering one. Treat it the way you would treat a print stylesheet or a dark mode toggle.

What it must not do is stand in for building the page properly. Headings in order, real controls, described images, labeled fields. Those are the foundation and no script supplies them.

Be careful about what you say on your own site as a result. Installing a widget does not entitle you to claim anything about compliance.

The alternative that actually holds

Fixing the page itself is permanent, costs nothing per visitor, works with every assistive technology, and cannot be switched off by a script failing to load.

It is also almost entirely structural. Most of what an overlay attempts to paper over comes down to a few dozen decisions about markup and color.

Every page written by Website Builder Studio is checked before anything publishes, validated against Google Search Essentials and modern web standards, so the structure is right when the page ships rather than adjusted afterwards.

It also costs nothing per visitor, survives the script failing to load, and cannot be switched off by a browser extension — three things no third-party widget can say.

What we say about our own checks

We check what a machine can check and we tell you plainly what that covers. A check is not a certificate, and the in-app assistant explains which findings a person still has to judge.

Nothing here is legal advice, and no tool we sell makes a claim about your legal position. The parts that depend on truthfulness, such as whether an image description is accurate, are yours.

That is a smaller promise than an overlay makes. It has the advantage of being one we can stand behind.

The split between what a machine can judge and what needs a person is set out in automated and manual testing, and it is the honest frame for any tool including ours.