Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use a single label for each form field. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 15% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 1% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 8% | 0% |
| case-20 | ✓→✗ | ▼ Worse | -2% | 0% |
| case-08 | ✓→✓ | = Same ✓ | -28% | 0% |
Multiple labels for a single field can cause screen readers to announce redundant information or fail to correctly associate the input with its purpose.
Search for form inputs that are associated with more than one <label> element.
Consolidate multiple labels into a single <label> or use aria-labelledby to reference multiple sources of text.
Explain how a 1:1 relationship between labels and inputs ensures clarity for assistive technology users.
Review the rendered markup and interactive states that affect Use a single label for each form field. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/form-field-multiple-labels
Other measured skills in the registry, with their headline benchmark lift.