Fix label axe errors
A form control has no programmatic label, so assistive technology cannot announce what input is expected.
Affected users
Screen reader users, speech-input users, and people who rely on larger click targets.
WCAG mapping
1.3.1 Info and Relationships (A); 3.3.2 Labels or Instructions (A); 4.1.2 Name, Role, Value (A)
Detection
wcagc reports unlabeled controls and keeps the finding separate from manual checks such as instruction quality.
Failing markup
<input id="email" type="email">Fixed code
<label for="email">Email</label>
<input id="email" type="email" autocomplete="email">Sources and standards
FAQ
Is placeholder text enough?
No. Placeholders disappear and are not a reliable accessible name. Use a visible label or an equivalent programmatic label.
Can aria-label fix this?
It can, but visible labels are usually better. Use aria-label when a visible label is not possible.
One rule rarely travels alone
Run a page through wcagc to find this rule, related WCAG issues, affected selectors, and manual checks that automation cannot judge.
Scan a page