New issue
Advanced search Search tips
Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

<audio> range input incorrectly exposed in acc layer

Project Member Reported by faulkner...@gmail.com, Aug 18 2017

Issue description

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

What steps will reproduce the problem?
(1) go to https://thepaciellogroup.github.io/AT-browser-tests/test-files/audio.html
(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



 
Note also the current accessible name "media control" is not useful in explaining the controls function; it controls the volume.
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

Hello,

I am able to reproduce this using this Chrome Accessibility Experiment to inspect the elements in Chrome canary: https://gist.github.com/marcysutton/0a42f815878c159517a55e6652e3b23a

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

same issue in <video> element controls
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.  

Sign in to add a comment