RE: requirements to test with Jaws in different organizations

Karen,



I would love to understand your issue better.

That may help us all understand your assumptions and assertions which seem
to be generalizations and may be fortifying discriminatingly to all those
who have spent thousands of hours and years of hard work, late nights and
long hours making sure that websites and mobile apps are complying with the
WCAG guidelines to the best of our knowledge, experience and many with
interactions with many disabled individuals and may even have some of those
disables our selves.



I don’t understand what you mean by “mandating a screen reader,

also makes the software speech included in tools like jaws physically

harmful,”



and

“that I need to fit their definition of disability to get access..even if
doing so could

result in my hospitalization.”



And

“the practice of one tool fits all testing stopped.”



And

“You are teaching the companies for which you work how to discriminate,

even if not especially when you claim a majority using your tools.

After all, using majority as a measure still fortifies discrimination on

large scales world wide.”



Alan Smith



*From: *Karen Lewellen <klewellen@shellworld.net>
*Sent: *Monday, July 5, 2021 5:38 PM
*To: *bryan rasmussen <rasmussen.bryan@gmail.com>
*Cc: *w3c-wai-ig@w3.org
*Subject: *Re: requirements to test with Jaws in different organizations



speaking personally,

My understanding is that wacg principles are to be browser agnostic, and

are  rooted in interaction not tool.

As someone experiencing a disability that while mandating a screen reader,

also makes the software speech included in tools like jaws physically

harmful, it is frustrating  being told by well  meaning companies who

themselves were told that Jaws testing was suitable, that I need to fit

their definition of disability to get access..even if doing so could

result in my hospitalization.

I respect your desire to make your job easier, but  given no single

person's tools apply to another person's body, my own included, I would

truly appreciate it if the practice of one tool fits all testing stopped.

You are teaching the companies for which you work how to discriminate,

even if not especially when you claim a majority using your tools.

After all, using majority as a measure still fortifies discrimination on

large scales world wide.

Speaking personally, of course.

Karen







On Mon, 5 Jul 2021, bryan rasmussen 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

>

>