Video element exposes unnamed graphic and button
Categories
(Toolkit :: Video/Audio Controls, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox98 | --- | verified |
People
(Reporter: scottaohara, Assigned: lefevren, Mentored)
Details
(Keywords: access, Whiteboard: [lang=html][lang=js])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Firefox's implementation of the video element exposes an unnamed graphic (used to render the poster image, regardless if one is specified or not) and an unnamed button (initial CTA play button rendered atop the video).
CodePen of various video elements
https://codepen.io/scottohara/full/bGWRMBj
Using Firefox with VoiceOver on macOS, navigate using the VO cursor (VO key + right arrow) through the video elements in the test page provided.
Or, if on a PC, use a screen reader of your choice and navigate the test page. NOTE: based on your screen reader's settings, the unnamed image may be ignored by the screen reader.
Actual results:
When navigating through the video elements, VoiceOver will encounter the unnamed image in each video element instance.
Navigating to each initial large "Play" button that is rendered atop the video instance will be announced without an accessible name (VoiceOver), or will be announced as "unlabeled zero button" (with JAWS 2021).
Expected results:
Since there is presently no way to specify alternative text for a poster graphic, this graphic should be hidden from the accessibility tree.
Regarding the unnamed button, provide it an accessible name of "Play", as has been done with the Play button that is part of the video players control toolbar.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Changing severity to S3 because while this is a sub-par screenreader experience, the lack of labelling doesn't actually block any critical functionality.
Comment 3•4 years ago
|
||
Hello! I'd like to tackle this issue. I'm currently setting up my firefox build now.
Comment 5•4 years ago
|
||
(In reply to secret.okra-0z from comment #4)
Is this bug open? I am interested
Yes this one is available. I'll assign it to you :)
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Thank you!! I'll be working on getting familiar with the build environment and bugs over the weekend :)
Comment 7•4 years ago
|
||
(In reply to secret.okra-0z from comment #6)
Thank you!! I'll be working on getting familiar with the build environment and bugs over the weekend :)
Hi Sadie! Are you still able to work on this?
Updated•4 years ago
|
Comment 8•4 years ago
|
||
Unassigning this issue in case someone wants to pick this up.
Updated•4 years ago
|
Hi there this is Kumar Kalyan I am new to this community; can anyone help me out by letting me know about how can I get started with this bug ?
(Reach me out ) https://linktr.ee/kumarkalyan
Updated•4 years ago
|
| Assignee | ||
Comment 10•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Comment 12•4 years ago
|
||
| bugherder | ||
Updated•4 years ago
|
Reproducible on Firefox 91(20210804193234) on macOS Big Sur 11. This issue is fixed on the Firefox 98.0b4(20220213185901) and latest Nightly 99.0a1(20220213214259) on the same OS.
Updated•2 years ago
|
Description
•