Chrome's Accessibility Audit API Expands to Include Voice and Gaze Metrics

Tech · 6 min read

The Chromium team announced an expanded Accessibility Audit API that collects anonymized signals for voice-triggered interactions and gaze-based focus changes, feeding new Lighthouse checks designed for hands-free and eye-tracking scenarios. The API does not record raw audio or video; it reports event-level metrics such as "voice command failure rate" and "gaze focus ambiguity" to protect privacy.

For developers this means Lighthouse can now flag patterns like unlabeled voice-only controls, ambiguous focus zones that confuse gaze-based switching, and inconsistent ARIA roles affecting speech recognition. The tooling integrates with DevTools, giving engineers prioritized issues and reproducible repro steps where possible.

Privacy advocates and accessibility specialists have debated the telemetry approach. Chromium’s proposal limits the granularity of telemetry and requires explicit consent in developer tools, but some voices caution that simulated environments and lab tests remain essential because telemetry aggregates may miss edge cases for specific assistive tech setups.

Adoption may accelerate improvements in cross-browser support for voice and gaze APIs, and design systems will likely add components with explicit voice and gaze affordances. Teams should update test matrices and include hands-free scenarios in both automated and manual QA to benefit from the new checks.