WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: should 'skip to content' be the first element on thepage?

for

From: Shrirang Sahasrabudhe
Date: Jan 22, 2007 2:20AM

Pls find below the scenario... the previous mail was sent by mistake; sorry for the inconvenience.

Hi,
In my app; on a search form I have a search box with Tabindex as 1
So user jumps to the search bar on the first tab.
I also have ‘skip to content’ and ‘skip to navigation’ links.
On clicking the ‘skip to content user is put on to the search bar.
But as the first tab goes to the search bar; user reaches the ‘skip to content’ link after he cycles through the search bar.
Is this behavior appropriate from accessibility point of view?
Or ‘Skip to content’ and ‘skip to navigation’ should have tabindex 1 and 2 respectively on every page?

I feel
< For sighted keyboard users; the thing would work fine as the main functionality of the app is available with most ease.
Using screen reader also this should work fine as the user can normally jump through all the form fields and may not use the ‘skip to content’ so often.
As the links are not visible on the page; ppl having cognitive challenges would not get confused due to the application behavior.>
Of-course this all is my thinking; Pls guide and correct if I am wrong.
Thanks.
Shri


Christian Heilmann < <EMAIL REMOVED> > wrote: Technically it could be after a main heading or an introductory text.
The biggest use case of skip links is however to allow visitors to
skip over large blocks of links like a menu when they are located
before the main content in the document.
I am a bit at a loss to come up with a scenario where a skip link that
is needed shouldn't be the first thing in a document. If it doesn't
have to be, there is a big chance you won't need one.
--
Chris Heilmann
Book: http://www.beginningjavascript.com
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/