WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: skip-nav tabindex setfocus etc.

for

From: Alastair Campbell
Date: Mar 15, 2006 3:00AM

Damn, I wrote the below before I scrolled up in my webAIM folder, it
seems to becoming standard practice (which is great).

> I am thinking of first
> recommending that skip-nav links be visible, second that for
> non-scrolling pages, why not just use setfocus and put focus
> where it should go, or use tabindex=1 to jump to the
> content--saves keystrokes.

We usually take a slightly different approach that I first noted on Tom
Gilder's blog tom.me.uk in 2003 (not there anymore), although we
implemented it differently.

The skip-link isn't visible until you tab to it. This means that those
using the keyboard find it, but otherwise it isn't visible (and it isn't
hidden from screen readers either). See www.particlephysics.ac.uk for an
example.

With regards to tabindex, don't confuse people! Having a different order
between tabbing and arrowing (usual reading method) is very confusing,
and should only be used for specific forms or applications.

Kind regards,

-Alastair

--
Alastair Campbell | Director of User Experience

Nomensa Email Disclaimer:
http://www.nomensa.com/email-disclaimer.html