W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2003

List of lists -- good for checking our work

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 19 Feb 2003 23:11:13 -0600
To: w3c-wai-gl@w3.org
Message-id: <002a01c2d89e$7df55e20$056fa8c0@TOSHIBATABLET>

This is a good list of lists.

We should also walk each one of these and see how it would be covered in our
guidelines.   
Also - if these are simpler - why does ours have to be more complex.  I'm
not saying ours doesn't.  I'm just saying that if it is - we should have a
good reason... or we should make our simpler.

Thanks Wendy.

 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Wendy A Chisholm
Sent: Wednesday, February 19, 2003 1:01 PM
To: w3c-wai-gl@w3.org
Subject: [techs] checklists, testing for conformance


Hello,

At this a.m.'s techniques telecon we talked about use cases for the 
printable version of the checklists (although the use cases seem to apply 
to checklists in general).  We came up with three uses of the WCAG 1.0 
checklist [1] based on our experiences:

1.  user: developer
task:  reviewing site, making notes in table cells. go back to checklist 
on-line. but no way to fill out on-line.

2. user: evaluation and repair tool developer
task:  making the eval tool do what the checklist does. uses the checklist 
as a guide to determine if the tool covers everything.

3. user: 3rd party evaluator
task: evaluating a web site.  since they are not the developer and perhaps 
not technical, may answer some of the checks "don't know" if they don't 
know the intent of the elements.

What other guidance can we give people when they are trying to determine 
conformance?

The User Agent Working Group published "How to evaluate a user agent for 
conformance to UAAG 1.0" [2] which includes a series of steps in prose. 
They also published a checklist for UAAG 1.0 [3].

The Education and Outreach Working Group published "Getting Started: Making 
a Web Site Accessible" [4] and "Evaluating Web Sites for Accessibility" [5].

Other resources:
WebAIM's checklist for 508 [6] and tutorials [6.5].
IBM's checklist [7]
NCAM's guidelines [8]
Dive Into Accessibility [9] sorts tips by person, disability, design 
principle, web browser (includes some assistive technologies), and 
publishing tool.

There is a lot of other great work out there, this is just a small sample 
to spawn some discussion.
--wendy

[1] http://www.w3.org/TR/WCAG10/full-checklist.html
[2] http://www.w3.org/WAI/UA/2001/10/eval
[3] http://www.w3.org/TR/UAAG10/uaag10-chktable.html
[4] http://www.w3.org/WAI/gettingstarted/
[5] http://www.w3.org/WAI/eval/
[6] http://www.webaim.org/standards/508/checklist
[6.5] http://www.webaim.org/howto/
[7] http://www-3.ibm.com/able/accessweb.html
[8] http://ncam.wgbh.org/cdrom/guideline/
[9] http://www.diveintoaccessibility.org/

-- 
wendy a chisholm
world wide web consortium
web accessibility initiative
http://www.w3.org/WAI/
/--  
Received on Thursday, 20 February 2003 00:11:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:21 GMT