please consider how thi relates to the management of "aria-active-descendant" and why we should not be working to bring the two of these in line.
Note also that in HTML there is a proposal to deprecate (and hopefully one day abandon) tabindex with positive values, in favour of something less painful than forcing the user to press tab a zillion times as the way to get around an app. The HTML accessibility task force is currently looking at these issues for HTML, and it would be good to align the work.
There is a question of where it makes more sense to have the conversation, but for the moment it is on public-html-a11y@w3.org and on their wiki - listed as accesskey for increasingly irrelevant historical reasons http://www.w3.org/WAI/PF/HTML/wiki/51wishlist
14.01.2015, 08:30, "Takayoshi Kochi (河内 隆仁)" <kochi@google.com>:
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.
Any comments are welcome!
Takayoshi Kochi
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com