WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: screen reader versions for testing

for

From: Beranek, Nicholas
Date: Oct 28, 2016 8:45PM

We test primarily with the latest versions of NVDA and Firefox. We've found that JAWS will compensate for bad coding practices (e.g. A missing programmatic label but adjacent text was present) and there were possibilities that it missed certain issues. If there is ever any question about the results from NVDA; then we'll try another browser. If it persists, we try another screen reader such as JAWS. Sometimes, we'll find that it's simply a user agent issue and we'll do our best to file a bug.

For responsive, we'll test the latest version of iOS with VoiceOver and Safari. Utilizing subject matter expertise: knowledge of the guidelines, nuances between screen readers, browsers, and operating systems, front-end development experience, other tools such as aXe and MSAA Object Inspect, the community, ARIA design patterns, and I could go on further, we're able to qualify that we've done our absolute best.

I hope this helps,

Nick Beranek
Capital One

> On Oct 28, 2016, at 4:54 PM, Mallory < <EMAIL REMOVED> > wrote:
>
> 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)
>>
>>