Keyboard accessibility: changing tab order

Michael S Elledge elledge at msu.edu
Wed Jan 27 18:24:01 UTC 2010


To follow on Armin's comment, you will also have more flexibility in 
page design by positioning and presenting content using CSS; that way 
your code order is optimized while your page appearance is flexible.

Mike

Armin Krauss wrote:
> Thanks Everett for helping me out here. I did not think of this and I 
> am happy you brought it up.
>
> Boyan, does this help you in any way?
>
> Armin
>
>
>
> On Wed, Jan 27, 2010 at 12:22, E.J. Zufelt <everett at zufelt.ca 
> <mailto:everett at zufelt.ca>> wrote:
>
>     Good morning,
>
>     I would add to this that it is not ideal to try to add
>     focusability to an element that does not natively support focus.
>
>     HTH,
>     Everett
>
>     Follow me on Twitter
>     http://twitter.com/ezufelt
>
>     View my LinkedIn Profile
>     http://www.linkedin.com/in/ezufelt
>
>
>
>
>     On 27-Jan-10, at 11:55 AM, Armin Krauss wrote:
>
>>     Hi Boyan,
>>
>>     the best way to have a tab order and comply with WCAG easily is
>>     to have the content in a order that needs no tab order. This
>>     means that the content is structured and sorted in the way the
>>     tab order should flow. Then you don't need to override the tab
>>     order. As a byproduct the content has a structure that makes for
>>     an user with AT more sense.
>>
>>     See 1.3.2 and 2.1.1 among others on
>>     http://webaim.org/standards/wcag/checklist
>>
>>     Hope that helps a bit.
>>
>>     Armin
>>
>>     --
>>
>>
>>
>>     On Wed, Jan 27, 2010 at 07:12, Boyan Sheytanov
>>     <boyan.sheytanov at asteasolutions.com
>>     <mailto:boyan.sheytanov at asteasolutions.com>> wrote:
>>
>>         Hi all!
>>
>>         I was trying to force the following tab order of the elements
>>         in Capture for Decapod: thumbnail item, take picture button,
>>         fix, compare, export. Since the buttons are <a> elements,
>>         they were easily ordered (having assigned them positive
>>         values for 'tabindex'). However, they do not seem to respond
>>         to pressing the Enter key. Additionally, the thumbnail item
>>         is a <li> element and the only valid values for the tabindex
>>         property are -1 or 0 (correct me if I am wrong here). These
>>         make the element focusable or part of the default tab order
>>         but I cannot find a way to make it the first element of the
>>         tab order.
>>
>>         My question is what is the 'proper' way to modify tab order
>>         and enable keyboard navigation in accessible web applications.
>>
>>         Greetings,
>>
>>         Boyan
>>
>>         _______________________________________________________
>>         fluid-work mailing list - fluid-work at fluidproject.org
>>         <mailto:fluid-work at fluidproject.org>
>>         To unsubscribe, change settings or access archives,
>>         see http://fluidproject.org/mailman/listinfo/fluid-work
>>
>>
>>     _______________________________________________________
>>     fluid-work mailing list - fluid-work at fluidproject.org
>>     <mailto:fluid-work at fluidproject.org>
>>     To unsubscribe, change settings or access archives,
>>     see http://fluidproject.org/mailman/listinfo/fluid-work
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>   



More information about the fluid-work mailing list