W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > February 2007

Re: TAW Checker approach

From: Sean Owen <srowen@google.com>
Date: Thu, 22 Feb 2007 13:34:16 -0500
Message-ID: <e920a71c0702221034i3dcacdbdwdb7ef3074458a93b@mail.gmail.com>
To: "Shadi Abou-Zahra" <shadi@w3.org>
Cc: public-mobileok-checker@w3.org, public-wai-ert@w3.org

Cool we will make sure to give you the call details. Yeah I agree, if
the test results are going to be output in some XML format, it makes
sense to reuse an existing vocabulary like EARL for that. Easily done.

On 2/22/07, Shadi Abou-Zahra <shadi@w3.org> wrote:
>
> Dear all,
>
> I've been following discussion and would like to attend the upcoming
> call on behalf of the W3C Evaluation and Repair Tools Working Group:
>   - <http://www.w3.org/WAI/ER/>
>
> Currently there are many evaluation tools for Web accessibility and we
> are maintaining a list of many of them in a sortable database:
>   - <http://www.w3.org/WAI/ER/tools/>
>
> However, currently we are focusing on finalizing the Evaluation and
> Report Language (EARL) which is an RDF vocabulary to record test
> results. It's primary use is for evaluation tools to be able to export
> their testing results in platform-independent and machine-readable
> format. These results could be used by authoring tools (to integrate
> different evaluation tools) or to compare the output by different
> evaluation tools. Please find some references on EARL below:
>   - <http://www.w3.org/WAI/intro/earl.php>
>   - <http://www.w3.org/TR/EARL10-Schema/>
>   - <http://www.w3.org/TR/HTTP-in-RDF/>
>
> There are several tools that output EARL results including the W3C
> Validator, Hera, HiSoftware, and TAW. We expect many more evaluation
> tools may support EARL once it reaches Recommendation stage (we are
> aiming for Last Call in the very near future).
>
> Anyway, there seems to be a strong relationship and synergy between Web
> accessibility evaluation tools and mobileOK checkers. Personally I think
> that several evaluation tool developers may be interested in supporting
> mobileOK beside WCAG or other standards. Maybe we should think about
> supporting these developers by defining a common testing framework?
>
> Most Web accessibility evaluation tool developers have already started
> to define some kind of languages to describe tests. The aim is to have
> the tool itself be an engine for pluggable tests, for example to test
> compliance to different standards (WCAG 1.0, WCAG 2.0, Section 508,
> etc). Here are links to some of these languages, I am sure there are
> many more I am not unaware of or that are not been put in public space:
>   - <http://eval.webaim.org/> (LRAE is a well documented language)
>   - <http://checker.atrc.utoronto.ca/index.html>
>   - <http://www.it.uc3m.es/vlc/waex.html>
>
> I hope this is sufficient information and background for a starter
> *grin*, please let me know if you have questions or comments.
>
>
> Regards,
>    Shadi
Received on Thursday, 22 February 2007 18:34:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:02 GMT