RE: [EXTERNAL] RE: Question about SC 2.4.3 Focus Order

+1



From: Rachael Montgomery <rachael@accessiblecommunity.org>
Sent: Friday, May 29, 2020 9:20 AM
To: w3c-wai-gl@w3.org
Cc: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>; 508 <508@access-board.gov>
Subject: [EXTERNAL] RE: Question about SC 2.4.3 Focus Order

+1
On May 29, 2020, 12:14 PM -0400, Christopher Loiselle <chris.loiselle@oracle.com<mailto:chris.loiselle@oracle.com>>, wrote:

+1 to JF’s interpretation.

From: John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>>
Sent: Friday, May 29, 2020 12:07 PM
To: Bruce Bailey <Bailey@access-board.gov<mailto:Bailey@access-board.gov>>
Cc: WCAG list (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>) <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>; 508 <508@access-board.gov<mailto: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<mailto: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<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2Fwww.w3.org%2FWAI%2FWCAG21%2FUnderstanding%2Ffocus-order.html&data=02%7C01%7Cnidogbo%40microsoft.com%7Cda5a9216a84040c7099a08d803ec4bc3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637263660721000261&sdata=ecQ5etSNS2iWFsqHPQd%2BBWgo1KeP%2BspJ9%2Fkkc4KvACk%3D&reserved=0>
www.w3.org/TR/WCAG21/#focus-order<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2Fwww.w3.org%2FTR%2FWCAG21%2F%23focus-order&data=02%7C01%7Cnidogbo%40microsoft.com%7Cda5a9216a84040c7099a08d803ec4bc3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637263660721010263&sdata=eMylKsoxJDGF5phj7WMvZ14vnok3X0uSs%2F73IAgZzM8%3D&reserved=0>
www.w3.org/TR/WCAG21/#dfn-navigated-sequentially<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2Fwww.w3.org%2FTR%2FWCAG21%2F%23dfn-navigated-sequentially&data=02%7C01%7Cnidogbo%40microsoft.com%7Cda5a9216a84040c7099a08d803ec4bc3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637263660721010263&sdata=R4GcyHRzZvgcawnUM9zV9CzzSjxI7mgbxQNneu5SD1c%3D&reserved=0>



--
​John Foliot | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2Fdeque.com%2F&data=02%7C01%7Cnidogbo%40microsoft.com%7Cda5a9216a84040c7099a08d803ec4bc3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637263660721010263&sdata=ttTYkBWw0ZKFWg5BR48VHYJ9t5uS9xG3zB%2FltQZON9A%3D&reserved=0>
"I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"