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

Re: pages to analyze

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 25 May 2009 09:22:34 +0200
Message-ID: <4A1A473A.3010804@w3.org>
To: Thomas Jewett <jewett@csulb.edu>
CC: public-wai-eo-badtf@w3.org
Hi Tom, all,

Looks good to me. Don't worry about any HTML coding, it is just the raw 
data for now. We will repackage it several times I guess.

Anybody have additional thoughts?

Best,
   Shadi


Thomas Jewett wrote:
> Hi, Shadi --
> 
> Here's the template. Turns out that the easiest way
> to document this was to put the info into a small
> database table -- with a huge bonus being the
> ability to re-order it in any way that we like.
> 
> On my PC, this is Microsoft Access, but that could
> be exported to anything else that would be useful,
> such as MySQL, etc. The export to HTML is really
> bad (I had to add column headings, for example),
> and it would only export in the order that data was
> entered. We can overcome this if the basic idea
> is what you want -- let me know, and I'll proceed
> with the rest of the pages.
> 
> See:
> http://www.tomjewett.com/badtf/BADemoWCAG2Analysis.html
> 
> Best,
> 
> Tom
> 
> On Fri, 22 May 2009 11:08:13 +0200
>  Shadi Abou-Zahra <shadi@w3.org> wrote:
>> Hi Tom,
>>
>> Thomas Jewett wrote:
>>> 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>
>>
>> It will be difficult to extract this information from the HTML. I'd 
>> prefer that you do the opposite: copy the code line into your report. 
>> For instance:
>>
>> # SC 1.3.1
>>  - H42: <h1>some text</h1>
>>  - H42: <h2>another text</h2>
>>  - G115: ...
>>
>>
>>> Which brings up some questions:
>>>
>>> - Should I do this for every occurrence, e.g., all <h2>s etc.?
>>
>> Yes, please. I know it is a lot of work but necessary to be sure.
>>
>>
>>> - 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.)
>>
>> As above, copy the code rather than the line numbers.
>>
>>
>>> - 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?
>>
>> The numbers are sufficient, I'll search and replace the text and links.
>>
>>
>>> - And most importantly, is this strategy useable for doing the
>>>   annotations and formatting the actual report?
>>
>> Don't think so. Please disregard the annotations for now. Once we have 
>> the complete report we can then select specific ones for annotations.
>>
>>
>>> Thanks for any ideas,
>>
>> Thanks for working on this! Please pass along a first iteration of the 
>> report (the template page only for now) rather than waiting until the 
>> end to get feedback.
>>
>> Best,
>>   Shadi
>>
>>
>>> 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 |
>>>
>>>
>>
>> -- 
>> Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
>>   WAI International Program Office Activity Lead   |
>>  W3C Evaluation & Repair Tools Working Group Chair |
> 
> 

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/ |
   WAI International Program Office Activity Lead   |
  W3C Evaluation & Repair Tools Working Group Chair |
Received on Monday, 25 May 2009 07:23:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 25 May 2009 07:23:07 GMT