Draft in Progress. Changes from previous version marked "(new)".
Len Kasday, Institute on
Disabilities/UAP at Temple
University
kasday@acm.org
This is a collection of user-oriented scenarios illustrating possible uses
of the Evaluation And Repair Language (EARL). See Sean Palmer's EARL Overview
and Minutes and
discussions following December Face to Face. (@@combine these scenarios
with Overview? Or reference from overview?)
EARL would initially be a means for expressing in a machine readable form (almost certainly XML, and very probably RDF):
The language would be extensible to
The following scenarious assume the existence of tools to create and process EARL documents. They include:
User: Person writing evaluation for client's web site, utilizing one or more evaluation tools that output EARL
This user would potentially be able to:
User: person responsible for repairing a web site in accordance with evaluation results (run by the user or a third party)
This user would potentially be able to:
An institution may need to use a web site that is not accessible, and no way to induce the site owner to make it accessible. For example, images may have missing ALT text. Daniel Dardailler's ALT Server paper described an approach in which a third party maintained ALT text images on a server. This could be generalized to any type of repair.
User: Person with a disability using a web site that is not accessible, but for which a third party has specified repairs.
This user would potentially be able to:
(see ER thread "Cursors face defining moment on the Web"
Users may wish to comment on pages or sections of pages as they browse which could be collected and optionally aggregated on an annotation server. This could involve digital signatures to check who comments came from.
(refer to the notes from the 13 March 2002 chat)
rev. 2/16/2001 LRK