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

RE: Proposed text for (new) checkpoint 6.3

From: Heather Swayne <hswayne@microsoft.com>
Date: Sat, 16 Jun 2001 19:48:05 -0700
Message-ID: <B7E0BEA478EBC24EBB2CF19F710760230170F177@red-msg-06.redmond.corp.microsoft.com>
To: "Marjolein Katsma" <access@javawoman.com>, <w3c-wai-au@w3.org>
Do we want authoring tools to interpret the work that the WAI has done?
Or are we trying to get authoring tools to document the features and
methods they support in order to adhere to the WAI Web content
guidelines?

-----Original Message-----
From: Marjolein Katsma [mailto:access@javawoman.com] 
Sent: Monday, May 07, 2001 7:26 AM
To: w3c-wai-au@w3.org
Subject: Proposed text for (new) checkpoint 6.3

Not at my best in formulating English right now - maybe I'm just tired
<g/>

Anyway, here's a draft proposal, subject to better wording, but I hope
the intention is clear enough:

---
6.3 In a dedicated section, document the process of producing accessible
content. [Priority 3]
	At minimum, provide an overview of tags and attributes that are
required for or enhance accessibility. Ideally, the text should explain
which features help for which types of disability and tools; a general
overview of steps to produce accessible content would be helpful.
---

Various techniques could help with that, one of them being:

At minimum: a "wrapper" document that lists tags and attributes and
their function for accessibility, with links to a general HTML reference
for syntax and context.

Cheers,


Marjolein Katsma
HomeSite Help - http://hshelp.com/
Bookstore for Webmasters - http://hshelp.com/bookstore/bookstore.html
Received on Saturday, 16 June 2001 23:04:23 GMT

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