[Athen] Questions for Vendors of Web-Based Applications

[Melanie Thornton]

Hi all,

I have been asked to pull together some questions for someone who is 
attending a conference where there will be vendors of various products.  
I wonder if you have developed a set of questions that you share with 
those who have access to vendors but who may not be able to construct 
accessibility-related questions on their own.  Here are some questions I 
composed.  I would love to have your input and/or your additions to this 
list.

Proposed questions:

    * How was it determined that the product meets Section 508 or other
      standards?
    * Has usability testing been conducted by users who use keyboard
      only access and/or screen readers?
    * If accessibility problems are found is the company committed to
      putting those fixes into a high priority queue rather than putting
      them in a 'feature request" queue?
    * Would the company be able/willing to sign a purchasing agreement
      that states that this product meets 508 or other standards?
    * Does the company have a contact person who is able to directly
      answer questions related to accessibility concerns?
    * Does documentation account for those who use assistive technology
      and/or keyboard only? 
    * Where applicable, do tutorials written for faculty or staff who
      are using the tool include information about best practices for
      accessibility  (i.e. adding descriptions of uploaded images,
      document accessibility, etc.)?

Thanks in advance,

Melanie


-- 

Melanie Thornton
Director, Project PACE
Associate Director, Disability Resource Center
2801 S. University Ave., DSC #103
Little Rock, Arkansas 72204
501.650.2239 (cell)
501.569.8240 (fax)
501.569.3217 (tty)

Websites:
http://ualr.edu/pace
http://ualr.edu/disability

We want your comments! 
<https://www.surveymonkey.com/s.aspx?sm=92u46bPPSZa2tyMqiGGTgQ_3d_3d>

AIM: MelanieatUALR

************************************
This message contains information which may be confidential or 
privileged. The information is intended to be for the use of the 
individual(s) named above. Please be aware that filing this email in 
publicly accessible records, or any disclosure, copying, distribution or 
use of the contents of this message is prohibited.
*******************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20100222/b1f4ead4/attachment.html>