2.5.3 Label in Name (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.5.3 Label in Name (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.5.3 Label in Name
2.5.3 Label in Name (Level A)
What it requires: If a control has a visible text label, its accessible name (what a screen reader announces) has to include that visible text — this matters for voice-control users, who speak the visible label to activate a control.
Common failure: A button visually reads “Subscribe” but is coded with aria-label="Join our newsletter list" — a voice-control user who says “click Subscribe” (matching what they see) finds nothing to activate, because the accessible name doesn’t contain that text.
Fix it: Make sure a control’s accessible name (via aria-label, aria-labelledby, or just its own text content) always includes the visible label text verbatim, even if you want to add extra context — put the extra context after the visible text, not instead of it.
In 2.5 Input Modalities: ← 2.5.2 Pointer Cancellation · 2.5.4 Motion Actuation →
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.