WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible Superfish-like drop-down menus?

for

From: L Snider
Date: Jun 6, 2017 4:22PM

Hi Jeremy,

Yes, I would agree with the menu bar approach. As I said these were ones I
used to use, some people use them, others don't...just depends on what you
want to do. At the time, they were better than suckerfish menus, but I am
not sure of suckerfish today (they may be way better).

Cheers

Lisa

On Tue, Jun 6, 2017 at 5:04 PM, Jeremy Echols < <EMAIL REMOVED> > wrote:

> Really? Example 1 seems like almost exactly what we use our site
> navigation to accomplish.
>
> As a keyboard user, I find the menu bar approach much nicer than the more
> typical tabbing through piles of links. One tab into the menu, one tab
> out, arrows to navigate within the menu.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Lucy Greco
> Sent: Tuesday, June 06, 2017 2:21 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Accessible Superfish-like drop-down menus?
>
> that example from w3c is for a menu bar not a site menu menu bars should
> only be used in apps and site menus are not menubars
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration University of California,
> Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> On Tue, Jun 6, 2017 at 12:40 PM, Ritz, Courtney L. (GSFC-7200) <
> <EMAIL REMOVED> > wrote:
>
> > Hi,
> >
> > I think we're going to be stuck with Superfish for the time being,
> > since we're in a bit of a time crunch.
> > But I'm going to push for us to look at other more accessible options
> > for future use.
> >
> > Courtney
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Jeremy Echols
> > Sent: Tuesday, June 06, 2017 3:35 PM
> > To: WebAIM Discussion List < <EMAIL REMOVED> >
> > Subject: Re: [WebAIM] Accessible Superfish-like drop-down menus?
> >
> > W3C has an example for a supposedly screen-reader-friendly menu
> > implementation: http://w3c.github.io/aria-practices/examples/menubar/
> > menubar-1/menubar-1.html
> >
> > I have no idea how well that would fit in Drupal. I'm going to be
> > trying to make something like this work shortly for our own site, but
> > it's going to be very experimental and probably very specific to our
> > needs, as Drupal isn't something I deal with very often. And there's
> > every chance I'll fail anyway :)
> >
> > If that menubar isn't a good example, though, I'd love to know before
> > I get started.
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Ritz, Courtney L. (GSFC-7200)
> > Sent: Tuesday, June 06, 2017 9:31 AM
> > To: WebAIM Discussion List < <EMAIL REMOVED> >
> > Subject: Re: [WebAIM] Accessible Superfish-like drop-down menus?
> >
> > Ah, thanks for clarifying this for me.
> > I'll take a look at that and have our developers do the same.
> >
> > Courtney
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Lucy Greco
> > Sent: Tuesday, June 06, 2017 12:29 PM
> > To: WebAIM Discussion List < <EMAIL REMOVED> >
> > Subject: Re: [WebAIM] Accessible Superfish-like drop-down menus?
> >
> > hello: this is normal behavior for a simple menu in Druple. what is
> > going on is as you tab to the menu link the menu is opening and then
> > you can tab thru the items of the menu. however if your going
> > backwards the menu is closed until you tab to it and then you keep
> going backwards over
> > the menu item itself but not the contents because the contents of the
> > menu are hidden until you tab to the menu itself. we have added some
> > ARIA to make this more understandable to a screen reader and the
> > ability to close the menu if you don't want to tab thru it take a look
> > at open.Berkeley.edu <http://open.berkeley.edu>; for an example of how
> > it works. you might also want to take a look at webaccess.berkeley.edu
> > to see an example of a menu that does not activate until you want it to.
> > hint don't tab thru to quickly stay on the links long enough to here
> > the aria we have added to tell you what is going on. we let you know
> > that you can open the menu but we also let you know that once your out
> > of the sub menu that the menu has closed behind you.
> >
> >
> > Lucia Greco
> > Web Accessibility Evangelist
> > IST - Architecture, Platforms, and Integration University of
> > California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> > On Tue, Jun 6, 2017 at 9:00 AM, Ritz, Courtney L. (GSFC-7200) <
> > <EMAIL REMOVED> > wrote:
> >
> > > Hi all,
> > >
> > > I tried a quick search in the archives and I didn't see anything too
> > > current on this, so apologies if I've missed something.
> > >
> > > Our developers have put some drop-down menus onto some sites in our
> > > Druple environment.
> > > As a JAWS user in IE or Firefox, I run into an annoying situation as
> > > I Tab through the link in these menus. If I Tab forward through
> > > them, I hear each links in the submenu, and then whatever links come
> > > after that submenu. However, if I start reverse-Tabbing back
> > > through the links, I end up completely skipping the submenu links.
> > >
> > > The first menu they tried was called a Nice Menu I think. They
> > > switched to Superfish, since it's supposed to be 508 compliant from
> > > what
> > they read.
> > > I'm still having this problem.
> > >
> > > So, I guess my question is, is this just standard behavior for an
> > > accessible drop-down menu that I just don't happen to like, or is
> > > this a problem that can be fixed by tweaking the menu or trying
> > > another
> > solution?
> > >
> > > Thanks for any suggestions you may have.
> > >
> > > Courtney
> > > > > > > > > archives at http://webaim.org/discussion/archives
> > > > > >
> > > > > > archives at http://webaim.org/discussion/archives
> > > > > > > > archives at http://webaim.org/discussion/archives
> > > > > > > > archives at http://webaim.org/discussion/archives
> > > > > > > > archives at http://webaim.org/discussion/archives
> > > >
> > > at http://webaim.org/discussion/archives
> > > > > >