[TECHS] Tests #138, #139, #140, #141, #142 - tabindex on input elements

Members of the Techniques task force have been assigned a number of tests 
to review and comment on to the list.   Here is my review of some of my 
assigned tests. 

Test numbers #138, #139, #140, #141, #142 listed below  require that any 
input element must have a tabindex.  I propose that we remove these tests 
since a specific tab order is NOT required in order to pass the WCAG 2.0 
Guidelines.  The tests are associated with Guideline 2.4, Provide 
mechanisms to help users find content, orient themselves within it, and 
navigate through it.  But, default navigation is provided by  UAAG 
Guideline 9. Provide navigation mechanisms [1].  Specifically Priority 1 
checkpoint 9.3,  Move Content Focus [2],  deals with sequential navigation 
to form controls and other enabled elements. 

Content authors should not be required to add a tabindex to input elements 
as long as the default tab order is sufficient. There are actually 
problems with adding a tabindex - once it is added to one element it often 
needs to be added to all focusable elements (including links) in order to 
keep the tab order logical.  In my experience, an element with a specific 
tabindex is always put in the tab order before elements that do not have a 
tabindex attribute set but are part of the default tab order.  Thus, if I 
have a page with two links followed by a form with two input fields, if I 
put a tabindex attribute on the input fields, they will be put into the 
tab order before the links. This may not be what is desired for logical 
navigation through the page. 

Since sequential navigation is covered by UAAG, the tabindex attribute is 
NOT required to meet Guideline 2.4 and I think these tests should be 
removed.  There is an HTML technique that discusses tab order [3] but it 
also has an editorial note that indicates that the technique needs to be 
updated to describe that, "it is often preferable to keep the default tab 
order."

I am not in favor of making this an optional test because of the 
possibility of creating confusion surrounding default tab order. But, if 
the group is in favor of making these tests optional, I would propose that 
they be associated with Guideline 2.4 Level 3 success criterion #2 When a 
page or other delivery unit is navigated sequentially, elements receive 
focus in an order that follows relationships and sequences in the content 
[4] (although the HTML tab order technique is associated with level 3 #1). 
 Currently the tests are listed as corresponding to a level 2 requirement. 
 

INPUT element, TYPE of "text", must have a tab index. [
http://www.w3.org/WAI/GL/WCAG20/tests/test138.html]
INPUT element, TYPE of "radio", must have a tab index. [
http://www.w3.org/WAI/GL/WCAG20/tests/test139.html]
INPUT element, TYPE of "password", must have a tab index. [
http://www.w3.org/WAI/GL/WCAG20/tests/test140.html]
INPUT element, TYPE of "checkbox", must have a tab index. [
http://www.w3.org/WAI/GL/WCAG20/tests/test141.html]
INPUT element, TYPE of "file", must have a tab index. [
http://www.w3.org/WAI/GL/WCAG20/tests/test142.html]

[1] 
http://www.w3.org/TR/2002/REC-UAAG10-20021217/guidelines.html#gl-navigation
[2] 
http://www.w3.org/TR/2002/REC-UAAG10-20021217/guidelines.html#tech-nav-active
[3] http://www.w3.org/TR/WCAG20-HTML-TECHS/#form_tabindex
[4] 
http://www.w3.org/TR/2004/WD-WCAG20-20041119/#navigation-mechanisms-focus


Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com