A11yDen

Home / Guides

Form labels that work for everyone

Every form control needs a name a person can perceive and software can read. When a field has no proper label, a screen reader user hears "edit text, blank" and has to guess; a voice control user cannot say the field's name to jump to it; and everyone loses the big click target a real label provides. Labels look like the simplest thing in accessibility — and are among the most commonly broken.

The criteria that govern a label

How to associate a label, in order of preference

  1. <label for="…"> with a matching id — the robust standard; clicking the label focuses the field, which helps everyone.
  2. Wrapping — putting the control inside its <label> element also associates them.
  3. aria-labelledby — points at existing visible text; the right tool for groups and unusual layouts.
  4. aria-label — a name with no visible text at all. A last resort: invisible labels cannot be seen by sighted voice-control users, which is exactly the mismatch SC 2.5.3 exists to prevent.

Placeholder text is not a label

A placeholder disappears the moment typing starts, taking the instruction with it. Its contrast is typically low, some screen readers do not announce it reliably, and it gives voice users nothing visible to say. Use placeholders only for a short example of the expected format — "e.g. 2026-01-31" — and always pair them with a real, persistent label. If a design removes labels "to look clean", the design is the defect.

Instructions, required fields and errors

The voice-control test you can do in your head

For every control on the form, ask: if a user said "click" followed by the words they can see, would the software find this field? If the visible text says "Email" but the accessible name is "Enter your electronic mail address here", the answer is no — and SC 2.5.3 fails. Visible text first, word for word, in the accessible name; extra description goes after it, never instead of it.

Put it into practice

Form Label Checker

Find unlabelled controls, placeholder-only labels and broken references.

Sources and checking

WCAG facts in this guide follow the official W3C WCAG 2.2 Recommendation and its Understanding documents; any other fact is attributed to its source in the text. Facts checked November 16, 2026. Direct links to the sources are in the references below.

References

More guides