W3C home > Mailing lists > Public > w3c-wai-au@w3.org > April to June 2006

ATAG 2.0 Part A clarification

From: Jan Richards <jan.richards@utoronto.ca>
Date: Wed, 10 May 2006 15:05:21 -0400
Message-ID: <44623971.90303@utoronto.ca>
To: WAI-AUWG List <w3c-wai-au@w3.org>

On the last call I was given three related action items:

1. Action Item: JR to change references User Interface to Authoring Tool 
User Interface. Recommendation made by TB to document why language is
deviating from WCAG.

2. Action Item: AI: JR Non text objects to be changed to authoring tool 
interface in order to make language consistent with WCAG.

3. Action Item: JR to write language concerning Part A.

----------------------------

Here's what I suggest:

1. If we do want to be very specific in the Part A checkpoints we can 
standardize the structure with "For the authoring tool UI..." at the 
start of each. If we decide to remove this wording, then at least it is 
easy to do ([DEL] stands for deleted text). Personally I lean towards 
having it in because many people don't read intro text:

A.1.1: FOR THE AUTHORING TOOL UI Provide text alternatives for all 
non-text content [DEL]. [Priority 1]
A.1.2: FOR THE AUTHORING TOOL UI Provide synchronized alternatives for 
multimedia [DEL]. [Priority 1]
A.1.3: FOR THE AUTHORING TOOL UI Ensure that all displays are 
configurable. [Priority 1]
A.1.4: FOR THE AUTHORING TOOL UI Ensure changes to the display settings 
of editing views do not affect the content being edited. [Priority 1]
A.1.5: FOR THE AUTHORING TOOL UI Ensure that information, functionality, 
and structure can be separated from presentation. [Priority 1]

A.2.1: FOR THE AUTHORING TOOL UI Ensure that all functionality is 
operable via a keyboard or a keyboard interface. [Priority 1]
A.2.2: FOR THE AUTHORING TOOL UI Ensure user configurable access to 
selectable actions. [Priority 3]
A.2.3: FOR THE AUTHORING TOOL UI Allow authors to control time limits. 
[Priority 1]
A.2.4: FOR THE AUTHORING TOOL UI Allow authors to avoid content that 
could cause seizures due to photosensitivity. [Priority 1]
A.2.5: FOR THE AUTHORING TOOL UI Ensure that editing views enable the 
author to navigate the structure and perform structure-based edits. 
[Priority 2]
A.2.6: FOR THE AUTHORING TOOL UI Allow the author to search content and 
markup within the editing views. [Priority 2]
A.2.7: FOR THE AUTHORING TOOL UI Provide an undo function. [Priority 2]
A.2.8: FOR THE AUTHORING TOOL UI Provide personalized configuration. 
[Priority 2]
A.2.9: FOR THE AUTHORING TOOL UI Ensure previews emulate accessible 
rendering features of target browsers. [Priority 2]

A.3.1: FOR THE AUTHORING TOOL UI Observe the accessibility conventions 
of the platform. [Priority 2]
A.3.2: FOR THE AUTHORING TOOL UI Maintain consistency [DEL]. [Priority 2]
A.3.3: FOR THE AUTHORING TOOL UI Document the [DEL] USER interface 
including all [DEL] accessibility features. [Priority 1]

A.4.1: FOR THE AUTHORING TOOL UI Support interoperability with assistive 
technologies. [Priority 1]


2. Reword A.1.1 to rem "content" (assuming 1): FOR THE AUTHORING TOOL UI 
Provide text alternatives for all non-text objects.



3. (a) Reword Part A: from  "Make the user interface accessible" to 
"Make the authoring tool user interface accessible".

(b) Add this Part A intro text:

The checkpoints in Part A are intended to increase the accessibility of 
the authoring experience for authors with disabilities. For this reason, 
the requirements are narrowly focused on the accessibility of the user 
interface that the author uses to operate the tool, while the 
accessibility of the Web content produced by this use is not as important.

(c) Add this Part B intro text:

The checkpoints in Part B are intended to increase the accessibility of 
the Web content produced by *any* author to *end-users* with 
disabilities. While the requirements in this part do not deal with the 
accessibility of the authoring tool user interface, it should be noted 
that any the features added to meet Part B must also meet the user 
interface accessibility requirements of Part A.


Cheers,
Jan
Received on Wednesday, 10 May 2006 19:05:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 September 2008 15:53:06 GMT