Closed
Bug 1496850
Opened 6 years ago
Closed 6 years ago
Volume slider in HTML5 audio player is verbalized as generic "slider" and not "volume slider" in NVDA.
Categories
(Toolkit :: Video/Audio Controls, defect, P3)
Tracking
()
VERIFIED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | verified |
People
(Reporter: charleyroy, Assigned: Gijs)
References
Details
(Keywords: access)
Attachments
(1 file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
Steps to reproduce:
Pre-step: Enable NVDA screen reader.
Step 1: Go to http://jsfiddle.net/sqdkxy4z/ (or set up a native HTML5 audio with controls)
Step 2: Click / focus on the volume player.
Actual results:
The verbalization just reads "slider".
Expected results:
The verbalization should give an indication that this is some kind of volume slider.
Assignee | ||
Comment 1•6 years ago
|
||
Does NVDA read the state (value) of the slider if it is manipulated? That is, is this just a question of putting an aria-label (accessible name) on the slider, or do we need to also provide information about the volume state ourselves?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(charleyroy)
Priority: -- → P3
Reporter | ||
Comment 2•6 years ago
|
||
I believe adding an aria-label to the slider to make it clear that this is controlling volume would solve the issue.
Flags: needinfo?(charleyroy)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•6 years ago
|
||
Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/ba07c543cc93
add label to volume slider, r=MarcoZ
Comment 5•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•6 years ago
|
Flags: qe-verify+
Comment 6•6 years ago
|
||
I reproduced this issue on Windows 10 with Fx 64.0a1 (20181005220146).
The issue is fixed on Fx 64.0b3 (20181022150107) on Windows 10 x64, macOS 10.13 and Ubuntu 18.04 x64.
You need to log in
before you can comment on or make changes to this bug.
Description
•