Current Posts

Tab Index - why and why not

WCAG Guidelines 9.4 (Priority 3) says to create a logical tab order through links, form controls, and objects. The "tabindex" attribute is great because it does exactly that -- it specifies the position of the current element in the tabbing order for the current document. But are they needed?

Download Web Axe Episode 24 (Tab Index -- Why)

[Transcript]

The basic code:
<INPUT tabindex="1" type="text" name="field1">
<INPUT tabindex="2" type="text" name="field2">
<INPUT tabindex="3" type="submit" name="submit">


Links:

Labels: , , , ,

1 Comments:

At 10:48 AM, Anonymous Ross Johnson said...

Just listened to the show, good info. The only time I felt it was necissary to use the tab index was an odd case where tabbing would cause a jump from over one of my form elements. I think it had something to do with floating text, but it was a quicker fix than trying to re-write the css.

 

Post a Comment

<< Home

RSS icon; follow the RSS feed for Web Axe
Twitter icon; follow Web Axe on Twitter

Like Web Axe?

Podcast Alley

Odeo

Mapper on Frappr

Add yourself to the Web Accessibility Enthusiasts mapper

Previous Posts