E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 10 (In chronological order)

From: surbhi Mudgal
Date: Thu, Jul 14 2016 10:32PM
Subject: Web applicationtesting
No previous message | Next message →

Hi,



Good Day.



Looking for a very simple confirmation on testing a web page or web
application. Would just like to know if there is any basic standard rule
to test using different screen readers ( JAWS, NVDA, VOICE OVER) or it
depends up on the user comfort.



And if any particular procedure to be followed can anyone please help me
understand the same.







Thanks & Regards,

Surbhi Mudgal.

From: Maya.Sellon
Date: Fri, Jul 15 2016 2:06AM
Subject: Re: Web applicationtesting
← Previous message | Next message →

Hi Surbhi,

I'm keen to hear what the others have to say, but we outsourced our testing to a professional company in the UK once and I asked them a very similar question. They told me that at a minimum I should test with either JAWS + Internet Explorer or NVDA+FireFox. I was told that for web pages at least, NVDA was every bit as good as JAWS.

I think the more systems you can test with, the better. I've seen test results from Dragon Speaking Naturally that were blockers that didn't appear with any other AT testing. But what you can do also depends on time and resource, of course.

I don't know if it's good enough, but given the time and resource that I have, I always test for desktop and mobile (NVDA + VO). And for larger projects, I reach out to the internal community and ask for volunteer to help me test with the AT they use as well.

regards,
Maya

From: Andrews, David B (DEED)
Date: Fri, Jul 15 2016 8:26AM
Subject: Re: Web applicationtesting
← Previous message | Next message →

I went to a session at CSUN this year, about this very topic. Don't remember who gave it, (getting old I guess,) and as I recall they of course recommended testing as many combinations as you could, which is good advice. As I recall, they said if you could only test one combo your best bet was NVDA/Firefox. I would add if you can add a second, it should probably be IE/JAWS.

You can go too far down this rabbit hole, or simplify it too much, from my experience.

Dave



David Andrews | Chief Technology Officer
Department of Employment and Economic Development
State Services for the Blind, 2200 University Ave. W., Suite 240, St. Paul MN 55114
Direct: 651-539-2294 | Mobile: 612-730-7931
Web | Twitter | Facebook

From: Caitlin Geier
Date: Fri, Jul 15 2016 12:16PM
Subject: Re: Web applicationtesting
← Previous message | Next message →

