If an input field has no label correctly associated with that field, a screen reader cannot tell what the user should enter. The user hears only "edit, empty text field" without knowing whether it concerns a name, an email address, or a postal code. The consequence is direct and concrete: people who rely on a screen reader or voice control cannot reliably fill in the form. With a contact form, that is inconvenient; with an order or registration form, it affects the core of your service.
This is not a theoretical risk. EN 301 549, the standard to which the European Accessibility Act refers, requires that each form field have a name, role, and value that can be read by software — in practice, this means a label that is programmatically associated with the field, not merely placed visually next to it. If that association is missing, it is one of the most frequently found issues during an audit, precisely because it is so easy to overlook at a glance.
What goes wrong in practice
The most common situations are a placeholder that serves as a label and disappears as soon as someone starts typing, a label that is present but not linked to the field via the for attribute, and fields that are indicated only by an icon or colour. In all three cases, a sighted user sees a form that works fine. For someone using a screen reader, the field is effectively unnamed. forfor
On top of that, required fields are often marked only with an asterisk or red color. Anyone who cannot perceive color misses that indication and only encounters an error message after submission — which then fails to be clearly linked to the correct field among the same type of fields. This way, small defects accumulate into a form that is simply impossible to complete for part of your visitors.
The consequences you do feel
The most direct consequence is loss of conversion: visitors who cannot fill in a form abandon it, contact you through another channel, or go to a competitor. This effect is not limited to people with a visual impairment — anyone who has a form filled in automatically via browser or assistive software is also dependent on correctly linked labels.
The second consequence relates to your obligations under the accessibility directive. In the mandatory accessibility statement, you indicate the extent to which your service complies with EN 301 549 and which gaps remain. Form labels that are incorrect should then appear as a known gap in that statement, with an action plan and timeline. If you do not do so and the gap comes to light through a complaint or inspection, then the question is not just whether the problem exists, but also whether you had already identified it.
The third consequence is less visible but equally relevant: a form with poorly linked labels is often a sign that broader structural issues exist in the code — the same underlying cause then also appears in error messages, in groups of related fields, and in the confirmation step. If you find it in one form, it is wise to review the rest of the ordering and login flow with the same eye.
What a scan does and does not show
Missing or disconnected labels are technically easy to identify, and should therefore be part of what automated testing detects as standard. Yet the caveat that appears in every axessia report also applies here: an automated scan tests the structure of the code, not whether the wording of a label is actually clear to the user. A field that is technically correctly labeled with the text "field 3" meets the structural requirement, but helps no one. This nuance is why a scan result is a starting point, not a final judgment.
If you want to know whether this type of issue also occurs on your own forms, then the free quick-scan of your key pages already provides an initial indication. For the checkout process and login environment, where forms are often most complex, the full assessment goes deeper; what is and isn't tested in that process is clearly laid out. How that assessment works exactly and which parts can and cannot be checked automatically, you can read in the explanation of our methodology.
Whether a found issue creates obligations in your situation and within what timeframe is for a lawyer or the competent supervisory authority to determine. What you can do yourself is recognize the issue before a complaint or inspection does it for you. In our knowledge base it is detailed per topic what form labels must meet and how you can check that on a normal working day, without needing to be a technician.