Kit Grose wrote:
> I've heard the request for pure CSS drop-down menus quite a lot, and
> rarely see people getting told what they should about how *bad* they
> are.
Thanks for bringing it up.
You're right of course, but CSS designers rarely want to know how *bad*
CSS is in that respect. It is actually possible to create working
solutions with CSS - one method mentioned in the original thread, but
they tend to disappear amongst all "can never work properly" solutions.
> Please, for your users' sake: use a Javascript drop down menu (but
> make sure it's one that is fully accessible, and that reverts to a
> pure-CSS menu when JS is not available).
Again: perfectly right, but the good Javascript menus also tend to
disappear amongst the many bad ones, and too few know how to, or bother
to, test any CSS or script solution across the board, and they rarely
ever leave them in working conditions.
Yes, warnings come up on the list almost as frequent as the requests for
help with those drop-downs. I guess those warnings are ignored for a
reason, but I can't think of a good one other than that the word
"accessible" is a no-no in most design-circles, and more or less
off-topic on this list.
Both CSS and Javascript tend to be used in ways that are
counter-productive when it comes to accessibility, and when did you last
hear a client ask for accessible solutions? I just did, but that's
probably because I won't accept to work with anything else. Can't
prevent others from doing it though.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
