E-mail List Archives
Thread: Testing with JAWS and NVDA - which versions are best?
Number of posts in this thread: 4 (In chronological order)
From: Sarah Jevnikar
Date: Wed, Aug 23 2017 3:36PM
Subject: Testing with JAWS and NVDA - which versions are best?
No previous message | Next message →
Hi everyone,
I'm about to start a project where previous accessibility tests have been run. I've been asked to give end-user feedback on complaints raised by the client who is concerned that WCAG 2.0 Level A failures are occurring.
These prior tests used several versions of both JAWS and NVDA. I'm running JAWS 17 but also have 16 on my system, but tests were run with 16 and 18. Does it make sense to run tests with both versions? I'm not sure how many have upgraded to JAWS 18 given the price and existing compatibility.
As for NVDA, the original tests were run with 2016.3, 2016.4, and 2017.3. I'm running 2017.3 on my machine, but am wondering if I need to test with the older versions. In my anecdotal experience it would appear that NVDA users tend to keep their software up to date but I don't want to miss things.
Added to this, I know the recent versions of browsers (Chrome, Firefox and IE) that were used to test, but these versions were released after JAWS 16 and NVDA 2016, so either tests have been happening since last year, or happening recently with old versions of screen readers. If the former, then proper notes about which version of SR has problems with which version of browser have not been kept to my knowledge.
Does anyone have any thoughts on which SR versions to use?
Thank you,
Sarah
From: Srinivasu Chakravarthula
Date: Wed, Sep 06 2017 10:50PM
Subject: Re: Testing with JAWS and NVDA - which versions are best?
← Previous message | Next message →
Hello,
I always test with latest version of NVDA and if something that needs
second opinion, I use another screen reader such as JAWS.
Regards,
Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
Website: http://www.srinivasu.org | http://serveominclusion.com
Let's create an inclusive web!
Lead Accessibility Consultant, Informatica
On Thu, Aug 24, 2017 at 3:06 AM, Sarah Jevnikar < = EMAIL ADDRESS REMOVED = >
wrote:
> Hi everyone,
> I'm about to start a project where previous accessibility tests have been
> run. I've been asked to give end-user feedback on complaints raised by the
> client who is concerned that WCAG 2.0 Level A failures are occurring.
>
> These prior tests used several versions of both JAWS and NVDA. I'm running
> JAWS 17 but also have 16 on my system, but tests were run with 16 and 18.
> Does it make sense to run tests with both versions? I'm not sure how many
> have upgraded to JAWS 18 given the price and existing compatibility.
>
> As for NVDA, the original tests were run with 2016.3, 2016.4, and 2017.3.
> I'm running 2017.3 on my machine, but am wondering if I need to test with
> the older versions. In my anecdotal experience it would appear that NVDA
> users tend to keep their software up to date but I don't want to miss
> things.
>
> Added to this, I know the recent versions of browsers (Chrome, Firefox and
> IE) that were used to test, but these versions were released after JAWS 16
> and NVDA 2016, so either tests have been happening since last year, or
> happening recently with old versions of screen readers. If the former, then
> proper notes about which version of SR has problems with which version of
> browser have not been kept to my knowledge.
>
> Does anyone have any thoughts on which SR versions to use?
>
> Thank you,
> Sarah
> > > > >
From: Beranek, Nicholas
Date: Thu, Sep 07 2017 7:09AM
Subject: Re: Testing with JAWS and NVDA - which versions are best?
← Previous message | Next message →
We test using the latest versions of NVDA and Firefox. We're a relatively small team for a company as big as Capital One that is constantly producing new features and capabilities that it would be unsustainable to test using all of the versions you mentioned. We test using this specific combination because it reveals to us the most accessibility issues. We've found that JAWS will sometimes compensate for bad code.
Once you get more comfortable looking at the code and knowing the standards, you can predict when things will go awry. Therefore, you won't need to spend as much time testing because you know what to expect.
Nick Beranek
Capital One
> On Sep 7, 2017, at 12:50 AM, Srinivasu Chakravarthula < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hello,
> I always test with latest version of NVDA and if something that needs
> second opinion, I use another screen reader such as JAWS.
>
> Regards,
>
> Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
> Website: http://www.srinivasu.org | http://serveominclusion.com
>
> Let's create an inclusive web!
>
> Lead Accessibility Consultant, Informatica
>
>
> On Thu, Aug 24, 2017 at 3:06 AM, Sarah Jevnikar < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Hi everyone,
>> I'm about to start a project where previous accessibility tests have been
>> run. I've been asked to give end-user feedback on complaints raised by the
>> client who is concerned that WCAG 2.0 Level A failures are occurring.
>>
>> These prior tests used several versions of both JAWS and NVDA. I'm running
>> JAWS 17 but also have 16 on my system, but tests were run with 16 and 18.
>> Does it make sense to run tests with both versions? I'm not sure how many
>> have upgraded to JAWS 18 given the price and existing compatibility.
>>
>> As for NVDA, the original tests were run with 2016.3, 2016.4, and 2017.3.
>> I'm running 2017.3 on my machine, but am wondering if I need to test with
>> the older versions. In my anecdotal experience it would appear that NVDA
>> users tend to keep their software up to date but I don't want to miss
>> things.
>>
>> Added to this, I know the recent versions of browsers (Chrome, Firefox and
>> IE) that were used to test, but these versions were released after JAWS 16
>> and NVDA 2016, so either tests have been happening since last year, or
>> happening recently with old versions of screen readers. If the former, then
>> proper notes about which version of SR has problems with which version of
>> browser have not been kept to my knowledge.
>>
>> Does anyone have any thoughts on which SR versions to use?
>>
>> Thank you,
>> Sarah
>> >> >> >> >>
> > > > The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
From: Jim Homme
Date: Thu, Sep 07 2017 7:29AM
Subject: Re: Testing with JAWS and NVDA - which versions are best?
← Previous message | No next message
Hi,
The thing that matters is whether the content is compliant. The best combination is NVDA 2017.3 with the latest version of Firefox. This is because NVDA shows the most pure accessibility information, and Firefox reveals the most accessibility information.
Jim
=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sarah Jevnikar
Sent: Wednesday, August 23, 2017 5:36 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Testing with JAWS and NVDA - which versions are best?
Hi everyone,
I'm about to start a project where previous accessibility tests have been run. I've been asked to give end-user feedback on complaints raised by the client who is concerned that WCAG 2.0 Level A failures are occurring.
These prior tests used several versions of both JAWS and NVDA. I'm running JAWS 17 but also have 16 on my system, but tests were run with 16 and 18. Does it make sense to run tests with both versions? I'm not sure how many have upgraded to JAWS 18 given the price and existing compatibility.
As for NVDA, the original tests were run with 2016.3, 2016.4, and 2017.3. I'm running 2017.3 on my machine, but am wondering if I need to test with the older versions. In my anecdotal experience it would appear that NVDA users tend to keep their software up to date but I don't want to miss things.
Added to this, I know the recent versions of browsers (Chrome, Firefox and IE) that were used to test, but these versions were released after JAWS 16 and NVDA 2016, so either tests have been happening since last year, or happening recently with old versions of screen readers. If the former, then proper notes about which version of SR has problems with which version of browser have not been kept to my knowledge.
Does anyone have any thoughts on which SR versions to use?
Thank you,
Sarah