E-mail List Archives
Re: Web applicationtesting
From: Maxability Accessibility for all
Date: Jul 16, 2016 3:50AM
- Next message: Maxability Accessibility for all: "Re: Accessibility user testing"
- Previous message: Bhaskarjyoti Hazarika: "Re: wcag 3.3.4"
- Next message in Thread: surbhi Mudgal: "Re: Web applicationtesting"
- Previous message in Thread: Bossley, Pete: "Re: Web applicationtesting"
- View all messages in this Thread
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.
>
>
>
- Next message: Maxability Accessibility for all: "Re: Accessibility user testing"
- Previous message: Bhaskarjyoti Hazarika: "Re: wcag 3.3.4"
- Next message in Thread: surbhi Mudgal: "Re: Web applicationtesting"
- Previous message in Thread: Bossley, Pete: "Re: Web applicationtesting"
- View all messages in this Thread