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

Reference to checkpoints

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Tue, 22 Apr 2003 17:55:35 -0400
Message-ID: <001601c30919$e80e75c0$6901a8c0@deque.local>
To: <w3c-wai-eo@w3.org>
For your consideration:
A. Social considerations page:
- Is second part of doc necessary... portion which contains  references to a few checkpoints?The tone of the doc suddenly seems to change. Is it now  justifying a few of the checkpoints or suggesting how guidelines help to attaina few of the advantages listed in the doc? 

- By the way, "clearly identifying the target of each link " helps all users and text to speech AT users as well. Not just users of old technology. At end of doc see:
. Clear Navigation and Links - providing clear and consistent navigation and clearly identifying the target of each link is a major benefit to users who
have to utilize old hardware.

B. Technical factors page:
Are references to checkpoints necessary here to say how site maintenance, server loading and device independence are supported in the WCAG?
The docs become longer when checkpoints are reproduced here. In case we must, then it needs to be restated in  lay language... the WCAG language does not make    for easy reading (most frequent criticism).
I guess readers of business suite are  looking for conceptual inputs highlighting macro/micro level issues here.
 

Sailesh Panchang
Senior Accessibility Engineer
Deque Systems Inc
11752, Valley Ridge Circle, Fairfax, VA 22033
Tel: 703-218-8018
Fax: 703-218-5047
E-mail: sailesh.panchang@deque.com
* Look up <http://www.deque.com> *
Received on Tuesday, 22 April 2003 17:53:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:35 GMT