> -----Original Message----- > From: Ben Curtis [mailto:[EMAIL PROTECTED] > Sent: Sunday, 5 December 2004 5:29 AM > To: [EMAIL PROTECTED] > Subject: [WSG] No skipping to content needed?
> A lot of people put an in-page anchor at the top to "skip navigation" > or "skip to main content." Are there any hidden gotchas with simply > putting the navigation last and positioning it first? > Interesting question, I think. The reason we tend to put the navigation to the top of the page is because for the user it is the most important object on a website. They want to always be able to access the navigation quickly and easily. It is even more important than the content of each page. This will be the case for those of us who use screenreaders and those who don't. In theory, a "skip to navigation" link at the top of the page could make your idea a nice little solution: it provides the users with screenreaders with quick access to the navigation, yet they don't have to tab through all that rubbish if all they want is the content. However, some problems I see: a lot of users I tested with screenreaders did not understand the concept of the "skip to content" or "skip navigation" links. They just tabbed through the navigation. If you turn things upside down, these users will be extremely confused, as they come to a page and the navigation is missing at the beginning. Also, if you do create a "skip to navigation" link at the top, then you might as well keep the "skip to main content" link and stick to standards. Or not? ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
