- From: Loretta Guarino Reid <lorettaguarino@google.com>
- Date: Mon, 19 Feb 2007 12:03:32 -0800
- To: "Christophe Strobbe" <christophe.strobbe@esat.kuleuven.be>
- Cc: WCAG <w3c-wai-gl@w3.org>
This sounds like a case where the web page is being navigated sequentially, but in the opposite order. Do we need to add a common failure for checking the opposite order. (Is this really common)? Or amend the test procedure to test in both directions? Loretta On 2/19/07, Christophe Strobbe <christophe.strobbe@esat.kuleuven.be> wrote: > > 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 Monday, 19 February 2007 20:03:51 UTC