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

Re: Requiring ATAG conformance

From: Matt May <mcmay@w3.org>
Date: Mon, 02 May 2005 16:43:13 -0700
Message-ID: <4276BB11.5090603@w3.org>
To: lguarino@adobe.com
Cc: w3c-wai-gl@w3.org

The Authoring Tools WG is working on eliminating this circularity in its 
next Working Draft of ATAG 2.0, which should be out in the next couple 
of weeks. In any case, the document will be very different from the 
current draft, so I would suggest holding off on this discussion until 
the new WD is published.


lguarino@adobe.com wrote:

>One of the proposals made for GL 4.2 was to include ATAG conformance 
>for authoring applications:
>[5] authoring applications (part of conformance?)
>Web applications that are created for the sole purpose of assisting
>users to create content intended for publication on the web must
>conform to at least Level A of the ATAG 2.0 Guidelines.
>In looking at the most recent ATAG 2.0 draft, it appears that ATAG 
>requires WCAG conformance:
><ATAG Guideline>
>1.1 Ensure that the authoring interface follows applicable software 
>accessibility guidelines. [Authoring Interface Checkpoints Relative to 
>WCAG or Authoring Interface Checkpoints Relative to ISO-TS-16071] 
>Rationale: If the authoring interface does not follow these 
>guidelines, people with disabilities may not be able to author Web 
>Techniques: Implementation Techniques for Checkpoint 1.1
>Success Criteria:
>The authoring tool must satisfy at least one of the following 
>(a) At least one full-featured Web-based authoring interface must 
>always conform to WCAG. 
>(b) At least one full-featured non-Web-based authoring interface must 
>always conform to ISO-TS-16071. 
></ATAG Guideline>
>So adding this requirement introduces a mutual dependency between the 
>guidelines. Can we do this, or does this introduce an infinite 
Received on Monday, 2 May 2005 23:43:17 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:07:39 UTC