An accessibility widget — often a standalone piece of code that you add to your website with a single line and that promises to make the site accessible "in seconds" — does not comply with the European Accessibility Act. The technical standard that the directive prescribes, EN 301 549 (in practice WCAG 2.1 level AA), tests whether the underlying code and interaction are accessible: can someone using a screen reader complete the checkout process, is every form field correctly labeled, can the site be operated using only a keyboard. A widget that applies a layer on top of the existing code does not change that underlying structure.
That is immediately the answer to the question many entrepreneurs ask after purchasing an overlay widget: no, that purchase alone does not make you compliant. The widget can enlarge the font, adjust contrast, or display a reading bar, and these are useful functions in themselves for some visitors. But the law demands something different: that the website itself, in the code, meets the requirements — not that there is a separate control panel alongside it.
Why an overlay does not address the core issue
Screen readers and other assistive software read the HTML structure of your page: the headings, the labels on form fields, the alt text on images, the order in which elements are reachable by Tab. An overlay widget runs as a separate JavaScript layer on top of that structure. It can display text larger or adjust colors, but it does not rewrite the underlying HTML in which, for example, a button lacks a label or an image lacks alt text. If that problem exists, it remains — for the widget and for the visitor who encounters it.
There is more: different users with visual disabilities and the organizations that represent them report that some overlays actually make operation more complicated, because the widget itself does not work well with the screen reader that someone already uses. Two assistive tools trying to operate on top of each other at the same time do not always produce a better result than one correctly built page. Anyone uncertain whether that applies to their own site will find in answers to questions that other entrepreneurs also ask a number of similar situations.
What the law actually expects
The directive requires an accessibility statement in which you indicate the extent to which your site or app meets the standard, which parts do not yet meet it, and what plan addresses that. That statement is based on your own assessment of the actual code and interaction, not on the presence of a tool. In the overview of the issues that most frequently go wrong it is spelled out concretely what that covers: color contrast, form labels, alternative text, and operability with keyboard only consistently come up.
That does not mean everything must be manually fixed before you know anything. An automated test of the key pages, including the checkout process and the login flow, often already reveals where the biggest bottlenecks are. You can request such an initial picture in a few minutes with the free quick-scan, though it remains true that an automated scan cannot test everything — whether alternative text is substantively correct, for example, requires human judgment.
What axessia does and does not do
We do not sell overlay widgets, and we do not build repairs into your code. This is a deliberate choice: a widget can create the impression that a problem has been solved, while the underlying page remains unchanged. What we do is test, prioritize, and document — the scan identifies what likely does not comply, the report presents this in plain language ordered by importance, and the system monitors whether the site remains accessible after your next update to your shop or app. How that testing works exactly and where the information comes from, we explain on the page that shows step by step how the system works.
For the question of whether a widget is "enough", that distinction is the most important thing to remember: a widget is a user setting, not a substitute for accessible code. If you are unsure whether a supplier of such a product is right to claim that a site complies with WCAG through it, you can best test that claim against the standard itself or ask a specialist.
First step without purchase
Before you invest in a widget, an audit, or an improvement plan, it is usually more useful to first know whether and to what extent the law applies to your organization, and where the largest gaps are. That overview is available free of charge, and does not require an account.
Do you want to see for yourself where your website or app currently stands, independent of what a widget supplier tells you? Do the free quick-scan and continue reading through the knowledge base to determine which step is most appropriate for your situation.