- Success Criterion 3.3.2
- Conformance level A
Required Input Format Never Stated Until After an Error
3.3.2 — Labels or Instructions
Scenario
Setting
A dating app's profile setup
What’s wrong
Required format not stated (date format, password rules) until after error.
Example
<input type="text" placeholder="Full name">Why it matters
Everyone filling forms, especially people with cognitive disabilities and magnifier users.
How to test
Try submitting a field with a specific required format (date, password) without reading any instructions: if the format is only revealed after you get it wrong, it fails.
How to fix
A persistent visible label must be provided, required status must be marked visually AND programmatically (with any symbol explained), and format rules stated before input.
<label for="name">Full name</label><input type="text" id="name" placeholder="e.g. Jane Smith">A persistent visible label survives once the user starts typing; a placeholder alone disappears.
Outcome
On a dating app's profile setup, this barrier is gone for everyone filling forms — they can finish what they came here to do.
Who is affected
Everyone filling forms, especially people with cognitive disabilities and magnifier users.
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
- No Indication of Which Fields on a Form Are Required
- Radio Button Group Missing Its Question or Prompt Text
- Field Instructions Placed After the Field They’re Meant to Explain