W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2005

RE: Selecting Web Accessibility Evaluation Tools- Issue 4

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Mon, 31 Jan 2005 19:35:44 +0100
To: "'Sailesh Panchang'" <sailesh.panchang@deque.com>
Cc: <w3c-wai-eo@w3.org>
Message-ID: <004a01c507c3$ad77bd90$da42fe51@K2>

Hi Sailesh,

> Some features one should  look for in a tool are:
> 1. How many checkpoints does the tooll address?
> 2. What is the accuracy / reliability with which  it can identify
barriers?
> 3. Can it spider through a site?
> 4. What platforms does the tool work on?
> 5. Does it allow  the evaluator to "customize" the   evaluation by
indicating  
> parameters. eg. how many links constitute a group.
> 6. Does it seek input when it is not possible to determine if there is
a 
> accessibility problem? eg. Is this table for layout table or a data
table or 
> is color being used for conveying essential info? Based on the
response the 
> tool can identify problems (if any) programatically. Still there can
be 
> issues where huuman judgement is needed and a tool   cannot do much.
> 7. How good is the reporting- report formats, content and are there
different 
> types of reports to meet needs of different users like supervisors,
person 
> doing eval / remediation work, etc? 
> 8. How is the user interface- in terms of ease of use / navigating?
> 9. How accessible is the tool to PWD and users of AT?
> 10. How good is the documentation?
 
These are very helpful questions, I will try to build them into the next
revision. Thank you.

Regards,
  Shadi
Received on Monday, 31 January 2005 18:35:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:52 UTC