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

Checkpoints for Guideline 1

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 25 Jun 2001 10:49:49 -0400
Message-ID: <3B374F8D.EEEF0D4C@utoronto.ca>
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Hello all,

Here's a reworking of 1.2 and 1.3 that enables them to better match the
new structure:

1.2 Ensure that the tool preserves all accessibility information during
transformations and conversions. [Priority 1]

Rationale: Accessibility information is often vulnerable to loss when
content is converted or transformed from one format into another.

Minimum functionality: All accessibility information present in the
initial document or fragment to be must be present in the converted or
transformed result. Where this is not reversible, inform the author.

Optional advanced functionality: Use markup, or some other mechanism to
record the transformation and ensure reversibility.

See also: Techniques for checkpoint 1.2


1.3 Ensure that when the tool automatically generates markup, it
conforms to the W3C's Web Content Accessibility Guidelines 1.0 [WCAG10].
[Relative Priority]

Rationale: Many tools generate markup that is not directly specified by
the author. Ensuring that markup is accessible will reduce author
workload during checking and correction. 

Minimum functionality: All decisions made by the tool regarding markup
type or practices should optimize the accessibility of the content (as
per WCAG). The author may be given the option of over-riding the choices
proposed or made by the tool.

See also: Techniques for checkpoint 1.3 



Jan Richards
Adaptive Technology Resource Centre (ATRC)
University of Toronto

Tel: (416) 946-7060  Fax: (416) 971-2896

Received on Monday, 25 June 2001 10:50:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:46 UTC