WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: screen reader versions for testing

for

From: Mallory
Date: Oct 28, 2016 3:53PM

Kinda the same here: test with current (sometimes the tester doesn't
have the absolute most-current either), and things that don't work, we
look them up to see if it's some known bug, if it was fixes, which
versions were affected. In general being up to date for some big bugs so
that if things work with a current version, we can be more aware it may
fail in an older version.

One thing I try to keep in mind is wealthy web developers tend to have
the latest and greatest. But the same usually can't be said for our
customers, so it's dangerous for us to assume "passes in latest" =works for everyone.

cheers,
_mallory

On Fri, Oct 28, 2016, at 09:42 PM, Moore,Michael (Accessibility) (HHSC)
wrote:
> 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)
>
>