Comments on Developers' Guide to Features of Web Accessibility Evaluation Tools

Thank you for your efforts to produce a document that I think many will find valuable and the opportunity to provide comments on it.

I suggest removing "Developers'" from the title.  While I see that it would be useful for tool developers, I don't see anything that is specific to that audience.  Project and product managers, quality assurance staff, compliance officers, application developers, content contributors, and others may equally benefit from this content.  It would be a shame if they overlooked this resource because of the title.

I would like to see a section that describes where the tool runs, perhaps under a heading such as "platform."  It can be a key consideration in selection, and would be useful for filtering the soon-to-be-updated list of tools..  Platforms might include browser add-ons, client applications, enterprise applications, web applications/Software-as-a-Service, etc.

1.1 Evaluation Tools
I am puzzled by the inclusion of "web authoring tool" as an "evaluation tool".  Perhaps you mean that some web authoring tools include features for evaluation?  I would like to see clarification on why this is included here.

2.1.1 Content types; bullet item "Script resources"
I suggest changing "modify the content or the presentation" to "modify the content, the presentation, or the behavior".

3.2 Example Tool B
Typo: "volumens" should be "volumes".

I hope this helps.  I am looking forward to seeing the next draft.

sb
Sarah E. Bourne
Director of Assistive Technology 
Massachusetts Office of Information Technology
Commonwealth of Massachusetts
1 Ashburton Pl. rm 1601 Boston MA 02108
617-626-4502 
sarah.bourne@state.ma.us 
http://www.mass.gov/itd

Received on Thursday, 14 August 2014 20:11:04 UTC