What is web accessibility? | web axe [at gmail] NOSPAM! dot com
Thursday, August 03, 2006
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?:
<INPUT tabindex="1" type="text" name="field1">
<INPUT tabindex="2" type="text" name="field2">
<INPUT tabindex="3" type="submit" name="submit">Labels: accessibility, attribute, podcast, tab, web
web design | create a website | Website Templates | UK Web Hosting | Search Engine Optimization | search engine optimisation | web hosting | Cheap Domain Names
Add yourself to the Web Accessibility Enthusiasts mapper
Dennis Lembree is the founder of web development company Web Overhauls, which specializes in web usability, standards, and accessibility.
Ross Johnson runs a web design company (3.7 Designs) that takes a wholistic view on the web and art of constructing pages. They strive to be creative and unique.
1 Comments:
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