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

Re: Report format

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Thu, 07 May 2009 09:00:37 +0200
Message-ID: <4A028715.8030309@w3.org>
To: Thomas Jewett <jewett@csulb.edu>
CC: public-wai-eo-badtf@w3.org
Hi Tom,

I'm not sure that it is only the Failures that we want to list to show 
that a Success Criterion has not been met. We can also show Techniques 
that have not been implemented, so that conformance with the Success 
Criterion could not be demonstrated. Having said that, it seems that we 
we'll need to clearly state the assumptions under which the evaluation 
took place (including mentioning Accessibility Supported Technologies).

I'll work on a draft format based on your input below for discussion.

Thanks,
   Shadi


Thomas Jewett wrote:
> Hi, Shadi --
> 
> If our report is going to be consistent with WCAG 2, it
> seems to me that it should go something like this:
> 
> For each success criterion, first mark it applicable
> or not. (We'll be able to skip the time-based media
> criteria, for example.)
> 
> For each applicable SC, first identify the failures.
> For example, for 1.3.1, we'll have (at least) failure
> F2 - using changes in text presentation to convey
> information without using the appropriate markup or
> text, with the line numbers where this occurs. I'm
> thinking that the *failure* is what we want in the
> annotation for the inaccessible version. One beauty
> of this is that we don't have to repeat any of the
> background or rationale, all of which is contained
> in "Understanding Guideline n.n".
> 
> Then for each failure, identify which techniques are
> needed to fix the problem. For F2, we'll have (at
> least) H42: Using h1-h6 to identify headings. As
> we've planned, the technique will be the annotation
> on the accessible page.
> 
> Looking at the complexity of the linkage between
> the WCAG 2 documents, I'm guessing that there is a
> database somewhere that organizes the information.
> If we had access to that, it might make the report
> easier to write.
> 
> Regards,
> 
> Tom
> 

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

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 May 2009 07:01:12 GMT