Re: [WSG] Dropmenu accessibility and layout problem IE6
From: "Benjamin Hawkes-Lewis" Multiple hubpages reached are an excellent fallback for the non-JS state, and I'd agree that using multiple hubs is a reasonable keyboard-accessible alternative for dropdowns, particular as opposed to having lots of options in the tab order. However: * Opening submenus by activating a button-type control (e.g. pressing enter) avoids the need for excess tabbing. (Assuming your submenu links aren't tabbable when submenus are closed.) * I'm a bit uncomfortable with indicating to the keyboard user that a menu will dropdown with an arrow (as in your example), but sending them to another page instead. A possible enhancement might be making the arrow appear on mouse hover only? Excellent point. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Dropmenu accessibility and layout problem IE6
Al Sparber wrote: Having a hierarchical menu operate via the keyboard is, in my opinion, not the most accessible approach. This simple example page might provide some insight into how to apprach the accessibility of a dropdown or flyout menu: http://www.projectseven.com/products/menusystems/pmm2/ug-examples/accessible/ Multiple hubpages reached are an excellent fallback for the non-JS state, and I'd agree that using multiple hubs is a reasonable keyboard-accessible alternative for dropdowns, particular as opposed to having lots of options in the tab order. However: * Opening submenus by activating a button-type control (e.g. pressing enter) avoids the need for excess tabbing. (Assuming your submenu links aren't tabbable when submenus are closed.) * I'm a bit uncomfortable with indicating to the keyboard user that a menu will dropdown with an arrow (as in your example), but sending them to another page instead. A possible enhancement might be making the arrow appear on mouse hover only? On the whole, I favour multiple hubpages over dropdown menus as a navigation pattern for typical content-driven websites as opposed to web applications - they keep options simple and visible. -- Benjamin Hawkes-Lewis *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
RE: [WSG] Dropmenu accessibility and layout problem IE6
> -Original Message- > From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On > Behalf Of Henrik Madsen > Sent: Friday, December 12, 2008 3:57 PM > To: wsg@webstandardsgroup.org > Subject: [WSG] Dropmenu accessibility and layout problem IE6 > > > Seeking input and layout assistance (IE6, what else). > > I am considering using a Son of Suckerfish dropmenu for one item in my > main nav bar. > > It is accessible to screenreaders but how - if it's even possible - > can it be made keyboard accessible? These are two different approaches: http://www.tjkdesign.com/articles/keyboard_friendly_dropdown_menu/TZ.asp http://www.tjkdesign.com/articles/new_drop_down/ -- Regards, Thierry | http://www.TJKDesign.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Dropmenu accessibility and layout problem IE6
Henrik Madsen wrote: Seeking input and layout assistance (IE6, what else). I am considering using a Son of Suckerfish dropmenu for one item in my main nav bar. It is accessible to screenreaders but how - if it's even possible – can it be made keyboard accessible? For example, tab to the item in the menu > hit another key(?) to open the dropmenu > tab to chosen submenu item > hit enter. http://htmldog.com/articles/suckerfish/dropdowns/ Having a hierarchical menu operate via the keyboard is, in my opinion, not the most accessible approach. This simple example page might provide some insight into how to apprach the accessibility of a dropdown or flyout menu: 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 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Dropmenu accessibility and layout problem IE6
On Dec 12, 2008, at 3:56 PM, Henrik Madsen wrote: Seeking input and layout assistance (IE6, what else). I am considering using a Son of Suckerfish dropmenu for one item in my main nav bar. It is accessible to screenreaders but how - if it's even possible – can it be made keyboard accessible? For example, tab to the item in the menu > hit another key(?) to open the dropmenu > tab to chosen submenu item > hit enter. Hi Henrik, for keyboard navigation support, you might want to try superfish instead. It's fully accessible with js turns off and very easy to implement. http://users.tpg.com.au/j_birch/plugins/superfish/ tee *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] Dropmenu accessibility and layout problem IE6
Seeking input and layout assistance (IE6, what else).
I am considering using a Son of Suckerfish dropmenu for one item in my
main nav bar.
It is accessible to screenreaders but how - if it's even possible –
can it be made keyboard accessible?
For example, tab to the item in the menu > hit another key(?) to open
the dropmenu > tab to chosen submenu item > hit enter.
http://htmldog.com/articles/suckerfish/dropdowns/
Or is it wiser to forget the dropmenu approach altogether and have an
intermediary page offering the submenu choices?
Here is the page in development. See under 'Services'
http://members.iinet.com.au/~generator/chem/index-new.php
I work on a Mac and everything looks and functions perfectly in 5
different browsers. A colleague with IE7 has reported same. However,
the layout is screwed in IE6:
http://members.iinet.com.au/~generator/chem/grab.jpg
Notice the dropmenu pushes content below it downwards and other menu
items to the right. There also appears to be a problem with outer
margins of the main content (which I do not see via browsershots.org).
I have included the relevant css and js (both external files) below.
Any assistance would be greatly appreciated.
TIA,
Henrik
-
The menu is in a div with this css:
#menu {
height: 24px;
width: 840px;
margin-left: 30px;
border-bottom: solid #636467 1px;
float: left;
margin-bottom: 30px;
display: inline;
}
The other css for the menu is:
#nav, #nav ul {
list-style: none;
padding: 0;
margin: 0;
line-height: 1;
}
#nav a {
display: block;
color: #636467;
font-size: 1.2em;
padding-bottom: 8px;
}
#nav a:hover {
color: #E96D1F;
}
#nav li {
float: left;
margin-right: 24px;
}
#nav li ul {
position: absolute;
left: -999em;
background-image: url(images/drop-bg.png);
background-repeat: repeat;
width: 170px;
}
#nav li li a {
color: #FF;
display: block;
padding-left: 8px;
padding-top: 6px;
padding-bottom: -2px;
width: 162px;
}
#nav li:hover ul, #nav li.sfhover ul {
left: auto;
}
-
And the javascript:
sfHover = function() {
var sfEls = document.getElementById("nav").getElementsByTagName("li");
for (var i=0; ihttp://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
