Forms
Form field has more than one label
WCAG 2.2 success criterion 1.3.1 Info and Relationships (Level A)
- WCAG 2.2
- 1.3.1 Info and Relationships
- Level
- A
- Default severity
- Needs review
- Available in
- Free
Why it matters
When two labels point at one field, browsers and screen readers disagree about what to announce: some join them, some read only the first.
Who it affects: Screen reader users, voice-control users who say a field's label to move to it, and people with memory or attention difficulties who lose a placeholder once they type.
What Lumtera flags
Form fields referenced by more than one <label> element.
Check ID form-field-multiple-labels — use it to filter the content report or with wp lumtera issues --rule.
How to fix it in WordPress
Keep one <label> for the field and put all the label text in it. Extra help such as "We never share your email" belongs in a hint tied to the field with aria-describedby. In form-builder plugins, this usually means removing a label you added by hand next to the field's own label setting.
Example
<label for="email">Email</label>
<label for="email">We never share it</label>
<input id="email" type="email">
<label for="email">Email</label>
<input id="email" type="email" aria-describedby="email-hint">
<p id="email-hint">We never share it.</p>
How to check your fix
- Update the post. The issue disappears from the Accessibility sidebar on the next check, and from the site report on the next scan.
- Click each field's label: the cursor should move into the field. With a screen reader, each field should announce its label when it receives focus.
Find this issue across your whole site
Lumtera runs this check in the block editor sidebar as you write, in the Elementor panel, in Review mode on the live page, and across the whole site in the content report and with wp lumtera scan. You can change its severity or turn it off in Accessibility → Settings.
Related checks
-
WCAG 1.3.1 · AError
Heading is empty
-
WCAG 1.3.1 · ANeeds review
Heading level is skipped
-
WCAG 1.3.1 · ATip
Content uses an H1 heading
-
WCAG 1.3.1 · ATip
Bold text may be a heading
-
WCAG 1.3.1 · ATip
Heading is very long
-
WCAG 4.1.2 · AError
Form field has no label
Start with the free plugin today
All 64 checks, the editor sidebar, Elementor panel and site report — free, with no account and no page limits.