Re: Question about SC 2.4.3 Focus Order

+1

** katie **

*Katie Haritos-Shea*
*Principal ICT Accessibility Architect*


*Senior Product Manager/Compliance/Accessibility **SME*
*, **Core Merchant Framework UX, Clover*


*W3C Advisory Committee Member and Representative for Knowbility *


*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Seneca, SC **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.






On Fri, May 29, 2020 at 1:03 PM Chuck Adams <charles.adams@oracle.com>
wrote:

> Hi Katherine,
>
> I think I have a use case which doesn't align with your statement:  "If
> forward "navigation sequences affect meaning", going backward would mean
> the meaning would be lost."  There may be other use cases which do, but I
> don't think your statement is always true.
>
> The use case I'll site is our current NBA standings or NHL standings.  The
> listings of the teams are tab-able (though there are other issues on these
> pages), and sequence of the teams has meaning: their position in the
> standings.  As one tabs through the teams, their position in the sequence
> is their ranking in the standings.  Reverse tab doesn't lose meaning.  The
> user is still tabbing through their rankings, but the reverse tab ascends
> the standings rather than descends.
>
> Regards,
> Chuck the sports fan
>
> -----Original Message-----
> From: Katherine Eng <eng@access-board.gov>
> Sent: Friday, May 29, 2020 10:32 AM
> To: Katherine Eng <eng@access-board.gov>; Bruce Bailey
> <Bailey@Access-Board.gov>; WCAG list (w3c-wai-gl@w3.org) <
> w3c-wai-gl@w3.org>
> Cc: 508 <508@Access-Board.gov>
> Subject: RE: Question about SC 2.4.3 Focus Order
>
> The first line of my response was removed. It was
>
> -1: no
>
>
> -----Original Message-----
> From: Katherine Eng <eng@access-board.gov>
> Sent: Friday, May 29, 2020 12:28 PM
> To: Bruce Bailey <Bailey@Access-Board.gov>; WCAG list (w3c-wai-gl@w3.org)
> <w3c-wai-gl@w3.org>
> Cc: 508 <508@Access-Board.gov>
> Subject: RE: Question about SC 2.4.3 Focus Order
>
> If forward "navigation sequences affect meaning", going backward would
> mean the meaning would be lost. I wouldn't expect a page with meaningful
> forward focus order to preserve the meaning when navigated backwards.
>
> If going forward and backward do not affect meaning, then 2.4.3 would not
> apply.
>
> Thanks,
>
> Kathy Eng
>
> -----Original Message-----
> From: Bruce Bailey <Bailey@Access-Board.gov>
> Sent: Friday, May 29, 2020 11:46 AM
> To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
> Cc: 508 <508@Access-Board.gov>
> Subject: Question about SC 2.4.3 Focus Order
>
> 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
>
>
> https://urldefense.com/v3/__https://nam01.safelinks.protection.outlook.com/?url=http*3A*2F*2Fwww.w3.org*2FWAI*2FWCAG21*2FUnderstanding*2Ffocus-order.html&amp;data=02*7C01*7Ceng*40access-board.gov*7C4f19ba3fd7914fb09e5c08d803ed7d4c*7Cfc6093f5e55e4f93b2cf26d0822201c9*7C0*7C0*7C637263665827766302&amp;sdata=6l99U13BUZXFGkeEycy2lsGArrshOTUOPUanJghNjJw*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJQ!!GqivPVa7Brio!KxHPlYWa2iXC0H4MaxGZmC0ZC4SLpvSzA-qwZCUn563rUcabS54ggKR9ISvTJBmSdw$
>
> https://urldefense.com/v3/__https://nam01.safelinks.protection.outlook.com/?url=http*3A*2F*2Fwww.w3.org*2FTR*2FWCAG21*2F*23focus-order&amp;data=02*7C01*7Ceng*40access-board.gov*7C4f19ba3fd7914fb09e5c08d803ed7d4c*7Cfc6093f5e55e4f93b2cf26d0822201c9*7C0*7C0*7C637263665827766302&amp;sdata=3FM5ojOcCzxrharhBPuXvXDW7h*2FVAwbWyuqigvlSYJo*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJSU!!GqivPVa7Brio!KxHPlYWa2iXC0H4MaxGZmC0ZC4SLpvSzA-qwZCUn563rUcabS54ggKR9IStWA4WBnQ$
>
> https://urldefense.com/v3/__https://nam01.safelinks.protection.outlook.com/?url=http*3A*2F*2Fwww.w3.org*2FTR*2FWCAG21*2F*23dfn-navigated-sequentially&amp;data=02*7C01*7Ceng*40access-board.gov*7C4f19ba3fd7914fb09e5c08d803ed7d4c*7Cfc6093f5e55e4f93b2cf26d0822201c9*7C0*7C0*7C637263665827766302&amp;sdata=DAMl8ftlAgcEQzFmgzJPA7BMEZcRYECdY2MxtsPhS94*3D&amp;reserved=0__;JSUlJSUlJSUlJSUlJSUlJQ!!GqivPVa7Brio!KxHPlYWa2iXC0H4MaxGZmC0ZC4SLpvSzA-qwZCUn563rUcabS54ggKR9ISuAVJ6eNA$
>
>
>
>
>
>
>

Received on Friday, 29 May 2020 17:09:37 UTC