Why doesn't a screen reader read my form fields?

Why a visible label does not always count

A screen reader will not read out a form field when the label that appears on the screen is not programmatically linked to that field — the text is visible, but the code lacks the reference that a screen reader needs to connect label and field. This typically happens because the `for` attribute of the label does not match the `id` of the input field, because the label does not wrap around the field in the markup, or because only a placeholder is used instead of an actual label element. To the eye, the form looks perfectly fine; to a screen reader, the field has no name.

This type of error can be detected automatically to a large extent: a scan will identify whether a label element is missing or does not refer to the correct field, and whether a field has only a placeholder instead of a label. What a scan does not assess is whether the label text that is there actually conveys what the field is asking for — a label with the text "field 1" is technically correct when linked, but conveys no meaning to a user. That assessment remains manual work, even when the link itself is correct.

Where this appears in WCAG 2.1

This requirement follows from WCAG 2.1, the compliance framework that EN 301 549 essentially translates into practice: criterion 1.3.1 (Info and Relationships) requires that the relationship between a label and its field is also established programmatically and not only visually visible, criterion 4.1.2 (Name, Role, Value) requires that every form element has a name that can be read by software — including a screen reader — and criterion 3.3.2 (Labels or Instructions) requires that a field has a label or instruction at all. Together, these three criteria determine whether a form field is recognizable and usable for someone using a screen reader.