WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Web applicationtesting

for

From: Maxability Accessibility for all
Date: Jul 16, 2016 3:50AM


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 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.
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Caitlin Geier
> Sent: Friday, July 15, 2016 2:17 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Web applicationtesting
>
> 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 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
> >
> >
> >
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of surbhi Mudgal
> > Sent: Thursday, July 14, 2016 11:32 PM
> > To: <EMAIL REMOVED>
> > Subject: [WebAIM] Web applicationtesting
> >
> > 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.
> > > > > > > > > > > >
>
>
>
> --
> Caitlin Geier
> User Experience Designer
> <EMAIL REMOVED>
> > > > > > > > >