WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Target Jaws version?

for

From: Birkir R. Gunnarsson
Date: Apr 29, 2015 6:54AM

I personally try to test 2 versions back (or at least 1), especially
with Jaws, seeing as users do have to purchase upgrades.
I usually manage to at least sanity test with Jaws 14 currently.
With NVDA and Voiceover I do try to stay current since they are free upgrades.
I know this does not cover everything.
There are users on corporate networks or on old licenses or equipment
that may not be able to stay this current, but you kind of have to
draw a line in the sand and come up with what seems a reasonably
balanced strategy for testing, because if you start testing with all
types of A.T. and browser combos you end up being unaffordable .. and
what are standards for if not for getting rid of testing with an
endless combo of A.T. apps and browsers.
(I only talk about screen readers here, the reason being that I am
v100% lacking as far as sight is concerned, but testing with
magnification and such is also a very important aspect of
accessibility testing that I sadly have to leave to others).
Cheers
-B


On 4/29/15, Moore,Michael (DARS) < <EMAIL REMOVED> > wrote:
> If you are working on an internal application you can test for compatibility
> with a specific set of hardware and software because your organization
> controls the environment. If you are building for the public there is not a
> way for you to detect feature support within the AT. The best approach is to
> follow the standards and test with the current release. JAWS, Window Eyes,
> and NVDA all have had very good support for ARIA for a few generations of
> the product cycle when it is supported by the browser.
>
> Mike Moore
> Accessibility Coordinator,
> Texas Department of Assistive and Rehabilitative Services
> (512) 424-4159 (Office)
> (512) 574-0091 (Cell)
>
>