E-mail List Archives
Re: ARIA tabs interaction
From: Detlev Fischer
Date: Apr 28, 2016 10:13AM
- Next message: Bryan Garaventa: "Re: ARIA tabs interaction"
- Previous message: Jordan Wilson: "On demand asset accessibility"
- Next message in Thread: Bryan Garaventa: "Re: ARIA tabs interaction"
- Previous message in Thread: Joseph Sherman: "ARIA tabs interaction"
- View all messages in this Thread
The best practice (to use arrow keys within tab lists for focuusing tabs) has always be conceptually difficult as there is no clear conceptual separation of tabbed navigation areas where you expect tabbing to work, and tab-panel like structures where (accorfding to ARIA best practices) arrow keys should be used. That is why many developers chose to support tabbing to tabs nad you find very different implementations with variants regarding the use of ARIA. For menus proper, i.e. the Menubar widget that really implement an application pulldowen menu like https://hanshillen.github.io/jqtest/#goto_menubar the situation is different.
So to answer the question, I personally don't see it as wrong to allow the user to tab through the top-level menu items, certainly niot for navigation menus, and I I see definite usability advantages of supporting both arrowing and tabbing for tabs in tab panels even if this deviates from ARIA best practice.
testkreis c/o feld.wald.wiese
Thedestr. 2, 22767 Hamburg
Mobil +49 (0)157 57 57 57 45
Fax +49 (0)40 439 10 68-5
Beratung, Tests und Schulungen fÃ¼r barrierefreie Websites
Joseph Sherman schrieb am 28.04.2016 16:29:
> The design guide for ARIA menu tabs uses the "Tab" key to get into the tabs
> list, and then the arrow keys to move through the menu tabs and menu items. In
> my experience users, especially without a screen reader, expect the "Tab" key
> to move to the next menu Tab and are confused when the "Tab" key skips the menu
> tabs. Is it "wrong" to follow the guide but allow the user to tab through the
> top-level menu items?
> > > > >