I agree - a media element with controls ought to be keyboard-accessible by
default. Right now it doesn't appear that you can even make an audio or
video element play in WebKit even if it is focused.
Firefox seems to treat the whole set of controls as one focusable element -
you can use the
On Tue, Sep 13, 2011 at 12:04 PM, Deepak Sherveghar bpw...@motorola.comwrote:
As with current Webkit behavior, only media elements with tab-index
attribute specified can be focused with keyboard (TAB key).
From a usability as well as accessibility perspective, we should be able to
focus (via
On Wed, Sep 14, 2011 at 7:30 AM, Dominic Mazzoni dmazz...@google.comwrote:
An alternative approach would be to make each individual subcontrol
focusable - the play/pause button, the seek slider, and the volume slider,
plus potentially other controls for video.
What would script see as
What would script see as focused if we allow subcontrols be focusable?
Since controls are part of shadow DOM, scripts wont be able to see
that. In this case then they would probably end up with respective
media element.
Well, then that should be layout tested as well.
--
--Antonio Gomes
On 9/14/11 2:02 PM, Antonio Gomes wrote:
What would script see as focused if we allow subcontrols be
focusable?
Since controls are part of shadow DOM, scripts wont be able to see
that. In this case then they would probably end up with respective
media element.
Well, then
Hi All,
As with current Webkit behavior, only media elements with tab-index
attribute specified can be focused with keyboard (TAB key).
From a usability as well as accessibility perspective, we should be able to
focus (via keyboard using TAB key)
media elements that have controls attribute
6 matches
Mail list logo
