- Success Criterion 2.4.6
- Conformance level AA
Same Label Used for Two Different Fields on One Form
2.4.6 — Headings and Labels
Scenario
Setting
A dating app's profile setup
What’s wrong
Ambiguous duplicate labels ("Name" for both product and user in one form).
Example
<label for="user-name">Name</label>
<input id="user-name">
...
<label for="referral-name">Name</label>
<input id="referral-name" placeholder="Friend who invited you"> Why it matters
A screen reader jumping between form fields hears Name twice and can't tell whether it's entering their own name or a referrer's.
How to test
Check for duplicate labels used for different purposes (e.g., 'Name' for both a product field and a user field) within the same form: ambiguity here fails.
How to fix
Reusing the same label for different fields on one form creates real ambiguity, even when each field is technically valid.
<label for="user-name">Your name</label>
<input id="user-name">
...
<label for="referral-name">Friend's name (who invited you)</label>
<input id="referral-name"> Outcome
A user fills in Your name and Friend's name without second-guessing which field is which.
Who is affected
Screen reader users filling out the profile risk entering their own name into the referral field or vice versa.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Heading or Label That Fails to Describe Its Own Purpose
- Generic Section Heading Like ‘Introduction’ That Says Nothing
- Identical Headings Repeated Over Completely Different Content
- Form Label Like ‘Field 1’ That Doesn’t Describe Its Purpose
- Clever Marketing Heading That Hides What a Section Actually Does
- Button Labeled ‘OK’ on a Destructive, Irreversible Action