[Accessibleweb] RE: Accessible menu system without popup/dropdowns

Marcus Duke mduke at u.washington.edu
Mon Dec 3 07:43:25 PST 2007


Thanks, Jill: One of these days, I'm going to have to clean-up my
hundreds of CSS links, and these two sites nicely condense a lot of
info for which I often have to browse many sites to obtain.

Dylan: Maybe this helps: Primarily, I *do not* want popups. And of
course, I want to separate content from presentation/style, which is
why I was originally thinking CSS (not sure how well Javascript menus
address this, other than perhaps UDM4, and Al Sparber claims his
Project VII menus address various accessibility attributes). I also
do want a "you are here" function.

Both CSS and Javascript can accomplish this. But for a lay/beginner
client, a Javascript package (with a good GUI) may be easier for them
to manage than altering CSS every time a change is needed in the
menus (e.g., beginner might be intimidated by following the method
described atwww.netmechanic.com/news/vol9/css_no1.htm). I use
MenuMachine for GoLive and it's incredibly easy, versatile, and can
produce text-based sitemaps on the fly to help with accessibility
issues. It saves me a lot of time compared with the multi-step
process I have to go through when editing the wsg.washington.edu CSS
menus (built using the technique described in the netmechanic.com
article).

Finally, I lean towards Javascript because of uncertainty about
client turnover frequency.

Sorry 'bout that--too much info, probably.

Marcus Duke
Webmaster/Info Specialist
UW Aquatic & Fishery Sciences

WYSIWYG: What you so intensely wish you got (Web designer's proverb)




> Message: 2

> Date: Fri, 30 Nov 2007 15:22:31 -0800

> From: "Dylan Wilbanks" <wilbanks at u.washington.edu>

> Subject: RE: [Accessibleweb] Accessible menu system without

> popup/dropdowns

> To: "'UW Web Accessibility Group'" <AccessibleWeb at u.washington.edu>

> Message-ID: <002e01c833a7$e188e7e0$6a155f80 at sphcm.washington.edu>

> Content-Type: text/plain; charset="US-ASCII"

>

>> I'm seeking an easier solution than CSS (i.e., javascript) to

>> replace a set of menus, and I'd like it to be politically

>> correct (e.g., http://www.udm4.com).

>>

>> The catch is most programs/options I have found are all for

>> popup/ dropdown submenus. I don't want this; I want all menu

>> levels to be static, other than the "you are here" hint.

>>

>> That may be all you need to read to help, but if you want

>> more info (e.g., context), here ya be:

>>

>> The site in question is http://depts.washington.edu/poeweb.

>>

>> Then, here's an example of a site done for us by UW Creative

>> Services that uses only CSS for the menus:

>>

>> http://wsg.washington.edu

>>

>> This works great but the somewhat byzantine CSS may be a bit

>> unwieldy for the client, who may have little understanding of

>> CSS (other than that which Dreamweaver so horrifically does

>> when you want auto-pilot styles...ugh).

>

> I'm unclear about what you want to do here. Is the issue that you

> want to

> create a menu where the content is separated from the style? Do you

> want

> different submenus to pop out depending on where you are on the site?

>

> Could you clarify a little better what you're trying to do here?

>

> Thanks.

>

> dw

>

> Dylan Wilbanks

> Web Producer

> Sch of Public Health and Comm Medicine

> U of Washington

> F-350 Health Sciences, Box 357230

> Seattle WA 98195-7230

> V: 206.221.6395 F: 206.543.3813

>

>

>

> ------------------------------

>

> Message: 3

> Date: Fri, 30 Nov 2007 15:31:36 -0800

> From: Jill Yetman <jyetman at u.washington.edu>

> Subject: Re: [Accessibleweb] Accessible menu system without

> popup/dropdowns

> To: Dylan Wilbanks <wilbanks at u.washington.edu>

> Cc: 'UW Web Accessibility Group' <AccessibleWeb at u.washington.edu>

> Message-ID: <47509D58.7070209 at u.washington.edu>

> Content-Type: text/plain; charset=ISO-8859-1; format=flowed

>

> UDM4 is "politically correct" mainly because it allows keyboard

> navigation with flyouts - most flyout menus do not.

>

> You might want to try editing an existing css menu

> http://www.alvit.de/css-showcase/css-navigation-techniques-

> showcase.php

> http://webdeveloper.econsultant.com/css-menus-navigation-tabs/

>

> Jill

>

> Dylan Wilbanks wrote:

>>> I'm seeking an easier solution than CSS (i.e., javascript) to

>>> replace a set of menus, and I'd like it to be politically

>>> correct (e.g., http://www.udm4.com).

>>>

>>> The catch is most programs/options I have found are all for

>>> popup/ dropdown submenus. I don't want this; I want all menu

>>> levels to be static, other than the "you are here" hint.

>>>

>>> That may be all you need to read to help, but if you want

>>> more info (e.g., context), here ya be:

>>>

>>> The site in question is http://depts.washington.edu/poeweb.

>>>

>>> Then, here's an example of a site done for us by UW Creative

>>> Services that uses only CSS for the menus:

>>>

>>> http://wsg.washington.edu

>>>

>>> This works great but the somewhat byzantine CSS may be a bit

>>> unwieldy for the client, who may have little understanding of

>>> CSS (other than that which Dreamweaver so horrifically does

>>> when you want auto-pilot styles...ugh).

>>

>> I'm unclear about what you want to do here. Is the issue that you

>> want to

>> create a menu where the content is separated from the style? Do

>> you want

>> different submenus to pop out depending on where you are on the site?

>>

>> Could you clarify a little better what you're trying to do here?

>>

>> Thanks.

>>

>> dw

>>

>> Dylan Wilbanks

>> Web Producer

>> Sch of Public Health and Comm Medicine

>> U of Washington

>> F-350 Health Sciences, Box 357230

>> Seattle WA 98195-7230

>> V: 206.221.6395 F: 206.543.3813

>>

>> _______________________________________________

>> Accessibleweb mailing list

>> Accessibleweb at u.washington.edu

>> http://mailman1.u.washington.edu/mailman/listinfo/accessibleweb

>

>

> ------------------------------

>

> _______________________________________________

> Accessibleweb mailing list

> Accessibleweb at mailman1.u.washington.edu

> http://mailman1.u.washington.edu/mailman/listinfo/accessibleweb

>

>

> End of Accessibleweb Digest, Vol 57, Issue 1

> ********************************************





More information about the Accessibleweb mailing list