E-mail List Archives

Re: screen reader versions for testing

for

From: Moore,Michael (Accessibility) (HHSC)
Date: Oct 28, 2016 1:42PM


Generally we test with the current release of JAWS. This is after we have thoroughly analyzed the code. If we run into unexpected problems then we will test with current release of NVDA, older versions of JAWS, more browsers etc. What we are doing at that point is attempting to determine who to file the defect with, what possible work arounds exist, and whether we can justify changing code that is technically compliant.

Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Delisi, Jennie (MNIT)
Sent: Friday, October 28, 2016 1:22 PM
To: <EMAIL REMOVED>
Subject: [WebAIM] screen reader versions for testing

Hello,

Interested in feedback. For those that test websites and documents for accessibility against the standards, but also use screen readers as a part of the testing protocols:

-how many versions do you test with? For example, if there is a version 17 and a version 18 of the same screen reader, are you testing with the current version and 1 version back?

-for those testing websites and documents that will be reviewed by the public, do you have a different number of versions you test with, as opposed to documents that will only be used internally? For example, there may be an expectation of employees having access to the latest version of a particular screen reader (with maybe one version back for a period of time), but the public may have varying amounts of resources to put towards upgrades.

Thanks in advance for any information you can share. I will be cross posting this on the IAAP list and LinkedIn.

Jennie

Jennie Delisi
Accessibility Analyst | Office of Accessibility Minnesota IT Services | Partners in Performance
658 Cedar Street
St. Paul, MN, 55155
O: 651-201-1135
Information Technology for Minnesota Government | mn.gov/mnit