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

Re: ATAG2: Ideas for reorganizing A.3.4 SC

From: Jan Richards <jan.richards@utoronto.ca>
Date: Sat, 06 Feb 2010 22:59:22 -0500
Message-ID: <4B6E3A9A.2030505@utoronto.ca>
To: w3c-wai-au@w3.org
On the Feb 1 telecon, I took an action to "Take another look at an
overall "Navigate by structure" wording in A.3.4"....

The potential issue here is that we might be being overly-prescriptive 
about the types of navigation by structure ATAG2 should require.

In the current draft we have:

A.3.4.1 Edit by Structure (A)
A.3.4.2 Navigate By Element Type (AA)
A.3.4.3 Navigate By Headings (AA)
A.3.4.4 Navigate Tree Structures (AA)

The new proposal expanded that to:

A.3.4.1 Edit by Structure (A)
A.3.4.2 Navigate By Type/Role (AA)
A.3.4.3 Navigate Tree Structures (AA)
A.3.4.4 Navigate By Accessibility Relationships (AA)

But the point was made that this could prevent AA-conformance by a
simple form-building tool that used tabindex to navigate the form being 
built - which for simple forms seems sufficient.

The key point is THAT available structure should be leveraged for 
navigation, not HOW it should be done.

Perhaps we could simplify our current requirements to:

A.3.4.1 Navigate by Structure: Editing views for structured web content 
include navigation mechanism(s) that can make use of the structure. 
(Level A)

- Then examples would include:
  + navigation in hieracrchies
  + navigation by element type and role
  + navigation by accessibility relationships etc.
- A proviso could point out that the navigation would rely on the author 
having added the appropriate structure.


A.3.4.2 Edit by Structure: Editing views for structured web content 
include editing mechanism(s) that can make use of the structure. (Level A)

Then the examples would include:
- any element is selectable - and once selected editing (e.g., cut, 
copy, paste, presentation) can be performed directly on that element, 
its contents, and its sub-elements.
- The same proviso.

NEW DEFN:
*Structured web content* is web content that includes machine-readable 
internal structure (e.g., markup elements), as opposed to unstructured 
content, such as raster image formats or plain human language text.


Cheers,
Jan



> 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 Sunday, 7 February 2010 04:00:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 7 February 2010 04:00:09 GMT