Forms & errors
A Form Field Has No Visible Label, Only a Hidden Hint
The field's name lives only in a tooltip or hidden description, so many people can't see what to type, and screen readers may not say it clearly.
label-title-onlyBest practiceBest practice — not a WCAG requirement, but it helps people all the same.
- Status
- SeriousSerious — Significant friction, or information that is lost.CurrentScanners run this rule today.
- Owner
- DesignDevContentTest
- Audit
- Automated+ManualA scanner finds it; a person confirms the fix.
Why it matters
The title attribute shows a small tooltip, but only when a mouse hovers. It doesn't show on touch screens or when you Tab to the field. Text linked with aria-describedby is meant as an extra hint, not the field's name.
People need a label they can see while they type. Without one, they guess, make mistakes, or give up. Screen readers may treat the hint as a description, not a name, so the field can sound unnamed.
Who it affects
| Who | What they experience | Impact |
|---|---|---|
| Low-vision users (magnification) | When zoomed in, they may never find the tiny tooltip, so they can't tell fields apart. | High impact |
| Cognitive and neurodivergent users | Once they start typing, any placeholder is gone and nothing on screen says what the field is for. | High impact |
| Voice control users | They can't see a name to say, so they can't easily move to the field by voice. | High impact |
| Screen reader users | They usually hear the hint, but it may come as a description after a pause, or not at all. | Partial impact |
| Keyboard-only users | Tabbing to the field doesn't show the tooltip, so they see an empty box. | Partial impact |
| Motor and dexterity | On a touch screen or with a switch, there's no hover, so the tooltip never appears. | Partial impact |
Business & product impact
| Area | Why | Impact |
|---|---|---|
| Legal | This rule is a best practice, not a WCAG fail on its own. But fields without visible labels often trigger other findings in a WCAG 2.2 AA audit under Australia's Disability Discrimination Act. | Moderate impact |
| Conversion | Unlabelled fields cause wrong entries, form errors and abandoned sign-ups or checkouts. | High impact |
| SEO | Search engines don't reward visible form labels. Don't sell it that way. | Low impact |
| Brand trust | Forms that make people guess feel careless, and everyone notices, not just disabled users. | Moderate impact |
| Cost to fix | Adding a `<label>` is quick. Fixing it in the shared form component fixes every form. | High impact |
Fixing it in code
A field named only by a tooltip
Don't
<input type="email" id="email" title="Email address">A screen reader says: “Edit text, Email address (varies by screen reader)”
Do
<label for="email">Email address</label>
<input type="email" id="email">A screen reader says: “Email address, edit text”
A visible <label> names the field for everyone, on every device.
A field named only by a hint
Don't
<p id="pc-hint">Your postcode</p>
<input type="text" aria-describedby="pc-hint">A screen reader says: “Edit text, Your postcode”
Do
<label for="pc">Postcode</label>
<input type="text" id="pc" autocomplete="postal-code">A screen reader says: “Postcode, edit text”
aria-describedby adds extra detail; the name must come from a label.
Fixing it in design and content
Search box with only a placeholder
Don't
A search field shows "Search" as greyed placeholder text, with a tooltip on hover.
Do
Show a visible word "Search" next to or above the field, or on the attached button, and keep it there while typing.
A screen reader says: “Search, edit text”
The label stays on screen, so people never lose track of the field.
Designer's handoff note
Give every field a visible label that stays on screen while typing. Don't rely on placeholder text or tooltips.
Put the label above or beside the field, close enough that it clearly belongs to it.
Quick test
Tool
The keyboard alone
Checklist
- Pass
- Every field has a visible label that stays on screen while you type.
- Fail
- A field shows no name, or its name only appears on mouse hover or disappears when you type.
Check these at the same time
What a green scan still misses
A scanner can't tell whether the visible label is clear, close to its field, or matches what's asked. Read the form as a new user would.
Reference
- Rule ID
label-title-only- Raised by
- axe-core: “Form elements should have a visible label”
- WCAG
- Best practice — not a WCAG requirement
- Last reviewed
- 14 October 2026