Form fields have no associated label
Automated check label, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Blocker: a task cannot be completed
- Typical effort
- Moderate, 1 to 4 hours
- Category
- Forms and controls
Who this affects
Screen reader users, voice-control users, and people with cognitive differences who rely on persistent labels.
Why it matters
Without a programmatic label the user hears "edit text, blank" and has no idea what to type. Placeholder text is not a substitute: it disappears the moment typing starts, and usually fails contrast too. Unlabelled checkout and contact fields are a direct revenue loss.
How to fix it
Use <label for="id"> bound to the input id, or wrap the input in the label. Keep the visible label; do not rely on placeholder alone.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Forms and controls
- Custom buttons, links or menu items have no accessible name
- Dialogs have no accessible name
- Custom input widgets have no accessible name
- Custom checkboxes, switches or radio buttons have no accessible name
- Form fields use invalid autocomplete values
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name