WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Inaccessible mega menu and WCAG2

for

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

Thanks Patrick. The suggested solution isn't an issue for me, but
they're more likely to fix it if they know it fails WCAG2. To me it
doesn't fit comfortably in 2.1.1, but I guess it's the best there is,
so thanks for that.

As regards the double menu link/button, I think it might cause more
confusion than it resolves. I think perhaps the accessibility
community needs to agree on the paradigm that is the best compromise,
settle on it, and start using it out there in the wild.

If we're afraid keyboard users won't know the shortcuts to use a menu
system, how do we deal with that? By adding info to the accessibility
page?

More questions than answers here :-)

Best, Lynn

On 16/01/2015, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 16/01/2015 16:09, Lynn Holdsworth wrote:
>> 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.
>
> I'd either still mark it as a (mild) failure of 2.1.1, or a pass - but
> in both cases I'd clarify that something needs to be done. Either remove
> the menu and its containing links completely from the focus cycle (using
> display:none instead of whatever off-screen hiding method they're
> presumably using), or make it work and show up for keyboard users.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > >