- Success Criterion 3.3.2
- Conformance level A
Field With Only an ARIA Label and No Visible Label
3.3.2 — Labels or Instructions
Scenario
Setting
A news outlet's article page
What’s wrong
Field has a programmatic name only (aria-label) with no persistent visible label — sighted-cognition users get placeholder-or-nothing.
Example
<input type="email" aria-label="Email address for newsletter">
<button>Subscribe</button>
<!-- no visible label or heading, just an empty box next to the button --> Why it matters
A reader with memory or attention difficulties glances away mid-article and comes back unable to tell what the empty box beside 'Subscribe' is for.
How to test
Inspect the field in DevTools: if it has only an aria-label (no persistent visible label on screen), sighted users relying on visual scanning get nothing.
How to fix
A programmatic name helps assistive tech, but sighted users need a visible label too, not either/or.
<label for="newsletter-email">Email address</label>
<input type="email" id="newsletter-email">
<button>Subscribe</button> Outcome
A reader immediately recognizes the newsletter box and signs up without hesitating.
Who is affected
Sighted users with cognitive disabilities, and screen magnifier users who zoom in and lose surrounding context, since aria-label gives them nothing to see.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Multi-Part Field Like a Phone Number With No Text Label
- Icon-Only Search Field With No Accessible Label
- Placeholder Text Used as the Only Label, Vanishing on Input
- Required Input Format Never Stated Until After an Error
- No Indication of Which Fields on a Form Are Required
- Radio Button Group Missing Its Question or Prompt Text