Misplaced Field Label

A control's visible text should lead its accessible name, not trail behind other context, so Voice Control matching stays fast and reliable.

WCAG Reference

Maps to: WCAG 2.5.3 Label in Name | Applies to: WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.1 | Level: A | Read the official specification →

What this rule checks

This is the companion to Mismatched Label Text, using the same visible-text recognition and the same interactivity and visibility filters. This rule applies only when that one passes: it reports elements whose label contains the visible text but does not begin with it. If the label does not contain the visible text at all, Mismatched Label Text owns that finding and this one stays silent. (Beta rule)

Why it matters

Voice control matches names from the front, and screen reader users hear extra context before the label they can see on screen. A button reading "Next" labelled "Proceed to payment, Next" technically satisfies label-in-name, yet the user saying "Tap Next" gets slower, less reliable matching than if the label began with the visible word.

Common failure patterns

• prefixing context onto the label: "Order summary, Edit" on a button that reads "Edit"
• composing a cell's combined label so the control's own text lands last

Remediation guidance

• start the accessible name with the visible label; put any extra context after it ("Edit, order summary", not "Order summary, Edit")
• iOS: begin accessibilityLabel with the control's visible text; keep supplementary detail after it or in accessibilityHint

Related docs

• Mismatched Label Text
• iOS Rule Repository
• Accessibility Issue Remediation Guide