Hi Franky, Thanks much for the great summary, and for your work on this! I actually didnt realize I had created invalid markup until you pointed it out. Im not entirely sure what you are suggesting for the work-around, but I would *really* love to see it, or maybe you could give a brief code example of what you are talking about?
In order to make things as accessible as possible, wed really need to nest the menus, so its too bad that Opera doesnt like that. Here is an old version of our page without the nested menus: http://www.berkeley.edu/test/calendar-tabs/sports-tabs-1.html This of course works just fine in Opera, but doesnt give the context of each menu (e.g. they cant tell that the menu that includes All Intercollegiate Sports is a submenu of the Sports menu) to users of screen readers. I recently discovered that you can download 40 minute versions of JAWS and Window Eyes, the most popular screen readers out there. They work for 40 minutes each time you re-boot your computer. It is really enlightening to do testing with these versions, though it does take a bit of work to get up to speed on their commands and how to use them properly. Heres an article on this: http://www.webaim.org/techniques/articles/screenreader_testing/ Thanks! Allison _____ From: francky [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 28, 2005 6:32 PM To: Allison Bloodworth Cc: '{tonyFelice}' <[EMAIL PROTECTED]>; paul walker; css-d@lists.css-discuss.org Subject: Re: [css-d] position: absolute; width: 100%, IE width not 100% Hi all, Allison wrote (28-12-05 19:48), resumé: 1> ... Paul's code + Tony's fix breaks FF: horizontal scrollbar to much & top <div> to short. and before (28-12-05 18:07): 2> ... [berkeley-site:] I got everything working in FF & Opera without having to change the nesting of the lists (thus, keeping it more accessible). @1: When Tony's code is placed in a IE * html-hack, FF will react as before, I think. But for me the major problems stay: - Paul's model doesn't work in Opera! See screenshot <http://home.tiscali.nl/developerscorner/css-discuss/images/paulwalker-sshot -Opera.png> 1. - When a visitor likes or needs to enlarge the font in his/her browser, the layout is not resistant. See screenshot <http://home.tiscali.nl/developerscorner/css-discuss/images/paulwalker-sshot -FF800x600-2fontsizesSmaller.png> 2 and screenshot <http://home.tiscali.nl/developerscorner/css-discuss/images/paulwalker-sshot -FF1280x1024-2fontsizesBigger.png> 3. @2: It happened that the html-validator showed some errors in placing the <ul>'s of the submenu's within the <li>'s of the menu... I corrected this in a <http://home.tiscali.nl/developerscorner/css-discuss/berkeley-francky.htm> berkely-testpage, in order to see if I could manage to get Tony's fix to it (and to steal the code in order to get Paul's model working in Opera). But ... only with corrected html, nothing changed: if the <ul>'s and <li>'s are in the correct w3c-way, now Opera goes vertical in the Berkely-model (just as in Paul's case)... screenshot <http://home.tiscali.nl/developerscorner/css-discuss/images/berkely-valid-in -Opera.png> 4. My conclusion: it is extremely hard (if not impossible) to satisfy IE, FF and Opera together in a liquid horizontal nested menu-structure. And the next step: what about other browsers? - I agree with Allison: a working model stays welcome! As a work-around I fall back to my suggestion to split up the menu in equally ranked <ul>'s for the (sub)submenus, which have visually the same layout and functionality. In order to get it as accessible as possible, I think that can be realised without to much trouble: by making a second navigation/menu-structure. I hope I can concretisize this in a testpage, over a few days. So long! francky ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
