W3C home > Mailing lists > Public > w3c-wai-au@w3.org > January to March 2013

RE: ATAG 2.0 Focus indicator during navigation

From: Alex Li <alli@microsoft.com>
Date: Thu, 7 Feb 2013 17:55:26 +0000
To: "Richards, Jan" <jrichards@ocadu.ca>, "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <4bde7a54dacb419c850ae631d1b72533@SN2PR03MB096.namprd03.prod.outlook.com>
No serious objection, but why are we deviating from WCAG 2.4.7?

-----Original Message-----
From: Richards, Jan [mailto:jrichards@ocadu.ca] 
Sent: Wednesday, February 06, 2013 6:15 AM
To: w3c-wai-au@w3.org
Subject: RE: ATAG 2.0 Focus indicator during navigation

Sorry, I pressed send to quickly on the previous email.  

Here's the proposal for a new ATAG 2.0 SC. The wording is adjusted from that of WCAG [1] and makes use of the ATAG2 term "sequential keyboard access": 

A.3.1.2 Focus Visible: If the *authoring tool* provides *sequential keyboard access*, then a keyboard focus indicator can be visible. (Level A)

---

[1] 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

 [2] ATAG2.0 Glossary: sequential keyboard access: Using a keyboard interface to navigate the focus one-by-one through all of the items in an ordered set (e.g., menu items, form fields) until the desired item is reached and activated. This is in contrast to direct keyboard access methods such as keyboard shortcuts and the use of bypass links.

(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca
Received on Thursday, 7 February 2013 17:57:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 February 2013 17:57:05 GMT