WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Web applicationtesting

for

From: Jamous, JP
Date: Aug 5, 2016 6:08AM

Automate than manual evaluate.

That's what I always tell our developers.

1. With automation you get to eliminate issues faster, but you miss out on details.
2. With a SR, you get first-hand experience with what is going on. Here it is important to use both JAWS and NVDA to identify the differences.
3. Once you identify the difference, you can write your code or modify it to find the balance or sweet spot.

I also advise our devs to refrain from using ARIA unless necessary. I have seen heavy ARIA sites that either crash JAWS or Internet Explorer.

ARIA was developed to be like medics. In other words, it comes to the rescue when there is an urgency to get something working. Otherwise, you should always check with your doctor to stay away from emergency situations. That's where you use proper semantic.

With proper semantic, all ATs function properly. With ARIA, each team or SR has its own way of coming to the rescue. I hope that makes sense.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of sucharu
Sent: Friday, August 05, 2016 12:05 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Web applicationtesting

Hi,
As per my understanding, JAWS and NVDA behavior differently because of two facts 1. JAWS make some guess work in some situations like unlabeled forms 2. ARIA support is at different levels in both screen- readers So, I think JAWS is likely to skip the errors easily catchable by freely available automated accessibility testing tools like AXE, a- inspector.
So, Is to test with automated tools first and then with JAWS, a better approach?
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Sean Murphy
Sent: Friday, August 05, 2016 9:39 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Web applicationtesting

Sorry, you should test NVDA and Jaws on both of those browsers.

NvDA has been enhanced to work better with Firefox then IE. Jaws works better with IE and does work extremely well with Firefox.


> On 1 Aug 2016, at 9:22 PM, Jamous, JP < <EMAIL REMOVED> > wrote:
>
> 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.
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of sucharu
> Sent: Monday, August 01, 2016 5:46 AM
> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Web applicationtesting
>
> Dear listmembers,
> Can someone provide link to any resource about "screen- reader and browser combination: potential first choice"
> Best,
> Sucharu
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of surbhi Mudgal
> Sent: Sunday, July 24, 2016 3:45 PM
> To: <EMAIL REMOVED>
> Subject: Re: [WebAIM] Web applicationtesting
>
> 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 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.
>>
> > > archives at http://webaim.org/discussion/archives
> >
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
>