Level AWCAG 2.1

2.5.3 Label in Name

For user interface components with labels that include text or images of text, the accessible name contains the visible text label.

Last reviewed: September 9, 2026

Understanding 2.5.3

Speech-input users (Dragon NaturallySpeaking, Voice Control, Voice Access) operate a page by saying the visible label of the control they want, such as "click Search" or "click Submit." If the accessible name computed for that control doesn't contain the visible label text, the voice command fails to match, even though a sighted mouse user has no trouble finding the button. This criterion exists so visible labels and programmatic names stay in sync for anyone who navigates by referring to what they see on screen.

How to Meet It

When you set an accessible name via aria-label or aria-labelledby, make sure it includes the visible text label as a substring, ideally with the visible text appearing first, since some speech tools match from the start of the name. Avoid aria-label values that replace or contradict the visible text with unrelated wording. When possible, let the accessible name come from the visible text itself (native <label>, button text content) rather than overriding it.

Code Examples

INCORRECT

<!-- Visible label says "Search", but voice command "click Search" won't match this accessible name -->
<button aria-label="Submit the current query now">Search</button>

CORRECT

<!-- Accessible name starts with the visible label text -->
<button aria-label="Search products">Search</button>

Frequently Asked Questions

Can the accessible name include more than just the visible text?

Yes. Adding extra context (e.g., "Search products" for a button visibly labeled "Search") is fine as long as the visible text is present in the accessible name, ideally at the start.

Does this apply to icon-only buttons with no visible text?

No. This criterion only applies when there is a visible text label (or image of text) to compare against. An icon-only button still needs an accessible name under 4.1.2, but 2.5.3 has nothing to check it against.

Related Success Criteria

2.5.1 Pointer Gestures 2.5.2 Pointer Cancellation 2.5.4 Motion Actuation 2.5.5 Target Size (Enhanced)

Quick Facts

Criterion2.5.3
LevelA
IntroducedWCAG 2.1

Automate Compliance

AccessiSight automatically scans and identifies 2.5.3 issues in your codebase.

Try Scanner Free