Slides from WDCNZ 2013

Slides from my WDCNZ 2013 presentation, "Make your widgets sing with ARIA":

Note: The presentation was about screen reader and keyboard support for ARIA widgets, so I didn't bother scripting mouse support for the custom slider widget, which will only work with a keyboard.

2 Responses to Slides from WDCNZ 2013

  1. 1. Ash:

    On slide 33 you have specified tabindex="-1" for the two hidden tabs – doesn’t this mean those tabs will never be accessed by tabbing using a keyboard?

  2. 2. Jason:

    Hi Ash,

    The recommended keyboard interaction pattern for tabs is to only have the currently selected tab control in the TAB order, so it gets tabindex="0" and the others get tabindex="-1". This gets dynamically updated when one selects another tab control using the arrow keys, as do the relevant aria-* attributes.

    You can read more at http://www.w3.org/WAI/PF/aria-practices/20091214/#tabpanel

    Also see http://accessibleculture.org/articles/2010/08/aria-tabs/

    Some folks prefer a pattern where all tab controls are in the TAB order and pressing Space or Enter activates it. I decided to stick with the pattern recommended in the ARIA Authoring Practices document.

Comments are now closed.