Form fields should not have multiple conflicting labels

Checks form controls for multiple associated labels and flags patterns likely to produce conflicting accessible names.

• Screen readers may announce noisy or confusing names
• Users may misunderstand expected input
• Inconsistent labels hurt form completion rates

Associate each control with one clear visible label, and use supplemental help text separately.

Bad Example:

<label for="email">Work Email</label>
<label for="email">Primary Contact</label>
<input id="email" type="email">

Good Example:

<label for="email">Work email</label>
<input id="email" type="email" aria-describedby="email-help">
<p id="email-help">We’ll only use this for account notifications.</p>

• Multiple <label for> tags for a single input
• Duplicating label text in aria-label
• Mixing placeholder text as a primary label

• Inspect computed accessible name in devtools
• Test with screen reader form navigation
• Confirm each field has one clear label and optional description