# Let voice commands use the label people can see

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Let voice commands use the label people can see

ID: MHC-D-RESEARCH-1106 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/let-voice-commands-use-the-label-people-can-see

The screen says Save. The hidden name should not insist on Commit artifact.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A visible button name does not work as expected with speech input.

### Avoid when

- This does not mean every accessible name must be identical to its visible label. Repeated controls may need additional distinguishing context.

### Explanation

Inspect the control’s accessible name and compare it with its visible label. The name should contain that label’s text so voice users can refer to what they see. Additional useful context may follow; unrelated replacement wording can break the connection.

### Checklist

- Does the accessible name contain the visible label text?
- Has a custom accessibility attribute replaced the ordinary label with different wording?
- Can a speech-input user identify and activate the intended control?

### Example

A visible Start recording control no longer has the unrelated accessible name Begin audio capture workflow.

### Check

Does the tested voice command match the visible control without requiring knowledge of hidden wording?

### Limits

- This does not mean every accessible name must be identical to its visible label. Repeated controls may need additional distinguishing context.

### Evidence and sources

- supports: WCAG 2.5.3 requires the accessible name to contain the text presented in a control’s visible label. — RS-71603CB81AF21C2D. Additional name text can be appropriate; unrelated replacement wording can prevent voice users from matching the visible control. (Success criterion and speech-input explanation.)
- RS-71603CB81AF21C2D: Understanding Success Criterion 2.5.3: Label in Name — https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html

### Vedokrok editorial review

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.

#### 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.

**Editorial takeaway:** 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.

#### Editorial evidence

- supports: 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. — RS-7E7303084DD310BE. 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. (2.5.3 Label in Name, Level A, criterion and note)
- supports: G208 describes including the visible text string intact and in order. — RS-6C3E14DD9FB8E707. 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. (Description; Tests, Procedure 1)
- supports: Inserting a hidden word between the words of a visible label can break the label-to-name match. — RS-D6D6626D1A7300E2. 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. (Example 2; Tests)
- supports: ARIA naming can override native text; aria-describedby contributes a description rather than an accessible name. — RS-71603CB81AF21C2D. 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. (Accessible Name and Description Computation specification)
- limits: 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. — RS-71603CB81AF21C2D. 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. (Intent; Symbolic text characters; Punctuation and capitalization)
- contextualizes: Chrome DevTools exposes computed accessibility properties, while markup inspection does not establish successful assistive-technology navigation. — RS-B01B06F4F3B23F5F. 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. (Overview of accessibility features in Chrome DevTools; The Accessibility tab; View an element’s computed accessibility properties)
- RS-71603CB81AF21C2D: Understanding Success Criterion 2.5.3: Label in Name — https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html
- RS-7E7303084DD310BE: Web Content Accessibility Guidelines (WCAG) 2.2 — https://www.w3.org/TR/2024/REC-WCAG22-20241212/
- RS-6C3E14DD9FB8E707: G208: Including the text of the visible label as part of the accessible name — https://www.w3.org/WAI/WCAG22/Techniques/general/G208
- RS-D6D6626D1A7300E2: F96: Failure due to the accessible name not containing the visible label text — https://www.w3.org/WAI/WCAG22/Techniques/failures/F96
- RS-B01B06F4F3B23F5F: Accessibility features reference — Chrome DevTools — https://developer.chrome.com/docs/devtools/accessibility/reference

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/keep-the-field-s-identity-after-the-user-starts-typing
