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

Re: WCAG 2 techniques in After pages

From: Thomas Jewett <jewett@csulb.edu>
Date: Mon, 24 Nov 2008 22:09:12 -0800
To: Shadi Abou-Zahra <shadi@w3.org>
Cc: public-wai-eo-badtf@w3.org
Message-ID: <web-16168152@romulus.csulb.edu>

Thanks, Shadi --

I've always been convinced that programmers have to
be a bit lazy -- much easier to adapt something
that already exists than to start with a blank
page. :-)

I've been thinking a lot about the in-between pages;
I know that someone is working on the annotation
format, but there's a lot of information to convey
and it would probably be a good discussion topic.

My usual page analysis is fairly close to the tests
described under failure conditions in WCAG 2,
although not always as formal. Mostly, I rely on
the Illinois/CITA Firefox Accessibility Extensions
for looking quickly at headings, lists, styles, and
so on, which is what I was doing here -- as well
as checking against the code. Frankly, I had to
make some guesses -- so this version probably isn't
quite accurate. Eric is doing a great job with the
code -- once that's firmed up, we'll refine the
list and probably discover more coverage that we
already have, as well as some things that we've
missed and want to add.


On Mon, 24 Nov 2008 21:59:14 +0100
  Shadi Abou-Zahra <shadi@w3.org> wrote:
> Hi Tom,
> This is really useful, thank you! It is also a very 
>interesting approach to reuse the existing format and 
>adapt the "barriers" to WCAG 2.0. This will be very 
>useful for the report and for the "in-between pages".
> Just to be clear, did you actually run any of these 
>success criteria and techniques against the actual demo 
> What about the success criteria not listed here, does 
>the demo meet them or are they not applicable? At some 
>stage we need to end up with a full evaluation of the 
>demo against WCAG 2.0 to identify the success criteria we 
>meet and don't meet.
> Thanks,
>   Shadi
> Thomas Jewett wrote:
>> This time, I started with a stripped-down version of
>> the "barriers" page and identified the SC and techniques
>> used to correct each one in the "after" pages. Then I
>> added a list in SC/technique order at the top. Results 
>> http://www.tomjewett.com/badtf/features-new.html
>> I'd welcome corrections from those who know the code
>> a lot better than I do!
>> 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 Tuesday, 25 November 2008 06:21:30 UTC

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