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

ATAG 2.0 In-group checkpoint review: A.0.1

From: Jan Richards <jan.richards@utoronto.ca>
Date: Wed, 26 Apr 2006 10:37:45 -0400
Message-ID: <444F85B9.9040904@utoronto.ca>
To: "List (WAI-AUWG)" <w3c-wai-au@w3.org>

Rolling along to A.0.1...

[1] Checkpoint text: OK

A.0.1 Ensure that browser-accessed functionality conforms to WCAG. 
[Relative Priority]


[2] Rationale: last clause added (starting with ", whether")

Rationale: Authors must be able to have access to authoring tool 
functionality that is implemented as Web content, whether this is one 
specific feature (e.g. Web-based help) or the entire authoring tool.


[2] Note: last sentence added

Note: For non-Web-based authoring tools, this is a relatively 
straightforward requirement, likely covering only a few areas of the 
interface (i.e. Web-based help features, etc.). However, for most 
Web-based authoring tools the requirement will cover the majority of 
functionality in the tool and overlap many of the other requirements in 
Part A of the guidelines. When this is the case, a note entitled "For 
Web-Based Interface Components" will appear below the success criteria 
to provide more information.


[3] Success Criteria: The second SC actually should not have been there 
- it must have been put in accidentally - it has been removed. In SC2 
"interface" added to agree with the notes.

SC1: Any interface component of an authoring tool that is accessed by 
the author within a Web browser must conform to WCAG.


[4] TECHNIQUES

Techniques for SC1:

Applicability: This success criteria is not applicable if the authoring 
tool lacks any component that is accessed via a Web browser.

Technique A.0.1-1.1: REWORDED

Technique A.0.1-1.1 [Sufficient]: For Web-based applications, following 
the requirements of WCAG. This means implementing all of the 
requirements of the Content Type-Specific WCAG Benchmark (specified in 
the conformance claim) for the content-type in which the authoring 
interface is implemented.

     Example A.01-1.1: Throughout tool development the templates and 
other mechanisms that are used to generate the authoring interface are 
designed with WCAG conformance as a goal and are periodically checked to 
ensure conformance.

Technique A.0.1-1.2 [Advisory]: Testing Web-based authoring interfaces 
against WCAG using automated evaluation and repair tools.

     Example A.01-1.2: Throughout development, with the authoring tool 
in various states that are representative of the range of tasks that the 
tool is able to perform, "snap-shots" of the tool are captured with the 
user agent. These snap-shots, containing both the editing interface and 
the content being authored are then examined with WCAG evaluation 
software. Problems are corrected and the process continues to iterate.




Cheers,
Jan
Received on Wednesday, 26 April 2006 14:38:14 GMT

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