- From: Thomas Logan <tlogan@gmail.com>
- Date: Thu, 6 Feb 2014 11:03:25 -0500
- To: "Patrick H. Lauke" <plauke@paciellogroup.com>
- Cc: "public-pfwg-comments@w3.org" <public-pfwg-comments@w3.org>, Michael Cooper <cooper@w3.org>, "wai-xtech@w3.org" <wai-xtech@w3.org>
Hi Patrick, I've encountered this exact same error and agree it should be fixed. It has major implications for component authors. I've seen the text from this document copied and pasted verbatim into accessibility presentations. Thomas Logan > On Feb 6, 2014, at 10:58 AM, "Patrick H. Lauke" <plauke@paciellogroup.com> wrote: > > I tried to comment on this before, but if memory serves I was told that the commenting period was over and it was handwaved...in any case, trying again: there seems to be a tiny error/typo in 3.1.3 Keyboard Navigation within Widgets, and specifically the third step of the "roving" tabindex. http://www.w3.org/WAI/PF/aria-practices/#kbd_general_within > > Currently, the process reads: > > * Set tabindex="0" to the current active descendant in the widget while setting tabindex="-1" on all the other child elements of the widget > * As the user navigates (e.g. arrows) away from an item, the old item gets a tabindex="-1" and the new item gets tabindex="0". > * Use the javascript method to set focus, using its JavaScript focus() method, on the item whose tabindex="-1" > > On that last item, I'd say it should read tabindex="0", NOT tabindex="-1", as we're intending to move the focus to the newly active item (which, in step two, has now been given tabindex="0"). > > P > -- > Patrick H. Lauke > -- > Accessibility consultant > The Paciello Group (UK office) > http://www.paciellogroup.com/ > The Paciello Group. > >
Received on Thursday, 6 February 2014 16:04:04 UTC