From: "Tim Arnold" <tim.arn...@gmail.com> > After using the stripped-down suckerfish CSS + very light JS for IE6 for > the past few years, I've started using the Suckerfish jQuery menu solution > ( > http://users.tpg.com.au/j_birch/plugins/superfish/) primarily because it > is > based on the Suckerfish menus, uses very clean XHTML/CSS, and provides a > wealth of JS fanciness without getting in the way of accessibility.
The only problem with Superfish approach is the Suckerfish part :-) Seriously, the examples here [1] become highly unusable and fairly inaccessible when script is disabled [1] http://users.tpg.com.au/j_birch/plugins/superfish/#examples Since this is a CSS list, and "Suckerfish-type" menus are CSS powered, it bears repeating that when you go beyond a straight and single-level dropdown, to a flyout scenario, it is very difficult for people to open the menu they want to open, and keep it open. The natural tendency of people is to move their mouse diagonally from a trigger link in one menu level to a target link in the next (flyout) level. Able-bodied folks have problems with this. Impaired folks often find it nearly impossible. If one must have a flyout scenario (for whatever reason), a scripted solution that does not fall back to pure CSS is the better choice. As for accessibility, consider this: http://www.projectseven.com/products/menusystems/pmm2/ug-examples/accessible/ -- Al Sparber - PVII http://www.projectseven.com Fully Automated Menu Systems | Galleries | Widgets http://www.projectseven.com/go/Elevators ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] 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/
