Hi John
Roger Hudson and Russ Weakley did an interested paper on this which explains the organization of navigation really well: http://www.usability.com.au/resources/ozewai2005/ Cheers, Gian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Green Sent: Thursday, 14 June 2007 5:10 AM To: wsg@webstandardsgroup.org Subject: RE: [WSG] Screen Reader Accessible Navigation Suggestions Yes that's exactly what I'm suggesting. Our www.accessibility.co.uk website is an example of that. It doesn't have third level navigation but if it did I would put another list below the second level navigation. The site is only about 30 pages so third level menus are not needed, and the few third level pages are just linked from within the body of second level pages. We have done the same at www.testpartners.co.uk, which has about 60 pages but don't look at the coding - it's more than 4 years old and in desperate need of a rewrite. Steve _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Moynihan Sent: 13 June 2007 19:44 To: wsg@webstandardsgroup.org Subject: RE: [WSG] Screen Reader Accessible Navigation Suggestions Hi Steve, Thanks for replying to my posting. I am a little confused as to exactly what you are referring to. Are you saying have a primary navigation for various sections of the website and then on each secondary page add another list and the same for third level pages? Would you have any links as examples that I can take a look at? Thanks for your help, John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Green Sent: Wednesday, June 13, 2007 1:50 PM To: wsg@webstandardsgroup.org Subject: RE: [WSG] Screen Reader Accessible Navigation Suggestions That's not a big site so I would expect that two lists for the primary and secondary navigation would be sufficient. Use a third list if you need a third level of navigation. I would advise against nesting the second and third level navigation lists, which is what people often do. It may be semantically correct but it makes it difficult for screen reader users to build a mental model of the navigation because it changes so much from page to page, and some won't even know what nested lists are. Consistency is key to a good user experience with a screen reader. Avoid any kind of dropdown menu. There have been many attempts to create accessible dropdown menus, but they all cause accessibility problems for one user group or another. Even the best ones rely on non-standard interaction models in order to achieve good accessibility, which is not really a solution at all. If you want to provide headings to indicate the primary, secondary and tertiary menus then you can hide them off screen. They are not essential but they can help the user build a mental model of the page and they provide landmarks that aid navigation. Steve _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Moynihan Sent: 13 June 2007 17:46 To: wsg@webstandardsgroup.org Subject: [WSG] Screen Reader Accessible Navigation Suggestions Hi Folks, I was wondering if the group could offer some advice regarding accessible navigation for a website. I have a website that I'm working on that needs to be accessible for people who use screen readers such as Jaws. I am kind of stumped on which type of navigation to utilize since the website has approximately 110 pages. I can just create a list for the navigation. Does anyone have any suggestions as to what would be the best way to set up the navigation for this site? Thanks for your help. John ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
