Checklist
Let voice commands use the label people can see
The screen says Save. The hidden name should not insist on Commit artifact.
When it fits
- A visible button name does not work as expected with speech input.
When to avoid it
- This does not mean every accessible name must be identical to its visible label. Repeated controls may need additional distinguishing context.
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?
Why it matters
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.
An example
A visible Start recording control no longer has the unrelated accessible name Begin audio capture workflow.
Check your result
Does the tested voice command match the visible control without requiring knowledge of hidden wording?
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.
Connected ideas
Useful withKeep the field’s identity after the user starts typing
Evidence and sources
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.