- From: Thomas Jewett <jewett@csulb.edu>
- Date: Thu, 21 May 2009 22:50:43 -0700
- To: Shadi Abou-Zahra <shadi@w3.org>
- Cc: public-wai-eo-badtf@w3.org
Hi, Shadi/all -- Trying to think of a reasonably efficient way to document what will have to be a line-by-line analysis of the code. I could simply add comments to a copy where they apply, for example: <!-- SC1.3.1, G115, G140, H42 --> <h1> Which brings up some questions: - Should I do this for every occurrence, e.g., all <h2>s etc.? - Should the comment be on the same line as the occurrence or before it? (I'm worried about connecting the report to the final line numbers in the code.) - Are just the SC/G/H numbers sufficient for this pass, or should I try to include all of the associated text and links here? - And most importantly, is this strategy useable for doing the annotations and formatting the actual report? Thanks for any ideas, Tom On Wed, 20 May 2009 18:29:36 +0200 Shadi Abou-Zahra <shadi@w3.org> wrote: > Hi Tom, > > As discussed, please start a WCAG 2.0 conformance >analysis of the following pages: > - ><http://www.w3.org/WAI/demos/bad/draft/2009/after/template/> > - ><http://www.w3.org/WAI/demos/bad/draft/2009/after/home/> > - ><http://www.w3.org/WAI/demos/bad/draft/2009/after/news/> > - ><http://www.w3.org/WAI/demos/bad/draft/2009/after/tickets/> > > Regards, > Shadi > > -- > Shadi Abou-Zahra - http://www.w3.org/People/shadi/ | > WAI International Program Office Activity Lead | > W3C Evaluation & Repair Tools Working Group Chair |
Received on Friday, 22 May 2009 05:51:22 UTC