New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Dec 17
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment

Issue 756837: <audio> range input incorrectly exposed in acc layer

Reported by, Aug 18 2017 Project Member

Issue description

Chrome Version: 60.0.3112.101
OS: (e.g. Win10)

What steps will reproduce the problem?
(1) go to
(2) Check the range input for volume using an object inspection tool

What is the expected result?
exposed as role= slider in MSAA/Ia2

What happens instead?
exposed as role=client in MSAA/Ia2

Comment 1 by, Aug 18 2017

Note also the current accessible name "media control" is not useful in explaining the controls function; it controls the volume.

Comment 2 by, Sep 8 2017

Status: Available (was: Untriaged)
Chrome 63.0.3208.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 10.0.14393 Build 14393


I am able to reproduce this using this Chrome Accessibility Experiment to inspect the elements in Chrome canary:

The element is shown as "Unknown" in Windows, aka "client".

Comment 3 by, Dec 8 2017

same issue in <video> element controls

Comment 4 by, Dec 14 2017

Labels: win-a11y
The user impact here is that the volume on a media player is not recognized properly by the screen reader because it is not treated as a slider.

Comment 5 by, Dec 14

Project Member
Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit - Your friendly Sheriffbot

Comment 6 by, Dec 17

Status: Fixed (was: Untriaged)
Just tested in Chrome 70 and this is now exposed as a slider. Works with NVDA. Not sure when it was fixed.

Sign in to add a comment