- From: Storr, Francis <francis.storr@intel.com>
- Date: Fri, 29 May 2020 18:13:46 +0000
- 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>
+1
Francis
-----
On 5/29/20, 08:47, "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
Received on Friday, 29 May 2020 18:14:05 UTC