Dylan Barrell (Deque's CTO) gave a talk awhile back about automated testing
<https://vimeo.com/151658306> which includes data about some of Deque's
research around browser / AT combinations. About ~15 minutes into the video
is our browser / AT testing matrix. Essentially, while it's ideal to test
as many combinations as possible, there's usually a limited amount of time
in which to do testing. The reasoning behind targeting certain combinations
over others is to get the most bang for your buck - to catch the most
issues in the least amount of time. The combinations used most frequently
at Deque are based on support (NVDA is better on Firefox than on Chrome,
for example) and on accuracy (NVDA presents what's actually there, while
JAWS sometimes guesses).

I haven't been able to find an accessible version of the matrix in the
video. The top browser/AT combinations listed are:

- Firefox (for Windows) / keyboard
- Firefox (for Windows) / NVDA
- Safari / Voiceover (desktop and mobile)
- Firefox (for Android) / Talkback
- Firefox (for Linux) / Orca


On Fri, Jul 15, 2016 at 10:26 AM, Andrews, David B (DEED) <
= EMAIL ADDRESS REMOVED = > wrote:

> I went to a session at CSUN this year, about this very topic. Don't
> remember who gave it, (getting old I guess,) and as I recall they of course
> recommended testing as many combinations as you could, which is good
> advice. As I recall, they said if you could only test one combo your best
> bet was NVDA/Firefox. I would add if you can add a second, it should
> probably be IE/JAWS.
>
> You can go too far down this rabbit hole, or simplify it too much, from my
> experience.
>
> Dave
>
>
>
> David Andrews | Chief Technology Officer
> Department of Employment and Economic Development
> State Services for the Blind, 2200 University Ave. W., Suite 240, St. Paul
> MN 55114
> Direct: 651-539-2294 | Mobile: 612-730-7931
> Web | Twitter | Facebook
>
>
>
>
>

From: Bossley, Pete
Date: Fri, Jul 15 2016 6:50PM
Subject: Re: Web applicationtesting
← Previous message | Next message →

We always test with NVDA + Firefox because that tends to get us a good idea of actual accessibility via web standards. We have seen cases where a site looks okay in JAWS but is not, JAWS just happens to be guessing correctly on labels and such. We will test with JAWS and IE when we are dealing with anything flash based.
As far as mobile testing, that is always iOS/Voice Over and usually some Android + Talkback as well.

From: Maxability Accessibility for all
Date: Sat, Jul 16 2016 3:50AM
Subject: Re: Web applicationtesting
← Previous message | Next message →

I second Caitlin . If you have only one combination time available go for
NVDA with firefox on Windows. As others rightly pointed JAWS try guessing
and provide accurate information to the user overwriting the source code.
For second combination if you have time and client requests JAWS and IE on
windows.
For mobile Safari and Voiceover for IOS and Talkback and firefox on
Android. I see very good accessibility support on Chrome on Android but
have not really checked any website.

Hope this helps.

On Sat, Jul 16, 2016 at 6:20 AM, Bossley, Pete < = EMAIL ADDRESS REMOVED = > wrote:

> We always test with NVDA + Firefox because that tends to get us a good
> idea of actual accessibility via web standards. We have seen cases where a
> site looks okay in JAWS but is not, JAWS just happens to be guessing
> correctly on labels and such. We will test with JAWS and IE when we are
> dealing with anything flash based.
> As far as mobile testing, that is always iOS/Voice Over and usually some
> Android + Talkback as well.
>
>
>

From: surbhi Mudgal
Date: Sun, Jul 24 2016 4:14AM
Subject: Re: Web applicationtesting
← Previous message | Next message →

Hi all,
Good day.

Thank you so much for the valuable responses.

Thanks & regards,
surbhi Mudgal.

On Fri, Jul 15, 2016 at 10:02 AM, surbhi Mudgal < = EMAIL ADDRESS REMOVED = >
wrote:

> Hi,
>
>
>
> Good Day.
>
>
>
> Looking for a very simple confirmation on testing a web page or web
> application. Would just like to know if there is any basic standard rule
> to test using different screen readers ( JAWS, NVDA, VOICE OVER) or it
> depends up on the user comfort.
>
>
>
> And if any particular procedure to be followed can anyone please help me
> understand the same.
>
>
>
>
>
>
>
> Thanks & Regards,
>
> Surbhi Mudgal.
>

From: sucharu
Date: Mon, Aug 01 2016 4:46AM
Subject: Re: Web applicationtesting
← Previous message | Next message →

Dear listmembers,
Can someone provide link to any resource about "screen- reader and browser combination: potential first choice"
Best,
Sucharu

From: Sean Murphy
Date: Mon, Aug 01 2016 4:52AM
Subject: Re: Web applicationtesting
← Previous message | Next message →

Voice over on the Mac and iOS

Jaws NVDA on the windows platform using IE and Firefox

Sean

Sent from my iPhone

> On 1 Aug 2016, at 8:46 PM, sucharu < = EMAIL ADDRESS REMOVED = > wrote:
>
> Dear listmembers,
> Can someone provide link to any resource about "screen- reader and browser combination: potential first choice"
> Best,
> Sucharu
>
>

From: Jamous, JP
Date: Mon, Aug 01 2016 5:22AM
Subject: Re: Web applicationtesting
← Previous message | No next message

Sucharu,

As suggested, but here is a more solid approach.

JAWS with Internet Explorer
NVDA with FireFox
VoiceOver with Safari on Mac, iPad and iPhone

If you cover the above, you can be in a great shape.