WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible Mega Menu and Safari


From: Moore,Michael (Accessibility) (HHSC)
Date: Mar 30, 2016 10:02AM

I thought that the original post concerned different behavior between Safari/VoiceOver vs. windows based screen readers. So the problem becomes how do you provide instructions when what you need to do is different based upon the OS/AT/Browser combination. I could see the instructions becoming very unwieldy very fast. Not to mention that most organizations do not even possess the expertise to manage that level of detail in the instructions. For example we are strictly a Microsoft house and when we are lucky our developers understand how to use JAWS with IE. Macs are confined to our graphic designers who think that AT stands for Artistic Trauma and that VoiceOver is something performed by David Attenborough.

Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Paul J. Adam
Sent: Wednesday, March 30, 2016 10:48 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Accessible Mega Menu and Safari

Looks like it only works if you press the down arrow key with VoiceOver quick navigation turned off. Or Tab into the menu.

It would be smart for JavaScript widgets that have various keyboard navigation methods to display a visible tooltip or show some instructions on how to actually operate the menu. Those instructions being accessible to screen reader users also.

This menu works as you're expecting with VO+Right Arrow key. http://www.washington.edu/accesscomputing/AU/after.html <http://www.washington.edu/accesscomputing/AU/after.html>;

Here's the ARIA Authoring Practices with keyboard interaction instructions, https://www.w3.org/TR/wai-aria-practices/#menu <https://www.w3.org/TR/wai-aria-practices/#menu>

Paul J. Adam
Accessibility Evangelist

> On Mar 30, 2016, at 10:18 AM, Robert Fentress < <EMAIL REMOVED> > wrote:
> Hi, all.
> I've just noticed a problem with the way Adobe's Accessible Mega Menu
> (
> https://adobe-accessibility.github.io/Accessible-Mega-Menu/) works
> with Safari and VoiceOver. Basically, when you activate a menu with
> Control+Option+Space the menu appears, but when you then press Right
> Control+Option+Arrow to have VO voice the text in the menu, the menu
> collapses. It only stays open if you tab into the revealed contents.
> This, of course, kinda defeats one of the points of this pattern, in
> that it means that you really only have access to the menu options,
> not the other structured content. In that case, you might as well
> just make it a more standard menu.
> I could have sworn I'd tested this before and it had worked. Do you
> know if anything has changed in recent updates to Safari or VoiceOver
> that would have affected this, or did I just miss it previously?
> On a related note, if you are stuck with this basic turducken mega
> menu pattern, is there an implementation that works better than
> Adobe's? If I could convince the people I'm making recommendations to
> to deviate slightly from the strict mega menu pattern, would a mega
> modal be better and, if so, do you know of some particularly good implementations?
> Best,
> Rob
> --
> Robert Fentress
> Senior Accessibility Solutions Designer
> 540.231.1255
> Technology-enhanced Learning & Online Strategies Assistive
> Technologies
> 1180 Torgersen Hall
> 620 Drillfield Drive (0434)
> Blacksburg, Virginia 24061
> > > archives at http://webaim.org/discussion/archives