W3C home > Mailing lists > Public > public-wai-eo-badtf@w3.org > November 2008

Re: [Minutes] BAD TF teleconference on 28 October 2008

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 10 Nov 2008 15:14:15 +0100
Message-ID: <491841B7.4050005@w3.org>
To: Thomas Jewett <jewett@csulb.edu>
CC: public-wai-eo-badtf@w3.org

Hi Tom,

Thank you for this work! Indeed the format looks good, however it seems 
that we have a slight misunderstanding. If I remember correctly, we had 
agreed that you will evaluate the "after pages" according to WCAG 2.0 to 
see if we have been missing anything that needs to be addressed.

The next step would then be to evaluate the before pages but only after 
we've updated them. This evaluation would be used for reporting. Note 
however that we will primarily provide icon-based reports ("in-between 
pages"). Updating this report may only be a final step depending on the 
time and resources available.

Would you be willing to evaluate the "after pages" according to WCAG 2?


Thomas Jewett wrote:
> Hi, Shadi and all --
> I've taken a quick look at what it will take to upgrade
> the BAD evaluation report to WCAG 2.0. We're certainly
> covering as many of the success criteria as we were
> of the 1.0 checkpoints. The work will be in documentation.
> I've attached a snippet of HTML to show one possible
> approach (just section 5.1 of the report). The main idea
> here is to leave the basic format alone; I don't see any
> reason to re-invent the wheel. I'd like to discuss this
> in our meeting Wednesday, however, before proceeding.
> The conformance matrix (section 4) will obviously need to
> be changed to use success criteria instead of checkpoints.
> I'm wondering if any of the automated tools mentioned in
> paragraph 3.2 (Methodology) have been upgraded to check
> WCAG 2.0? I know that at least one vendor was working on
> this, but haven't heard from them recently.
> One minor suggestion on the report page: in my sample,
> I've added a bit of padding to the table cells -- this
> makes it easier even for fully-sighted readers to use,
> and can especially help those with low vision or
> dyslexia. There might be similar changes we could make
> elsewhere in the style sheet.
> Talk to you Wednesday,
> 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 Monday, 10 November 2008 14:14:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:50 UTC