Hi Takayoshi,
 
14.01.2015, 13:04, "Takayoshi Kochi (河内 隆仁)" <kochi@google.com>:
I was not aware that positive tabindex value is being deprecated, but anyway it should make sense
when tabindex=0 specified on the shadow host. And as it has not been completely deprecated,
it should be okay to keep the document as is, but I will add some comments or pointer.
 
Yep. It was more "for your information".
 
 
For aria-activedescendant, I was not aware either, do you think it still make sense when the
real active descendant is in a shadow tree (i.e. the host and the active element live in different scope)?
(added public-html-a11y to cc)
 
Yes, because I think as far as possible it makes sense to align the models we use for managing focus in different places. (It may be that the right answer is to look at changing ARIA - but having two different models for fairly similar things seems like a bad idea to me).
 
cheers
 
 
 
On Wed, Jan 14, 2015 at 6:28 PM, <chaals@yandex-team.ru> wrote:
Hi,
 
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
 
cheers
 
Chaals
 
14.01.2015, 08:30, "Takayoshi Kochi (河内 隆仁)" <kochi@google.com>:
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
 
 
--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
 


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