Voice Control Accessibility: Dragon, Apple Voice Control & WCAG Label-in-Name

Millions of users with motor disabilities (including quadriplegia, cerebral palsy, Parkinson's disease, and repetitive strain injury) operate computers entirely through speech recognition software such as Dragon NaturallySpeaking, Apple Voice Control, and Windows Voice Access. When on-screen visual button text disagrees with underlying code attributes, voice users are rendered completely unable to activate interactive controls.

How Speech Input and Voice Control Software Works

When a voice control user sees a button labeled "Submit Application", they simply speak the command: "Click Submit Application". The speech software scans the accessibility tree for interactive elements whose programmatic accessible name matches the spoken words.

WCAG 2.5.3 (Label in Name) Explained

Under WCAG 2.5.3 (Label in Name - Level AA), for any interactive component that includes visual text, the programmatic accessible name (accessible name) must contain the exact words presented visually. Ideally, the accessible name should begin with the visual text string.

Top Voice Navigation Traps

Compliant vs Non-Compliant Button Markup

<!-- ❌ BROKEN: Visual text 'Sign In' is overridden by aria-label -->
<button type="button" aria-label="Customer Login Portal">
  Sign In
</button>

<!-- ✅ COMPLIANT: aria-label contains visual text at the start -->
<button type="button" aria-label="Sign In to Customer Portal">
  Sign In
</button>

<!-- ✅ BEST PRACTICE: No aria-label needed; native text is ideal -->
<button type="button" class="btn-primary">
  Sign In
</button>

Testing with Apple Voice Control and Windows Voice Access

Enable Apple Voice Control (macOS Settings > Accessibility > Voice Control) and command the browser: "Click Pricing", "Click Free Audit". If the browser fails to click the target button, your codebase violates WCAG 2.5.3.