Success Criterion 2.5.3
Conformance level A

2.5.3 · Label in Name

Lesson overview · Label in Name

In plain language

What a control SAYS on screen must be part of what it's CALLED for assistive tech.

Who it affects

Voice-control users and screen-reader users who depend on spoken names matching visible text.

How to check

Inspect controls with visible text: the accessible name must contain that exact visible text.

Common misconception

An aria-label that adds *extra* context beyond the visible label is fine. The failure is when the aria-label replaces the visible words entirely, so voice-control users saying the visible label get no match.

Learn more

Understanding Understanding this success criterion (opens in a new tab)

Scenarios in this lesson

Accessible Name That Doesn’t Match the Control’s Visible Label
Visible Label Text With No Accessible Name Behind It
ARIA Label Naming a Completely Different Action Than Shown
Accessible Name Built From an Icon Instead of Visible Text
Translated ARIA Label That Doesn’t Match the Visible Language
Visible Label Text Reordered or Broken Apart in the Name
ARIA Reference Pointing to the Wrong Element for a Name
Accessible Name Missing the Units Shown in the Visible Label
Title Attribute Overriding a Control’s Intended Accessible Name
Link’s Accessible Name Missing the Words Shown on Screen