Best practices

Why accessibility overlays are not enough

Widgets that promise compliance in one line of code do not fix the source code. Here is why, and what to do instead.

An accessibility overlay is a layer added to an existing site via a script. The vendor promises instant compliance. The reality is more nuanced, and the shortcut has a cost.

They do not fix the source

An overlay tries to repair the page at display time, without touching the code. Yet screen readers and assistive technologies read the real code. Problems with structure, forms or navigation therefore often remain.

They create a false sense of security

Showing an accessibility button can give the impression that the topic is handled. That is misleading: compliance is not measured by the presence of a widget, but by the real accessibility of the journeys.

They are increasingly contested

Overlays face criticism from experts and associations, and litigation. Some even hinder the people they claim to help, by interfering with their own tools.

What to do instead

The durable route is to identify the real problems through an audit, fix them at the source (often CSS, ARIA attributes, text alternatives), then publish an honest statement and monitor for regressions. This is exactly Inclaria's approach.