Re: Action item: Tabindex technique

I agree that this technique looks good. More HMTL ignorance hre: if tabindex
is specified for any interactive elements on a page, must it be specified
for all elements? If so, should we add this to the test?

And I agree that using tables to express relationships between form fields
is acceptable, and even desirable in many cases. I wish AT knew how to use
the tables headers to label the cells/fields and navigate between fields
when content is structured that way.

Loretta

On 2/17/06 7:25 AM, "John M Slatin" <john_slatin@austin.utexas.edu> wrote:

> 
> Thanks, Yvette!
> 
> This looks very good.
> 
> I added a Status section at the top, to help us (and Ben) keep track of
> the technique as it moves toward acceptance.
> 
> I have one suggestion and one question.
> 
> Suggestion:
> Add a sentence/note explaining that all elements (or is it all focusable
> elements?) with tabindex will receive focus before *any* element that
> does not have tabindex.
> 
> So for example, if the form controls in your example have tabindex, but
> the links in the navbar do not have tabindex, users would have to tab
> through the form in order to reach the navbar.
> 
>  But it occurs to me I don't know what would get focus immediately after
> tabbing through the form: would it be to the next focusable element in
> the code? Or would it be the first focusable element in the delivery
> unit?
> 
> But that wasn't the question I wanted to ask. Here's the question:
> 
> I notice that the form is contained within a data table. I've done this
> myself, but I want to make sure we all agree that this is acceptable
> practice for WCAG 2.0.
> 
> I think it is: there are logical relationships here, not just between
> individual form controls and their labels, but between groups of form
> controls.
> 
> So: is it OK to use the table here? Or do we want to insist on using
> <fieldset> to group related controls, with CSS to control layout; and
> would that be an alternative way to make the tab order work properly?
> 
> Thoughts, anyone?
> 
> Thanks!
> John
> 
> 
> "Good design is accessible design."
> John Slatin, Ph.D.
> Director, Accessibility Institute
> University of Texas at Austin
> FAC 248C
> 1 University Station G9600
> Austin, TX 78712
> ph 512-495-4288, f 512-495-4524
> email jslatin@mail.utexas.edu
> web http://www.utexas.edu/research/accessibility/
> 
> 
>  
> 
> 
> -----Original Message-----
> From: public-wcag-teamb-request@w3.org
> [mailto:public-wcag-teamb-request@w3.org] On Behalf Of Yvette Hoitink
> Sent: Friday, February 17, 2006 6:18 am
> To: public-wcag-teamb@w3.org
> Subject: Action item: Tabindex technique
> 
> 
> Hello everyone,
> 
> Last Tuesday, we discussed using tabindex to specify a taborder that
> does not follow the order the elements are placed in the code. We
> decided that in some cases, it was a sufficient technique (for example
> for navigating forms column-by-column), just as long as relationships in
> the content were still followed. I created a technique for that in
> 2.4.7:
> <http://trace.wisc.edu/wcag_wiki/index.php?title=Creating_a_logical_tab_
> orde
> r_through_links%2C_form_controls%2C_and_objects>
> 
> Comments are welcome as always!
> 
> Yvette Hoitink
> Heritas, Alphen aan den Rijn, the Netherlands
> E-mail: y.p.hoitink@heritas.nl
> WWW: http://www.heritas.nl
> 
>

Received on Friday, 17 February 2006 15:33:29 UTC