- From: Patrick H. Lauke <plauke@paciellogroup.com>
- Date: Thu, 06 Feb 2014 15:58:56 +0000
- To: public-pfwg-comments@w3.org
- CC: Michael Cooper <cooper@w3.org>, wai-xtech@w3.org
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 15:59:20 UTC