WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Question about CSS Hover Dropdown menus

for

From: indamockwood-l@verizon.net
Date: Feb 22, 2007 7:50AM

I'm not actually designing a specific site.

I'm trying to put together a list of design elements that are popular, but that have accessibility implications, and specifying just what those implications are. Call it a pre-emptive strike, if you will.

I already know that long, large, drop down menus have accessibility implications because they may be overwhelming. I just also wanted to know if they had any other implications, such as not being entirely accessible to those who surf the web only using keystrokes, or those using screenreaders (because they have to go through all the lists).

MJ

From: Joshue O Connor < <EMAIL REMOVED> >
Date: 2007/02/22 Thu AM 05:38:02 CST
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Question about CSS Hover Dropdown menus

>Christian said:
> multi level menus are generally more a
> problem of information architecture and overloading the user with
> options than a technology issue.

I'll second that. Do you really need them? If you think you do it might
be a good idea to go back to the drawing board and try and simplify your
information architecture.

IMHO, of course.

Josh


********************************************************************

NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.

NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI


********************************************************************