Hi,
 
I noted the bugs, this thread, and the document in the HTML accessibility wiki where I am trying to collate stuff about focus navigation and similar keyboard access issues (in what might yet be a vain attempt to really improve the situation which is overall pretty dismal still): https://www.w3.org/WAI/PF/HTML/wiki/Keyboard
 
19.02.2015, 04:56, "Takayoshi Kochi (河内 隆仁)" <kochi@google.com>:
[Shadow]: Shadow host with tabindex=-1, all descendent tree should be ignored for tab navigation
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27965
 
 
I am not sure if this really is a problem (which might just be my brain going slowly). See my comment for more details, but it isn't clear to me that this needs to be fixed. On further reflection, I wonder if the point is where the author has explicitly marked tabindex="-1" - and how this relates to comound ARIA controls...
 
 
cheers
 
Focus on shadow host should slide to its inner focusable node
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28054

On Wed, Jan 14, 2015 at 2:27 PM, Takayoshi Kochi (河内 隆仁) <kochi@google.com> wrote:
Hi,
 
For shadow DOMs which has multiple focusable fields under the host,
the current behavior of tab navigation order gets somewhat weird
when you want to specify tabindex explicitly.
 
This is the doc to introduce a new attribute "delegatesFocus" to resolve the issue.
https://docs.google.com/document/d/1k93Ez6yNSyWQDtGjdJJqTBPmljk9l2WS3JTe5OHHB50/edit?usp=sharing
 
Any comments are welcome!
--
Takayoshi Kochi


 
--
Takayoshi Kochi
 
 
--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com