E-mail List Archives

Search E-mail List Archives for

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

From: Jeevan Reddy
Date: Wed, May 03 2017 11:55PM
Subject: Browser &Screen reader combination for common UI component testing
No previous message | Next message →

Hi Friends
Hope All of you doing well!
we have a repository of common UI components where all of our products
consumes these components.
What are the browser and Screen reader combinations we need to
consider for a11y testing as per ARIA design patterns? Latest IE with
JAWS16+, NVDA with firefox and safari with voiceovere enough? or we
need to consider other browser combinations as well?.

Thanks

--
Best Regards,
Jeevan Reddy,
Lead Accessibility Consultant,
Edgeverve Inc,
Bangalore, India.

From: Rakesh P
Date: Thu, May 04 2017 5:26AM
Subject: Re: Browser &Screen reader combination for common UI component testing
← Previous message | Next message →

Jeevan,

I recommend the following combination of SR vs Browsers.
<http://www.maxability.co.in/2017/02/screen-reader-and-browser-combination-for-accessibility/>;However
if your target is to to see the usage statistics look at Web AIM SR survey
6. <http://webaim.org/projects/screenreadersurvey6/>;

On Thu, May 4, 2017 at 11:25 AM, Jeevan Reddy < = EMAIL ADDRESS REMOVED = >
wrote:

> Hi Friends
> Hope All of you doing well!
> we have a repository of common UI components where all of our products
> consumes these components.
> What are the browser and Screen reader combinations we need to
> consider for a11y testing as per ARIA design patterns? Latest IE with
> JAWS16+, NVDA with firefox and safari with voiceovere enough? or we
> need to consider other browser combinations as well?.
>
> Thanks
>
> --
> Best Regards,
> Jeevan Reddy,
> Lead Accessibility Consultant,
> Edgeverve Inc,
> Bangalore, India.
> > > > >

From: Tim Harshbarger
Date: Thu, May 04 2017 2:46PM
Subject: Re: Browser &Screen reader combination for common UI componenttesting
← Previous message | Next message →

Jeevan,

If the common UI components are also used on mobile devices, I would suggest adding at least a mobile platform to your test environment. Which mobile platforms you pick will depend on your likely users and your testing resources.

From: Jeevan Reddy
Date: Fri, May 05 2017 10:02AM
Subject: Re: Browser &Screen reader combination for common UI component testing
← Previous message | Next message →

Thanks Tim and Rakesh.
Our UI components are catering only to desktop web.
How about using NVDA with Chrome? These days chrome has good a11y support,
any thoughts are appreciated.
Thanks
Jeevan

On Fri, May 5, 2017, 2:16 AM Tim Harshbarger <
= EMAIL ADDRESS REMOVED = > wrote:

> Jeevan,
>
> If the common UI components are also used on mobile devices, I would
> suggest adding at least a mobile platform to your test environment. Which
> mobile platforms you pick will depend on your likely users and your testing
> resources.
>
>

From: Tim Harshbarger
Date: Fri, May 05 2017 1:50PM
Subject: Re: Browser &Screen reader combination for common UI component testing
← Previous message | No next message

Jeevon,

I am not sure I can answer this question for you since I expect it comes down to available resources.

Given infinite resources to test and fix accessibility defects, I would test with every possible combination of browser, AT, and platform. That way no matter what At, browser, and platform someone is using, I would feel fully confident they were getting a good experience. But we never have access to infinite resources.

One way I might try to figure out an answer is imagine testing is complete and I found defects unique to all combinations. Given that all the defects have the same level of impact on the user, how would I prioritize fixing them with the resources on hand? Which defects would we be able to fix in a reasonable amount of time? Which fixes would likely benefit the users most? Most?

Typically, at this point with most other types of defects, people would be trying to figure out which defects impacted the most people to the greatest degree. Those would be first to be fixed. But we really don't have hard data that tells us how many people are using which combinations. The best we can do is extrapolate a guess based on whatever information we can gather.

There is also the question about how much accessibility support a user agent or platform needs to provide before it becomes a viable addition to the testing environment. So there is always some guess work (at least for me) on when the accessibility support is good enough.

Unfortunately, no answer, but hopefully some thoughts that might help you figure what you want to do.

Thanks,
Tim