If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Can't set a tabindex to a video or audio element

NEW
Unassigned

Status

()

Toolkit
Video/Audio Controls
8 years ago
8 years ago

People

(Reporter: Yves Van Goethem, Unassigned)

Tracking

({access, html5})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: video, audio, tabindex, keyboard, URL)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier: 

Setting a custom value for the tabindex attribute on video and audio elements isn't possible without JavaScript.

Reproducible: Always

Steps to Reproduce:
1. Go to the attached URL
2. Hit the TAB key to focus a video element
3. The last element will get focus, since the tabindex was set in JavaScript
4. Than the cursor goes back to the first present focusable element of the page.
Actual Results:  
The browser adds tabindex="0" to any video or audio element and overrides the value of the attribute if any else was present.

Setting a tabindex attribute is still possible in JavaScript.

Expected Results:  
The browser shouldn't override the defined value of a tabindex.

This looks like a quick-fix to make video keyboard accessible, because removing tabindex from video and audio elements with JavaScript makes them unreachable by the keyboard.
The HTML5 draft defines video and audio as "Interactive Content" and must therefore be keyboard accessible : http://www.w3.org/TR/html5/embedded-content-0.html#interactive-content
(Reporter)

Updated

8 years ago
Keywords: access, html5
Whiteboard: video, audio, tabindex, keyboard
Version: unspecified → 1.9.1 Branch
Yeah, there's some discussion in bug 486899 and bug 494175 comment 23, just as well to have a specific bug on this.

We could wallpaper over this specific problem by only setting tabindex when there is no currently specified tabindex (we unconditionally set it to 0 right now), but fixing this the right way (per above bugs) would be best...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component: Video/Audio → Video/Audio Controls
Product: Core → Toolkit
QA Contact: video.audio → video.audio
Version: 1.9.1 Branch → unspecified
You need to log in before you can comment on or make changes to this bug.