RE: Move Checklist out of Appendix

Good catch.

The checklists and annotated checklists evolved into the Quick Reference. 

So we should update these docs to reflect both the evolutions and the
changes in name.

Your suggestion to remove them from the requirements doc might be best since
it will keep us from having to repeatedly revise the charter as these
support documents evolve during implementation phases.   Also, that doc
won't be a formal note - at least is isnt planned that way - so it probably
doesn't belong in same treatment as techniques. 

Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
The Player for my DSS sound file is at http://tinyurl.com/dho6b 
 

> -----Original Message-----
> From: w3c-wai-gl-request@w3.org 
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Michael Cooper
> Sent: Tuesday, July 11, 2006 10:54 AM
> To: w3c-wai-gl@w3.org
> Subject: RE: Move Checklist out of Appendix
> 
> 
> Structurally I think it makes sense to move checklists out of 
> the appendix for the reasons you described.
>  
> Procedurally we might need to look at how this impacts our 
> requirements. The WCAG requirements document doesn't say 
> anything specific about checklists, but the "Requirements for 
> WCAG 2.0 Checklists and Techniques" [1] does. As I read this 
> document, it doesn't actually require us to create 
> checklists, but describes what they should be like if we do. 
> However, since this requirements document is a deliverable in 
> the Charter [2] I think it is strongly implied that we are 
> supposed to do checklists. Therefore, if we decide to remove 
> checklists, I think we should either a) remove checklists 
> from the Checklists & Techniques requirements document, b) 
> clarify in that document that checklists are not a required 
> deliverable but that we're merely specifying their structure 
> should we choose to provide them, or c) remove the charter 
> reference to that requirements document altogether. I 
> personally think option a might be best, but we should consider them.
> 
> Michael
>  
> [1] http://www.w3.org/TR/wcag2-tech-req/
> [2] http://www.w3.org/2004/04/wcag-charter.html
> 
> ________________________________
> 
> 	From: w3c-wai-gl-request@w3.org 
> [mailto:w3c-wai-gl-request@w3.org]
> On Behalf Of Gregg Vanderheiden
> 	Sent: Thursday, July 06, 2006 6:53 PM
> 	To: w3c-wai-gl@w3.org
> 	Subject: Move Checklist out of Appendix
> 	
> 	
> 
> 	In discussions between WCAG Editors and EO 
> representative - we discussed moving the Checklist and the 
> Mapping out of the appendix.
> 
> 	 
> 
> 	The Mapping would be moved so that it would not be 
> locked in the guidelines and could be updated as new 
> techniques or better mappings are developed in the future. 
> 
> 	On the call today the working group concurred with this view.
> 
> 	 
> 
> 	RE the Checklist
> 
> 	-          Now that we have the quick reference -
> 
> 	-          And because the guidelines are only guidelines and SC
> 
> 	 
> 
> 	The checklist is basically redundant.  It is no shorter 
> than the normative section of the guidelines and it is less 
> useful than the Quick
> Reference.   Any checklist should also really allow note 
> taking and be more
> of a tool. 
> 
> 	 
> 
> 	We are therefore thinking of removing the checklist 
> from the appendix - and implementing any checklists as 
> developer or evaluation resources in conjunction with EO or 
> ERT groups.
> 
> 	 
> 
> 	Anything we should be thinking about counter to this? 
> 
> 	
> 	Gregg
> 	
> 	------------------------
> 
> 	Gregg C Vanderheiden Ph.D. 
> 	Professor - Depts of Ind. Engr. & BioMed Engr.
> 	Director - Trace R & D Center 
> 	University of Wisconsin-Madison 
> 	<http://trace.wisc.edu/ <http://trace.wisc.edu/> > FAX 
> 608/262-8848
> 
> 
> 	The Player for my DSS sound file is at http://tinyurl.com/dho6b 
> 
> 	  <http://trace.wisc.edu:8080/mailman/listinfo/> 
> 
> 	 
> 
> 	 
> 
> 
> 
>

Received on Tuesday, 11 July 2006 16:32:49 UTC