WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: ARIA tabs interaction


From: Joseph Sherman
Date: Apr 28, 2016 12:34PM

Right, if the Tab key changes the menu Tabs AND goes through the Tab/menu items that can definitely be a pain to navigate.


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Lucy Greco
Sent: Thursday, April 28, 2016 2:02 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] ARIA tabs interaction

from the user prospective if you let the tab key be used the user may not
know witch tab is selected in the end its key to not use the tab key so
that the user can be sure the last interaction with the tab selection is there choice let me give a sample in the gmail settings tabs let you tab through them. as you tab throu the tab itself is selected. the user finds the settings pannal they want and then they keep tabbing and dam if it does
not chage the selected tab so in this sinarryo the user needs to figure
out how the hell to pick the second tab and then skip over the rest of the tabs and move to the contents of the tab if these were just aero selectable tabs that problem would not happen

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
Follow me on twitter @accessaces

On Thu, Apr 28, 2016 at 10:43 AM, Bryan Garaventa < <EMAIL REMOVED> > wrote:

> The danger of this logic being, if everybody does this differently,
> nobody will ever understand what is expected now or in the future.
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> 415.624.2709 (o)
> www.SSBBartGroup.com
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Detlev Fischer
> Sent: Thursday, April 28, 2016 9:14 AM
> Subject: Re: [WebAIM] ARIA tabs interaction
> 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.
> Detlev
> --
> Detlev Fischer
> 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
> http://www.testkreis.de
> 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?
> >
> >
> > Joseph
> >
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >