Checklist
Keep the visible command intact in the accessible name
Adding helpful hidden words can split the phrase a person sees. Check the whole label inside the actual name.
Before you use it
- Use when
- A visible button name does not work as expected with speech input.
Keep this limit in mind
- This does not mean every accessible name must be identical to its visible label. Repeated controls may need additional distinguishing context.
Current editorial reading
Compare the label with Name, not Description
For a control with a visible text label, inspect its computed Name in the browser’s accessibility inspector. Keep the label’s words together and in order. A button reading Export report does not retain that phrase in the name Export monthly report. Export report for March does. Do not demand a character-for-character match: capitalization and most punctuation do not determine this check.
Add context without breaking the command
Putting the visible label first is a WCAG best practice, not a separate requirement. Monthly Export report still contains the phrase, although it does not follow that preference. Extra help can belong in Description instead. An aria-describedby association supplies a description; it cannot repair a missing phrase in Name. Check any aria-label or aria-labelledby that overrides the visible text.
Then try the intended command
Use the visible phrase with the supported speech-input setup and record which control responds. Record the browser, speech tool and settings. If it fails, inspect the name and the interaction; matching text alone does not guarantee operation. Icon-only controls still need appropriate names, but this visible-text comparison does not cover them.
Take it with you
Save the visible label, computed Name and observed command result separately. A screen reader may speak a description after the name, so hearing the visible words somewhere is not enough. This is a focused naming check, not a full accessibility evaluation.
Sources and evidence (5)
What we checked
WCAG 2.2 SC 2.5.3 requires a control’s name to contain its visible text label; placing that text first is stated as best practice.
W3C Recommendation 2024-12-12; criterion and note inspected 2026-10-06. The normative containment requirement and best-practice prefix placement are distinct. This is a standard, not an efficacy study.
Web Content Accessibility Guidelines (WCAG) 2.2 · 2.5.3 Label in Name, Level A, criterion and note
G208 describes including the visible text string intact and in order.
Technique updated 2025-09-24; selected passages inspected 2026-10-06. Informative sufficient technique, not an additional normative rule. The Export report examples are original editorial illustrations.
G208: Including the text of the visible label as part of the accessible name · Description; Tests, Procedure 1
Inserting a hidden word between the words of a visible label can break the label-to-name match.
Failure technique updated 2026-05-18; selected passages inspected 2026-10-06. Used for the specific interrupted-phrase counterexample; no claim that every speech tool fails on every such control.
F96: Failure due to the accessible name not containing the visible label text · Example 2; Tests
ARIA naming can override native text; aria-describedby contributes a description rather than an accessible name.
Understanding page updated 2026-04-05; selected passages inspected 2026-10-06. Screen-reader speech may include both name and description. Inspector comparison and the recorded speech trial are editorial checks; this draft reports no real speech-input or screen-reader test.
Understanding Success Criterion 2.5.3: Label in Name · Accessible Name and Description Computation specification
Label in Name does not apply where a control lacks a visible text label, and capitalization and most punctuation are not decisive for its matching check.
Selected passages inspected 2026-10-06. Other naming requirements still apply. Symbols and mathematical expressions have specific treatment in the full guidance; this card does not offer a universal literal-string algorithm or full conformance judgment.
Understanding Success Criterion 2.5.3: Label in Name · Intent; Symbolic text characters; Punctuation and capitalization
Chrome DevTools exposes computed accessibility properties, while markup inspection does not establish successful assistive-technology navigation.
Official tool documentation updated 2026-05-28; selected passages inspected 2026-10-06. Supports the feasibility and limits of the inspector step. Other browsers may expose equivalent information through different tools; no browser or assistive-technology runtime test was performed.
Accessibility features reference — Chrome DevTools · Overview of accessibility features in Chrome DevTools; The Accessibility tab; View an element’s computed accessibility properties
Editorial sources (5)
- Understanding Success Criterion 2.5.3: Label in Name
- Web Content Accessibility Guidelines (WCAG) 2.2
- G208: Including the text of the visible label as part of the accessible name
- F96: Failure due to the accessible name not containing the visible label text
- Accessibility features reference — Chrome DevTools
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingKeep the visible command intact in the accessible name
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
WCAG 2.5.3 requires the accessible name to contain the text presented in a control’s visible label.
Additional name text can be appropriate; unrelated replacement wording can prevent voice users from matching the visible control.
Understanding Success Criterion 2.5.3: Label in Name · Success criterion and speech-input explanation.
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details