- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Mon, 21 Feb 2005 15:23:03 +0100
- To: <public-wai-ert@w3.org>
Hi, This is where the WCAG 2.0 Test Suites come into play. In WCAG 2.0 each "Success Criteria" needs to be testable (independently from automated or manual execution). For each Success Criteria there are fine-grained tests which should determine whether the criteria is met or not. <http://www.w3.org/WAI/GL/WCAG20/tests/> In ERT we need to help the development of these Test Suites in order to allow the following: * tests are well structured and complete so that E&R tools could use them effectively * tests are atomic and unambiguous to ensure a single interpretation in E&R tools * tests can be used as a repository to measure the coverage and precision of E&R tools Maybe we should discuss some of this on the call tomorrow. Regards, Shadi -----Original Message----- From: public-wai-ert-request@w3.org On Behalf Of Andrew Kirkpatrick Sent: Friday, February 18, 2005 20:15 To: public-wai-ert@w3.org Subject: Re: EARL Scenarios > One of the main objective of EARL is to combine different tools' > evaluation results in order to compare them. Another important feature > of EARL is that it can be used for exchanging data between tools. I agree with this as a good objective. Comparing results between tools won't be possible until there is a defined list of tests that the tools can reference. It is possible to reference issues by the WCAG guideline, but the actual tests occur at a much more fine-grained level (e.g. alt missing from an image that is in a link that contains other text is more specific than 'images must have alt'). Getting this list is very important, and difficult. AWK -- Andrew Kirkpatrick WGBH National Center for Accessible Media 125 Western Ave. Boston, MA 02134 E-mail: andrew_kirkpatrick@wgbh.org 617.300.4420
Received on Monday, 21 February 2005 14:23:31 UTC