WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Inaccessible mega menu and WCAG2

for

From: Lynn Holdsworth
Date: Jan 16, 2015 9:09AM

Apologies - I lied :-)

It *is* possible to get to a new page using the top menu links. And
the new page contains all of the submenu items.

But it's still confusing for keyboard users to be tabbing through a
bunch of invisible links. So presumably 2.1.1 isn't pertinent here.
But focus visible doesn't feel like quite the right fit.

Any thoughts on this?

Thanks, Lynn

On 16/01/2015, Lynn Holdsworth < <EMAIL REMOVED> > wrote:
> Thanks everyone.
>
> No, it's not possible to open the menu or get to a different
> destination by activating one of the links in the top menu.
>
> 2.1.1 looks like a good point to fail it on - thanks Patrick.
>
> I worked on a menu system for a while, and it functioned pretty much
> exactly like native menus: left/right arrows move across the top or
> open/close sub-submenus; down arrow opens a submenu or moves through
> its options; Esc closes a submenu, etc., and I liked it a lot. But it
> wasn't possible to create an implementation that worked across all
> screenreaders. And we were never sure whether we should indicate that
> an item could be expanded if pressing Enter moved the user to a
> different page. So I'm very interested in this discussion and what you
> all think.
>
> Best, Lynn
>
> On 16/01/2015, Don Mauck < <EMAIL REMOVED> > wrote:
>> I'd like to give my two cents for what it's worth. For me, I like the
>> way
>> menus and submenus currently work as it is the way most application menus
>> work.
>>
>>