- From: Gregg Vanderheiden <po@trace.wisc.edu>
- Date: Sat, 20 Mar 1999 18:13:14 -0600
- To: <pjenkins@us.ibm.com>, <w3c-wai-gl@w3.org>
Regarding comment #3 - this is an interesting thought. We'll need to see
if we can do this without making the page less understandable or if any of
these need to be more narrow... but it seems to me that we should be able
to do this.
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
Professor - Human Factors
Dept of Ind. Engr. - U of Wis.
Director - Trace R & D Center
Gv@trace.wisc.edu, http://trace.wisc.edu/
FAX 608/262-8848
For a list of our listserves send "lists" to listproc@trace.wisc.edu
3. use the same terms in all checkpoints, for example, in the Priority 1
checkpoints:
change: "all information conveyed", "document's text", "content of
each page", "the screen", "the site's content", dynamic "content",
"information", "the page", etc.
to: "the content", for example
4.1 Ensure that the contents conveyed with color is also ...
6.1 Clearly identify changes in the natural language of the contents.
8.3 Ensure that the contents is organized...
9.2 Avoid any blinking or updating of the content that causes flicker.
16.1 Use language that is clear and simple, yet appropriate for the
content.
Note: eliminating the word "page" or "site" also allows the checkpoint
to be flexibly applied on a page by page basis or on a site basis.
Regards,
Phill Jenkins (678-4517 tieline) 1-512-838-4517
Accessibility Program Manager
IBM Special Needs Fax: 1-512-838-9367
11501 Burnet Rd pjenkins@us.ibm.com
Austin TX 78758 http://www.ibm.com/sns
Received on Sunday, 21 March 1999 01:21:22 UTC