- Success Criterion 4.1.2
- Conformance level A
- W3C reference F68
Form Field With No Programmatic Label at All
4.1.2 — Name, Role, Value
Scenario
Setting
An e-book reader's library page
What’s wrong
A form field has no programmatic label — screen readers announce 'edit text' with no idea what to type.
Example
Here's what happens on an e-book reader's library page: a form field has no programmatic label — screen readers announce 'edit text' with no idea what to type.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. In this case (an e-book reader's library page), they hit a dead end with no way forward.
How to test
Tab to a form field and check its accessible name in DevTools: if none is programmatically determined, it fails.
How to fix
Associate a label with every form field (label for/id pairing (code tying a label to its field), aria-label, or aria-labelledby (code pointing to the element that names it)).
Outcome
Once corrected, an e-book reader's library page lets them get the same outcome as everyone else.
Who is affected
Screen-reader and voice-control users who can operate only what the accessibility tree exposes.
Learn more
- Understanding Understanding document (opens in a new tab)
- Technique Related technique (opens in a new tab)
Related scenarios
- Custom Dropdown or Slider With No Accessibility API Support
- Content Changes That Never Update Their Accessible Name
- Scripted Link or Button With No Real Role or Keyboard Support
- Clickable Div Turned Into a Control but Given No ARIA Role
- Assistive Technology Never Told Which Element Currently Has Focus
- Multi-Part Field Where Each Box Has No Individual Name