- Success Criterion 3.3.2
- Conformance level A
Character Limit Enforced but Never Communicated to Users
3.3.2 — Labels or Instructions
Scenario
Setting
A hospital's patient portal appointment scheduler
What’s wrong
Character limits enforced but never communicated.
Example
<input type="text" placeholder="Full name">Why it matters
Everyone filling forms, especially people with cognitive disabilities and magnifier users.
How to test
Type past any enforced character limit: if the field silently stops accepting input with no stated limit anywhere, 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 hospital's patient portal appointment scheduler, 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
- 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