- Success Criterion 3.3.2
- Conformance level A
Required-Field Asterisk Used With No Explanation Anywhere
3.3.2 — Labels or Instructions
Scenario
Setting
A pharmacy app's prescription-refill form
What’s wrong
An asterisk (*) marks required fields but its meaning is never explained anywhere on the form — users unfamiliar with the convention don't know what it signifies.
Example
<label for="dob">Date of birth *</label>
<input id="dob">
<!-- the asterisk appears on several fields but its meaning is never defined anywhere on the page --> Why it matters
A patient unfamiliar with form conventions doesn't know the asterisk means required, skips the date of birth field, and the refill request gets rejected.
How to test
Look for an asterisk (*) marking required fields, then search the form for text explaining what it means: if the meaning is never stated anywhere, it fails.
How to fix
State what the asterisk means once, in plain language, near the top of the form.
<p>Fields marked with an asterisk (*) are required to process your refill.</p>
<label for="dob">Date of birth *</label>
<input id="dob"> Outcome
The patient understands the asterisk and completes every required field on the first submission.
Who is affected
Older adults, non-native speakers, and people with cognitive disabilities who may not recognize the asterisk convention.
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