Barney Carroll wrote: > If you're thinking about this in the first place you may want to > consider the increasingly popular philosophy that navigation is 9 > times out of 10 the last thing someone wants to see first on any page > (you just used it to get here, it's only if you've made a mistake > that you're going to want to navigate away again immediately). If you > subscribe to this usability belief, you may consider sequencing your > page <header><content><navigation> and including a 'Skip to > navigation' at the end of the header.
> Using a bit of clever CSS, this needn't affect the visual layout of > the page. This might be confusing for sighted keyboard users as tabbing navigation would work differently than what they would expect; this would be different if the menu was some vertical navigation bar (right hand side next to content) rather than an horizontal one showing above the content. Also, I think (I may be wrong though) the WCAG 2 (FWIW) recommends to "display" the elements in the same sequence as they show in the markup. --- Regards, Thierry | www.TJKDesign.com ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
