Thierry Koblentz wrote:
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.
True - however I've become a big fan of tab-browsing recently (my home PC's mouse broke a week ago and I haven't seen fit to get a new one yet), and it is generally quite a jumpy affair - you're never exactly sure where you're going to jump to visually, and it's often not immediately visible with objects that don't highlight once activated.
As it stands, John's site already employs a nav that is above but below the header (as does the WaSP example I mentioned).
Admittedly if you're entirely reliant on visual presentation and tab-browsing (what kind of a demographic is this, I wonder?), I can imagine some users might get infuriated at going through the header and starting to plow around the content and extras without being able to access that nav that's apparently 'right there'. I would start back-tabbing at this point, but I don't know if that'd occur to most.
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.
Would be interested to see if this is the case. Quickly skimmed the guidelines but couldn't find anything.
Regards, Barney ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
