Re: SC 2.4.6 (Focus order) and (reverse) tab order

I think the generic problem is when scripting happens in one direction
that "fixes" the tab order, but it fails to fix it when traversed in
the reverse direction. If I am understanding this correctly, then I
suspect this is uncommon but possible, and could be addressed by
David's suggestion.

Loretta

On 2/20/07, Gregg Vanderheiden <gv@trace.wisc.edu> wrote:
>
> That is what I meant.   Onblur changing focus fails WCAG.  So it is not
> necessary to create another failure for that.
>
>
> Gregg
>  -- ------------------------------
> Gregg C Vanderheiden Ph.D.
>
>
>
> > -----Original Message-----
> > From: w3c-wai-gl-request@w3.org
> > [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Christophe Strobbe
> > Sent: Tuesday, February 20, 2007 3:35 AM
> > To: WCAG
> > Subject: RE: SC 2.4.6 (Focus order) and (reverse) tab order
> >
> >
> > Hi Gregg,
> >
> > At 23:58 19/02/2007, Gregg Vanderheiden wrote:
> > >I believe the onblur event would fail WCAG.  When you fix
> > that failure, the
> > >problem disappears - no?   If so we don't need another failure.
> >
> > Using the onblur event wouldn't necessarily fail WCAG, it
> > depends on what that event triggers. In this case, it
> > triggers something that causes a failure. (The failure is
> > somewhat similar to F44 but uses JavaScript instead of
> > tabindex.) I don't know if the example I gave is a *common*
> > failure, but adding the note suggested by David to the intent
> > of SC 2.4.6 would at least address the issue.
> >
> > Best regards,
> >
> > Christophe
> >
> >
> >
> > >Gregg
> > >  -- ------------------------------
> > >Gregg C Vanderheiden Ph.D.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: w3c-wai-gl-request@w3.org
> > > > [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Christophe Strobbe
> > > > Sent: Monday, February 19, 2007 9:16 AM
> > > > To: WCAG
> > > > Subject: SC 2.4.6 (Focus order) and (reverse) tab order
> > > >
> > > >
> > > > Hi,
> > > >
> > > > During a review of test cases in the BenToWeb test suite for WCAG
> > > > 2.0, the following occurred to me:
> > > > SC 2.4.6 requires that "When a Web unit or authored component is
> > > > navigated sequentially, components receive focus in an order that
> > > > follows relationships and sequences in the content."
> > However, there
> > > > are many types of content that can be tabbed through both in
> > > > "normal"
> > > > order (usually top to bottom, just pressing the TAB key) and in
> > > > reverse order (pressing SHIFT + TAB). It is possible for
> > scripts to
> > > > manipulate the focus in such a way that certain items are
> > skipped in
> > > > normal tabbing order but not in reverse tabbing order. This would
> > > > fail the intent of SC 2.4.6 but this is not made explicit
> > anywhere.
> > > >
> > > > An example of this behaviour can be seen at
> > > > <http://www.bentoweb.org/ts/XHTML1_TestSuite2/testfiles/sc3.2.>
> > > 5_l3_027.html>.
> > > > When tabbing through this file, focus goes from the first to the
> > > > third link (the second links is skipped because an
> > 'onblur' event on
> > > > the first link changes focus to the third link). When tabbing in
> > > > reverse order, however, you get all the links.
> > > >
> > > > Best regards,
> > > >
> > > > Christophe
> >
> >
> > --
> > Christophe Strobbe
> > K.U.Leuven - Departement of Electrical Engineering - Research
> > Group on Document Architectures Kasteelpark Arenberg 10 -
> > 3001 Leuven-Heverlee - BELGIUM
> > tel: +32 16 32 85 51
> > http://www.docarch.be/
> >
> >
> > Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
> >
> >
> >
>
>
>
>

Received on Wednesday, 21 February 2007 05:11:46 UTC