Freelock’s Day 22 Advent Calendar Entry Highlights “Label in Name” for Voice Accessibility

The post explains how mismatched visual and accessible labels break navigation for users relying on voice commands. A button that displays “Submit” but uses an aria-label like “Submit this form now” may seem helpful but prevents users from activating it by saying “Click Submit.” This issue affects people with motor disabilities, temporary injuries, or those multitasking using tools like Apple Voice Control, Dragon NaturallySpeaking, or Windows Voice Access.

Common pitfalls include replacing visible text with overly descriptive ARIA labels, using mismatched alt text for images, or creating icon-only buttons without proper labeling. Freelock advises that accessible names must either exactly match or start with the visible label. For added context, developers are encouraged to use aria-describedby instead of overwriting visible text with aria-label.

The blog offers specific guidance for testing compliance using voice control software or browser accessibility inspectors. It warns that modern frameworks and third-party plugins often introduce these issues, particularly in modal dialogs, sliders, or icon libraries. Freelock underscores that predictable, visible labeling supports both usability and trust—allowing users to activate elements simply by saying what they see.