W3C home > Mailing lists > Public > public-wai-eo-badtf@w3.org > May 2009

Re: pages to analyze

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
Message-ID: <web-18345563@romulus.csulb.edu>
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 

- Should the comment be on the same line as the occurrence
   or before it? (I'm worried about connecting the report 
   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 

- And most importantly, is this strategy useable for doing 
   annotations and formatting the actual report?

Thanks for any ideas,


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:
>  - 
>  - 
>  - 
>  - 
> 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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 May 2009 05:51:23 GMT