Re: [selecting eval tools] simplifying terminology and wording at beginning

What Shawn wrote up reads  well and I like it better. Some  issues however, are:
1.  Do we not want "repair" to be part of the title?
2. Validation tools: 
Shawn wrote: "...they evaluate more than specific accessibility issues".
My understanding is that  the primary purpose of such a tool is to validates proper use of  mark-up, etc. and check  conformance against the specs or standards. 
It does not really  check for accessibility barriers although  invalid code contributes to inaccessibility.
Therefore I feel that the above line within quotes should not be there. 
3.  Transformation tools: Do you mean Lynxviewer, or something for Firefox that can  disable style sheets, disable images, disable
page colors, show access keys, etc.?
I feel that something that converts a Word or PPT or PDF file to HTML is  a transformation tool but not an accessibility evaluator.
And self voicing browsers like HPR are essentially user agents or adaptive software or AT, are they not? Calling HPR an transformation tool will allow one to stretch further and call JAWS too a transformation tool. I suppose this is not intended.  
So of the three examples above, I think only the first category has a place in this doc on selecting eval tools. 
4. In the intro we should  also highlight that  using these eval and repair tools  is not enough. Some of the tools help inautomatic and fast  identification of some accessibility barriers. But manual checking by actual users of AT is necessary for most content. 
The above is needed in this doc if it has a section on "What are eval tools?" and is not covered in other docs in the resource suite.
Sailesh Panchang
Senior Accessibility Engineer 
Deque Systems,11180  Sunrise Valley Drive, 
4th Floor, Reston VA 20191
Tel: 703-225-0380 Extension 105 
Fax: 703-225-0387
* Look up <> *


Received on Friday, 17 December 2004 23:09:17 UTC