> > > > Some questions on expanding menu's: > > > > - is a css + javascript combination still the best way to go (instead of > > > > css only)? > > > > Short answer: yes. Justification: > > http://www.wait-till-i.com/index.php?p=327 > > Well at least we need to remember one thing: the user can turn off > javascript support (also the fact is that 'noscript' is one of the > most popular extension in firefox). So even if we use javascript, we > have to make sure that the design is also accessible without > javascript support.
yes, as stated... quote: Notice that we are talking about modern DOM scripting here, that works unobtrusively (http://onlinetools.org/articles/unobtrusivejavascript) and follows the idea of progressive enhancement (http://en.wikipedia.org/wiki/Progressive_Enhancement). It is easy to find examples of scripts that dont help the cause, so please let the sins of the past be behind us. :unquote > > Short answer: Try using a keyboard (without creating invalid markup). > > I'm sorry, but I do not really get the meaning of the phrase, I am > using a keyboard :D quote: You are at the mercy of the browser when it comes to keyboard support. While the focus pseudo class offers you the option to trigger a style application via keyboard, browsers only allow keyboard access to links and buttons. With links being inline elements you can only nest other inline elements in them, and you may make it a real pain for users relying on assistive technology to use your site. While CSS can only apply styles to an element that has the focus (which could have happened either by keyboard or mouse) JavaScript can use several keyboard event handlers and even recognize which key is currently pressed. This enables you to create menus that work like real application menus. While the normal web way of navigating through a list of links via keyboard is to jump from link to link via Tab (or the A key in Opera), real application menus like the Windows start bar or any dropdown in the browser menu can be navigated with the arrow keys. :unquote > > If you want a good, free, as accessible as it gets menu try the YUI > > menu component: > > http://developer.yahoo.com/yui/menu/ > > YUI is great, both in quality and "size" :D (136K menu.js, 41K menu-min.js). The "my solution is smaller than yours" is as boring as the opposite equivalent when it comes to body parts. However: http://yuiblog.com/blog/2006/10/16/pageweight-yui0114/ As in terms of quality: There is a great book by Sitepoint called the JavaScript Anthology where James Edwards, developer of the Ultimate Dropdown Menu(UDM) explains ALL the things a real dropdown menu has to cater for - and these are a lot. If you can do better, do it, and consider these uses cases of the menu: - a user can only navigate via keyboard - the menu sub level cannot fit in the browser's viewport when it is expanded - a user is incapable of non-erratic mouse movements Happy coding. ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
