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

ATAG2 proposal for reorganizing A.3.4 SC

From: Jan Richards <jan.richards@utoronto.ca>
Date: Fri, 29 Jan 2010 16:26:58 -0500
Message-ID: <4B6352A2.90303@utoronto.ca>
To: WAI-AUWG List <w3c-wai-au@w3.org>
Hi all,

This proposal attempts to address the IBM Feedback v2 comments (and the 
survey comments of other WG members)...I suggest a new A.3.4.2 
encompassing the various ways elements can be grouped for navigation and 
A.3.4.4 for using relationships (such as ARIA) to help authors navigate:

A.3.4.1 Edit by Structure: Editing views that display structured element 
sets provide a mechanism for the author(s) to select any element in the 
structured element set and perform editing functions (e.g., cut, copy, 
paste, presentation) on that element, its contents, and its 
sub-elements. (Level A)

A.3.4.2 Navigate By Type/Role: Editing views that display structured 
element sets provide a mechanism for the author(s) to shift the editing 
focus in the following ways (Level AA):
- from any heading element to the previous or next instance of any 
heading element.
- from any element to the previous or next instance of the same element.
- from any element with a role to the previous or next instance of an 
element with the same role.

A.3.4.3 Navigate Tree Structures: If an editing view displays a 
structured element set, then the author(s) can move the editing focus 
from any element to the following other elements in the structured 
element set (if they exist): (Level AA)
(a) Parent: The owning element; and
(b) Child: The first owned element; and
(c) Previous Sibling: The element immediately preceding at the same 
level; and
(d) Next Sibling: The element immediately following at the same level.

A.3.4.4 Navigate By Accessibility Relationships: Editing views that 
display structured element sets provide a mechanism for the author(s) to 
shift the editing focus between elements connected by recognized 
accessibility relationships. (Level AA)

ED. the intent would explain that this meant relationships as the HTML 
LABEL "for" attribute and ARIA relationship attributes such as 
aria-describedby and aria-labelledby. As per the definition of 
"recognized", the forms of accessibility relationships that the 
authoring tool recognizes are to be listed in the conformance claim.


Cheers,
Jan



-- 
(Mr) Jan Richards, M.Sc.
jan.richards@utoronto.ca | 416-946-7060

Adaptive Technology Resource Centre (ATRC)
Faculty of Information | University of Toronto
Received on Friday, 29 January 2010 21:27:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 29 January 2010 21:27:23 GMT