Ryan, Sure they are frowned upon, but what option do you have? I always resort to a solution that involves javascript - CSS alone just doesn't work in IE6: Dropdowns/flyouts will show appear under select boxes - this is a big issue in IE6 and no amount of css (even hacks) can get around this in that browser. Oh and besides, it doesnt even support :hover css attributes for anything other than an anchor tag...
If you could guarantee that IE7 was used by everyone, at least them we could have CSS only solutions. Frankly, I hate drop down menus. They are unnecessary on most standard websites. Jame's work on UDM is probably the most accessible and functional ones out there - they cost, but he's a nice bloke so its worth it if you are doing something professionally with them. Karl On 6/13/07, Ryan Moore <[EMAIL PROTECTED]> wrote:
Thanks For your Input Phil. What annoys me with some of the solutions is trying to understand some of the browser hacks, and isn't it now with many of the browsers improving that hacks are frowned upon? On 6/12/07, Philip Kiff <[EMAIL PROTECTED]> wrote: > > >> Ryan Moore wrote: > >>> I see that it relies on a source of JS to complete the effect, and > >>> i'm wondering if it's possible to complete this purely with XHTML & > >>> CSS. Anyone have a good example of this? > > > Keryx Web (Lars Gunther) wrote: > >> Just do not do it. It cannot be done. > >> > >> a. JS is the best tool for *behavior*. CSS for design. > >> b. There are huge accessibility and usability issues with pure CSS > >> menus, such as: > >> - off-screen positioning > >> - moving the mouse the shortest distance will often lead to the menu > >> getting closed > >> - non-intuitive keyboard navigation > > Ryan Moore wrote: > > Ok. > > > > So typically is any form of navigation that relies on a rollover or > > hover state would be a bad practice of accessibility/usability? > > It depends on how it is done. I would disagree with Lars that it cannot > be > done, but to do it properly in a way that meets usability and > accessibility > guidelines requires a great deal of care and attention to detail. > > I think that the Ultimate Drop Down Menu 4.5 by Brothercake comes about > as > close as any I've seen to meeting those guidelines (someone else > mentioned > it last week in response to a similar question about accessible > drop-down > menus): > http://www.udm4.com/ > > UDM4 normally uses JavaScript, but it is designed so that the it will > degrade gracefully and you can set it up so that your menu will work the > same way as a CSS-only menu if JavaScript is turned off. It also > includes a > keyboard module that allows you to configure better keyboard access. > > UDM4 is copyrighted and there is a licensing fee, but non-profit > organizations can obtain a free license. I do not have any > relationship, > business or personal, with Brothercake/UDM4 other than having used it > when > working on a non-profit site in the past. > > Phil. > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
