Accessibility ≠ Overlay: the European Commission recommends fixing accessibility at the source
The European Commission puts it plainly: if a tool does not make the website itself meet the applicable accessibility criteria, it is not an appropriate solution. Accessibility problems should be fixed at their source.
The European Commission enters the overlay debate
In its official web accessibility guidance, the European Commission specifically addresses accessibility overlays. It explains that the technical requirements linked to the Web Accessibility Directive rely on the harmonised European standard EN 301 549 v3.2.1 and distinguishes between adding a tool and actually meeting those requirements.
Adding a tool is not the same as meeting the criteria
An overlay may add controls, alter styles or attempt runtime repairs. The relevant question, however, is whether the resulting website satisfies the accessibility requirements that apply to it. The Commission states that overlays, or any other tools, that do not ensure the website itself meets the detailed criteria are not an appropriate solution.
Fix accessibility at the source
The Commission’s recommendation is direct: it is better to fix accessibility problems at their source. If a form field lacks an accessible label, fix the form. If a menu does not work with a keyboard, fix its interaction. If a custom component does not expose its name, role or state correctly, fix the component itself.
The goal is not to make an external layer appear to compensate for the problem, but to make the original interface accessible.
What role does EN 301 549 play?
EN 301 549 sets accessibility requirements for ICT products and services. For the Web Accessibility Directive, the Commission identifies harmonised version 3.2.1 as the technical reference. Compliance therefore cannot be reduced to installing a widget or obtaining a good automated score.
Testing with disabled people remains necessary
The Commission also recommends involving disabled people in testing. Automated tools can identify certain errors, but they do not reproduce the full experience of people using keyboards, screen readers, magnification, voice recognition or other assistive technologies.
Accessibility ≠ Overlay
This fourth article adds the European Commission’s published position to the series: an additional tool is not an adequate solution if the website still fails to meet accessibility criteria. The practical recommendation is to design, develop, evaluate and maintain accessibility in the product itself.
Official sources
European Commission — Web Accessibility
Web Accessibility Directive — Standards and harmonisation
This article is part of the Accessibility ≠ Overlay series. Issue 04 — European Commission.