- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Dec 2013 05:27:18 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24106 Bug ID: 24106 Summary: FKA: No defined way to get keyboard focus into and out of a shadow DOM component Product: WHATWG Version: unspecified Hardware: PC OS: All Status: NEW Keywords: a11y, a11ytf Severity: normal Priority: P2 Component: HTML Assignee: ian@hixie.ch Reporter: silviapfeiffer1@gmail.com QA Contact: contributor@whatwg.org CC: dglazkov@chromium.org, faulkner.steve@gmail.com, hayato@chromium.org, jcraig@apple.com, mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org, tink@tink.co.uk Depends on: 23870 +++ This bug was initially created as a clone of Bug #23870 +++ FKA (full keyboard access): There is currently no defined way to get keyboard focus into and out of a shadow DOM component. Some components (like the native "number" input type) don't need this, but others (like native video controls) need multiple tab stops inside the shadow DOM component. For example: <input type="number"> Although there are multiple focusable elements inside (textfield, increment button, and decrement button), all features can be controlled with standard keyboard behavior. Focus stops on the input, and the increment/decrement buttons are activate with up/down arrows. <video controls> There are multiple controls in the shadow DOM component, including volume/mute buttons/sliders, a playback position slider, a cc toggle button and subtitle picker menu, etc. There is currently no consistent way to control HTML 5 media elements without using a mouse. I suggest that the specs provide a way for a web component to declare whether it has a focusable sub-DOM, which should be the default for <video> and <audio> sub-DOMs, and probably some input types like date and color. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 16 December 2013 05:27:20 UTC