Issues for ATAG 2.0 Working Draft

This document provides a guide to issues which are yet to be resolved, as well as those which have already been resolved, by the Authoring Tools Accessibility Guidelines Working Group (AUWG). It will be maintained through the life of the Authoring Tool Accessibility Guidelines 2.0 document, and updated regularly as new issues are raised or resolved.

Issues for Guidelines

Unresolved

1. Definitions needed for a number of terms.

(TB's list, 13 Jan 2004) (KM to make proposal, 26 Jan 2004)
Decision:

2. Concept of "typical user" in success criteria may be unclear.

(Concept introduced by JT, 25 June 2003) (Problems raised by TB, 26 Sept 3003) (KM to make proposal, 26 Jan 2004)
Appears in success criteria for checkpoint 4.1
Decision:

3. Concept of a "usability STUDY override" to normative requirements for conformance (success criteria) still undecided (connected with idea of typical user)?

(JR Raises, 22 Sept 2003) (Problems raised by TB, 26 Sept 3003)
Decision:

4. Functional spec or usability-oriented guide? Is ATAG a document that specifies programmatic requirements, or one that directs the outcome (related to usability override)?

(Raised by MM, 26 Sept 2003 in Seattle)
Decision:

5. Where will Definition of Authoring Tool example images "live" (in the guidelines or techniques) - currently they have been moved to the techniques?

Decision: Raised by JR. (KM to make proposal, 26 Jan 2004)

6. Handling non-W3C formats - Rationale and success criteria of 2.2

(Discussed, 26 Sept 2003 in Seattle) (Joint discussion with WCAG-WG, 24 Oct 2003)
Decision:

7. There may be insufficient attention paid to Web-based authoring environments

(GD's Comment attached to reply by CMN)
Decision:

8. New editorial additions require group approval.

(various places in the document)
Decision:

Resolved

1. How do we deal with changes to the WCAG conformance levels that may impact ATAG's relative priority checkpoints?

Decision: Use a separate "ATAG 2.0 References to WCAG" document that we intend to publish as a W3C Note when ATAG 2.0 becomes a Recommendation.

2. "Opt-out" policy on accessibility? (Turn off accessibility features, rather than turning them on)

(Raised by GP, 26 Sept 2003)
Decision: Agreed to require accessibility features be enabled by default but suggest ability for author to opt-out (turn them off).

Issues for Implementation Techniques

Unresolved

1. Can ATAG implementation techniques link to ISO16071

(TB's analysis of linking to ISO1071 vs. IBM-SAG ver.3.1)
Decision: Group would prefer to link to ISO16071 (Agreed - 15 Dec 2003).
Outstanding issue is W3C protocol for this (MM to check).

2. What form of document presentation will work best for listing the techniques?

(KM's comment) (JR's proposal, 17 Nov 2003)
Decision:

3. How does the new techniques document work with the old icon-based approach of ATAG 1.0 techniques?

(Raised on call, 17 Nov 2003)
Decision:

4. Checkpoint 4.X (4.2) is still lacking techniques

(Added at Seattle F2F, 26 Sept 2003 ) (JR's proposed wording, 7 Nov 2003) (JR's sample workflow, 4 July 2003)
Decision:

5. New editorial additions require group approval.

(various places in the document)
Decision:

Resolved

Issues for Test Suite

Unresolved

1. How to make use of and expand TB's draft test plan

(TB's testing principles document, 14 May 2003) (TB's proposal, 5 Jan 2004)
Decision:

2. Test case development in conjunction with WCAG-WG?

(Joint discussion with WCAG-WG, 24 Oct 2003)

Resolved

Last updated $Date: 2003/12/01 20:50:51 $ by Jan Richards (jan.richards@utoronto.ca)

Copyright © 1998 - 2003 W3C (MIT, INRIA, Keio ), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.