W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

Re: Better focus support for Shadow DOM

From: 河内 隆仁 <kochi@google.com>
Date: Thu, 26 Feb 2015 15:17:40 +0900
Message-ID: <CADP2=hph1YZNajm+Tjq34dVD2EvAqfWLV0kAX5EEMJ8WiPp21A@mail.gmail.com>
To: Chaals from Yandex <chaals@yandex-team.ru>
Cc: public-webapps <public-webapps@w3.org>
Hi Chaals,

Thanks for the comment.
Honestly I'm not so familiar with ARIA/a11y requirements but the problem
sounds to apply Shadow DOMs overall,
not specific to the problem I'm trying to address here.  Do you have any
concrete cases that this (isTabStop feature et al.)
can regress or degenerate (or improve?) any a11y?

For issue 27965, I commented on it with an example.


On Thu, Feb 19, 2015 at 7:45 PM, <chaals@yandex-team.ru> wrote:

> 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
>
>



-- 
Takayoshi Kochi
Received on Thursday, 26 February 2015 06:18:28 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC