WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard menu accessARIA

for

From: Ryan E. Benson
Date: Jul 5, 2012 7:12PM

Hi Joe

> is there a danger of some users, who are familiar with the tabenter paradigm of keyboard
> accessibility on the web, perhaps not realising that the arrow keys can be used?

As somebody who has been nearly keyboard-only for 15+ years, it comes
down to two things: knowledge and UI. Obviously you have no control on
how much knowledge a user has, however you can dictate what the UI
does. The key point is controlling focus. If I tab to a nav menu, I
expect to hit a sub menu or the second main link. If neither happens,
I decide how important it is to me to get the menu. If it is, I will
try arrows, and other things. If you clearly define focus, I can tell
I am on the second menu item, in the content/somewhere else, or still
in your /lovely/ menu system (and the JS doesn't recognize focus) and
I have to use the mouse or watch the status bar and hope that you have
pretty URLs.

--
Ryan E. Benson


On Tue, Jul 3, 2012 at 4:13 AM, Joe Chidzik
< <EMAIL REMOVED> > wrote:
> I appreciate the value of using ARIA to make drop down menus more naturally accessible by accepting arrow key navigation. This can reduce the amount of keystrokes required, and typically more closely matches standard desktop application behaviour.
>
> A good example is the main menu on the IBM site: http://www.ibm.com/us/en/
>
> You can tab to the first item, then arrow leftright to select, and enter to expand the menu. Similar, one within the expanded menu, you can tab between menus, and arrow updown within the menus.
>
> (As an aside, within JAWS, the main menu is announced as "toolbar", and the sub menus announced as "menu". Using NVDA, the main menu items are just announced "button" with the submenu items announced as "link"; a shortcoming in NVDA, imho, but I assume it will be fixed. Though my question is about keyboard accessibility for sighted users.)
>
> Whilst this ARIA based approach is more accessible as keyboard users don't need to tab through every item, they can instead quickly arrow to the required menu link, is there a danger of some users, who are familiar with the tabenter paradigm of keyboard accessibility on the web, perhaps not realising that the arrow keys can be used? Or is it safe to assume that users will be familiar with this approach, which is similar to Windows (and I assume Mac and other platform) applications, where keyboard access is granted by tabenter and arrow key presses?
>
> I've typically recommended that site's put something on their accessibility page telling keyboard users how to access the site e.g. use arrow keys to switch between items, and enter to expand.
>
> I'm using the IBM site as an example here. I've found it well done generally, but have seen other sites using ARIA in a less well implemented way, where it might be less obvious that you need to use a combination of arrow keystabenter to get around.
>
> Would be interested in other's opinions on this.
>
> Kind regards
> Joe
> > >