From: "Rahul Gonsalves" <[EMAIL PROTECTED]> > I did eventually go with the PVII menu - it's /sweet/. I'm wondering > how accessible it is with js disabled, but that's another question > for another list. Please do go through and give me some feedback. > > http://cfl.in/gamma/
Our implementation is designed so that the submenus are hidden instead of being positioned offscreen. We feel this is necessary with a "pure CSS" menu. Why? Because if you attempt to navigate a Son of Suckerfish menu with your keyboard, you will wind up tabbing through all of the submenu items. That's a problem, because they are not visible. The average user will think that the tab key (or equivalent) is not working and that's all she wrote. For blind users, they will need to listen to all links instead of just the root ones. This can be desirable sometimes, but usually it is not. If I were deploying your menu on our site, I would simply make sure that each of the links in the submenu is also available in the flow of the narrative on all associated pages. This article, written last year, discusses some of the concepts in the context of one of our commercial menu tools - but the theory is also applicable to the CSS Express Menu. http://www.projectseven.com/tutorials/accessibility/pop_integrated/index.htm -- Al ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- 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/
