Re: requirements to test with Jaws in different organizations

Bryan,

The main reason that I can think of to test with JAWS *as well as* NVDA and
Voice Over is that JAWS was the most popular screen reader, by far, in
WebAIM's most recent
Screen Reader User survey <https://webaim.org/projects/screenreadersurvey9/>.
It should not add significant time to the testing process, in my
experience. My team does not usually go through the entire website with
screen readers, but instead uses them for spot checks when there's an odd
structure and we're not sure how it will work with screen readers, and to
create screencasts to illustrate issues such as multiple links that have
the same accessible text. As Steve noted, most WCAG conformance problems
can be identified by other means; I have found that learning to navigate
with a screen reader was most valuable for helping me know what problematic
code patterns to look for in relation to specific kinds of webpage
structures.

-Annie

On Mon, Jul 5, 2021 at 1:57 AM bryan rasmussen <rasmussen.bryan@gmail.com>
wrote:

> Hi,
>
> This might be slightly off for the list, but don't know where else to
> ask that would be good. So I am working on a project for an online
> education platform that wants to move into the U.S market.
>
> The platform would like to limit testing at least part of the
> development process to nvda and voiceover, to decrease costs /
> workload, I personally would like to test with -Jaws all the time but
> often one can't for various reasons. So does anyone have a pattern for
> how they do periodic testing with Jaws in such a way as to decrease
> workload). And more importantly if anyone knows of any organizational
> / governmental regulations requiring testing with Jaws that would
> affect the educational market in the U.S?
>
> Thanks,
> Bryan Rasmussen
>
>

-- 
Annie Heckel

Lead Accessibility Auditor
Online ADA <https://onlineada.com/>