- From: Rachael Montgomery <rachael@accessiblecommunity.org>
- Date: Fri, 29 May 2020 12:20:25 -0400
- Cc: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>, 508 <508@access-board.gov>
- Message-ID: <1ecdaa7b-6a9d-432e-bf7c-302f1303a0b7@Spark>
+1 On May 29, 2020, 12:14 PM -0400, Christopher Loiselle <chris.loiselle@oracle.com>, wrote: > +1 to JF’s interpretation. > > From: John Foliot <john.foliot@deque.com> > Sent: Friday, May 29, 2020 12:07 PM > To: Bruce Bailey <Bailey@access-board.gov> > Cc: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>; 508 <508@access-board.gov> > Subject: Re: Question about SC 2.4.3 Focus Order > > Hi Bruce, > > +1: yes, of course > > > > ...navigated sequentially: navigated in the order defined for advancing focus > > I think the key is the term 'advancing', which suggests 'forward' (as opposed to backward) movement. > > Logic (to me) suggests that *IF* the 'advancing' tab order (1, 2, 3, 4, 5) is logical and appropriate when moving forward, it would stand that going in the opposite direction would expect a tab order in reverse (5, 4, 3, 2, 1).. Since the user is already consciously "reverse-advancing" (retreating?) using shift+tab, I would suspect their expectation would be that the visible tab focus proceeds in *THAT* (reversed) order. > > My $0.02 > > JF > > On Fri, May 29, 2020 at 10:47 AM Bruce Bailey <Bailey@access-board.gov> wrote: > > Fellow AG'lers, I am asking that you indulge me in a quick straw poll: Does SC 2.4.3 Focus Order include backwards navigation? > > > > +1: yes, of course > > 0: not sure / maybe > > -1: no, of course not > > > > FWIW, the associated Understanding Doc has a contradiction between the third paragraph of Intent and the first example provide. I will be filling an issue (and, hopefully, following up with a pull request) about that, but really I first need a sense of the group consensus before that can happen. > > > > Follows is 2.4.3 and the relevant affiliated definition. > > > > Success Criterion 2.4.3 Focus Order (Level A): If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. > > > > navigated sequentially: navigated in the order defined for advancing focus (from one element to the next) using a keyboard interface > > > > www.w3.org/WAI/WCAG21/Understanding/focus-order.html > > www.w3.org/TR/WCAG21/#focus-order > > www.w3.org/TR/WCAG21/#dfn-navigated-sequentially > > > > > > > -- > John Foliot | Principal Accessibility Strategist | W3C AC Representative > Deque Systems - Accessibility for Good > deque.com > "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things" > >
Received on Friday, 29 May 2020 16:20:58 UTC