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

Re: 6.3: RE: checkpoints 6.1,6.2,6.3

From: Phill Jenkins <pjenkins@us.ibm.com>
Date: Mon, 18 Jun 2001 00:59:44 -0400
To: w3c-wai-au@w3.org
Message-ID: <OF11B03A81.21A7B743-ON86256A6F.001B49CD@raleigh.ibm.com >
I agree that the minimum for 6.3 should not be

At minimum, provide an overview of the tags and attributes
that are required to enhance accessibility.

but as Heather suggests, point to WCAG.  Here is my proposal:

At minimum, provide an overview of the tags and attributes
that are support by the authoring tool and link to the latest
W3C WAI Web Content Accessibility Guidelines and techniques.

Regards,
Phill Jenkins,  (512) 838-4517
IBM Research Division - Accessibility Center
11501 Burnet Rd,  Austin TX  78758    http://www.ibm.com/able



"Heather Swayne" <hswayne@MICROSOFT.com>@w3.org on 06/16/2001 10:06:00 PM

Sent by:  w3c-wai-au-request@w3.org


To:   "Jan Richards" <jan.richards@utoronto.ca>, "WAI AU Guidelines"
      <w3c-wai-au@w3.org>
cc:
Subject:  6.3: RE: checkpoints 6.1,6.2,6.3



I always thought the minimum for checkpoint 6.3 would be for an
authoring tools documentation to inform the author above the WAI Web
content accessibility guidelines and provide a pointer to their latest
documentation. Checkpoint 6.1 provides for documenting the accessibility
features and methods of that particular authoring tool.

-----Original Message-----
From: Jan Richards [mailto:jan.richards@utoronto.ca]
Sent: Monday, May 28, 2001 12:32 PM
To: WAI AU Guidelines
Subject: checkpoints 6.1,6.2,6.3

Hello all,

To follow up on today's call, here's my take on checkpoints 6.1, 6.2,
6.3.


6.1 Document all features that promote the production of accessible
content. [Priority 1]

This checkpoint promotes the production of accessible content by helping
authors learn how to use the accessibility related features of the tool.
At minimum, the tool should include documentation explaining the purpose
and use each of these features. More advanced implementations might
provide context-senstive links to this content from within the authoring
tool user interface.

---

6.2 Ensure that creating accessible content is a naturally integrated
part of the documentation, including examples. [Priority 2]

This checkpoint promotes the production of accessible content by
implicitly demonstrating to the author that all content, regardless of
purpose, should comply with the WCAG guidelines. At minimum, all
documented examples of the authoring tool interface (i.e. dialog boxes,
code views, etc.) should include any relevant accessible authoring
practices.

---

6.3 In a dedicated section, document the process of producing accessible
content. [Priority 3]

This checkpoint promotes the production of accessible content by
explicitly informing the author of the steps they need to take (using
the the features of the tool documented for Checkpoint 6.1) to satisfy
this goal. At minimum, provide an overview of the tags and attributes
that are required to enhance accessibility. The documentation for each
feature might explain which disability groups and user agents benefit
from its use.



--
Cheers,
Jan

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

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

jan.richards@utoronto.ca
Tel: (416) 946-7060  Fax: (416) 971-2896

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Received on Monday, 18 June 2001 00:59:50 GMT

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