WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: resolving conflict between JAWS and key-press events for navigating large drop-down menus

for

From: Mallory van Achterberg
Date: Aug 25, 2014 8:07AM

I gotta say, I really like that Abode isn't using the whole menu/
menuitem role stuff. Reading the spec, that menu stuff sounds
entirely like an application/widget thingie, not a list of links
like all web navigation menus should be.

But as a sighted keyboarder, discoverablility hits me there.
If I didn't think to try mystery-meating with my arrow keys,
I as a "Typical Web Keyboarder User" would never, ever know
that there were any submenus. If I use tab or the left/right
arrows I move along as expected to the main menu items (sparing
me the Thousand Tabs of Death), and I see if yo *do* magically
happen to try using a top/bottom arrow key, then aria-expanded
and aria-hidden set to "false" should let users know there's an
existing, active, explorable submenu.

On the other hand, the Adobe menu mostly seems awesome as a web
menu, but what Michael describes seems an awful lot like a
complicated government-style menu with a lot of controlly thing...
in which case, I dunno, maybe he should be using the complicated
(and easy to mess up apparently) menu/menuitem role system.

_mallory
On Mon, Aug 25, 2014 at 01:19:00PM +0000, Jonathan Avila wrote:
> Michael, I believe your ARIA roles could be on the wrong elements. Take a look at this mega menu implementation contributed by Adobe. http://adobe-accessibility.github.io/Accessible-Mega-Menu/
>
> Best Regards,
>
> Jonathan
> SSB BART Group
>
>