- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Mon, 04 Dec 2006 21:03:45 +0100
- To: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
- Cc: public-wai-ert@w3.org
Hi Carlos, Carlos Iglesias wrote: > In response to the action item recorded at [...] the following is a > proposal to include warnings management in EARL. Thank you for working on this, and for sharing your ideas! > - Does this proposal cover everybody's needs? I think purists would argue that these are actually three separate testable criteria hiding in one shell: * CSS document validity * background/foreground color contrast * redefinition of properties > - Is there any use case where a warning messages could be treated > as anything else than "plain text"? It seems we still need a compelling example of a real warning in the context of EARL. We often talked about warning to describe situations such as "nearly-passed" or "could-do-better". I can't think an example but we need one to justify this new feature. > - Are any additional properties necessary? (e.g a warning id) Inspired by your example, I was thinking of an earl:relatesTo property which points to another related test result. However, I think that would be an attempt to define a test description language... Regards, Shadi -- Shadi Abou-Zahra Web Accessibility Specialist for Europe | Chair & Staff Contact for the Evaluation and Repair Tools WG | World Wide Web Consortium (W3C) http://www.w3.org/ | Web Accessibility Initiative (WAI), http://www.w3.org/WAI/ | WAI-TIES Project, http://www.w3.org/WAI/TIES/ | Evaluation and Repair Tools WG, http://www.w3.org/WAI/ER/ | 2004, Route des Lucioles - 06560, Sophia-Antipolis - France | Voice: +33(0)4 92 38 50 64 Fax: +33(0)4 92 38 78 22 |
Received on Monday, 4 December 2006 20:03:54 UTC