- From: Daniel Dardailler <danield@w3.org>
- Date: Tue, 24 Apr 2001 15:51:43 +0200
- To: "Leonard R. Kasday" <kasday@acm.org>
- cc: "Sean B. Palmer" <sean@mysterylights.com>, w3c-wai-er-ig@w3.org
> Why are you saying repair is not core? because > Personally speaking at least, I think it's an important part of EARL. For > example, if I'm evaluating a web page, and I see some poorly worded ALT > text, I'd certainly want to have a way to suggest better ALT text. And > once I do that, the output can be used for repair. as you say: the earl output can be used for repair, and for many other things: it's a evaluation report. there's no repair information ("how to repair it") in the core vocabulary we put together so far repair is just one scenario of use certification is another metrics chart etc > Repair has been in the user scenarios for months... e.g. see the part > starting at http://www.w3.org/WAI/ER/IG/earl.html#evaluation . > > Len > > > At 08:42 AM 4/24/01 +0200, Daniel Dardailler wrote: > > >Thanks Sean. > > > >Before we start publicizing this stuff. > > > > > Done, and done. EARL is now open for business! > > > > > > http://www.w3.org/2001/03/earl/ > > > - EARL - the Evaluation And Repair Language > > > >At the PF f2f, we also discussed the fact that Repair in EARL were > >sort of "not core", and so maybe the correct expansion of the acronym > >should be > > EARL: Evaluation and Reporting Language. > > > >What do people think ? > >I think it's still time to change it but later on it will be more > >problematic. > > > > > > -- > Leonard R. Kasday, Ph.D. > Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple > University > (215) 204-2247 (voice) (800) 750-7428 (TTY) > http://astro.temple.edu/~kasday mailto:kasday@acm.org > > Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group > http://www.w3.org/WAI/ER/IG/ > > The WAVE web page accessibility evaluation assistant: > http://www.temple.edu/inst_disabilities/piat/wave/
Received on Tuesday, 24 April 2001 09:52:01 UTC