- From: Greg Lowney <gcl-0039@access-research.org>
- Date: Wed, 17 Oct 2012 12:44:37 -0800
- To: Jim Allan <jimallan@tsbvi.edu>
- CC: WAI-ua <w3c-wai-ua@w3.org>
- Message-ID: <507F18B5.2090904@access-research.org>
The proposed clarification sounds fine to me. -------- Original Message -------- Subject: ACTION-762: Review 2.2.3 for language, do we mean tab, source, or document order? From: Jim Allan <jimallan@tsbvi.edu> To: WAI-ua <w3c-wai-ua@w3.org> Date: 10/16/2012 8:55 AM > ACTION-762: Review 2.2.3 for language, do we mean tab, source, or > document order? > > current: 2.2.3 Default Navigation Order (former 1.9.9): If the author > has not specified a navigation order, the default *sequential > navigation* order is the document order. (Level A) > > Sequential navigation is defined in the glossary. We will need to > review 2.2.3 after the discussion of the glossary change proposed by > Jan [1]. > > There was confusion about the term 'document order'. the original > intent of the SC was to be sequential navigation of enabled elements > in source code order - the Lynx model of navigation - ignoring all > css. In other words in what order does the focus move when the user > hits the 'tab' key. Discussion ensued about using the rendered content > (rtl or ltr depending on language) to be the default order for > sequential navigation of enabled elements. > Most browsers (all that I have checked - ie, ff, chr, o) all move > through the document in source code order barring any tabindex > commands. Rather than making the browser change the default behavior, > we should not move to rendered content order. > > recommend changing the wording to reflect specifically source code order > <new> 2.2.3 Default Navigation Order (former 1.9.9): If the author has > not specified a navigation order, the default *sequential navigation* > order is the document source code order. (Level A) > > Jim > > > 1. http://lists.w3.org/Archives/Public/w3c-wai-ua/2012OctDec/0011.html >
Received on Wednesday, 17 October 2012 19:47:39 UTC