W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

RE: Changing voices in screen readers Re: Múltiplas vozes em leitores de telas

From: Bryan Garaventa <bryan.garaventa@whatsock.com>
Date: Wed, 13 May 2015 10:24:04 -0700
To: "'Phill Jenkins'" <pjenkins@us.ibm.com>
Cc: "'WAI Interest Group'" <w3c-wai-ig@w3.org>
Message-ID: <000b01d08da1$9fc0fb20$df42f160$@whatsock.com>
Yup, confirmed on another Windows7 64bt machine, this is broken in JAWS16.


From: Phill Jenkins [mailto:pjenkins@us.ibm.com] 
Sent: Wednesday, May 13, 2015 9:53 AM
To: Bryan Garaventa
Subject: RE: Changing voices in screen readers Re: Múltiplas vozes em leitores de telas


currently using JAWS 15 and Win 7, no problems.   

However, I don't switch between SAPI, Eloquence and/or Vocalizer - I just customize the voice settings within the one speech
synthesizer engine. 

good question for Freedom 
Phill Jenkins, 

From:        "Bryan Garaventa" <bryan.garaventa@whatsock.com <mailto:bryan.garaventa@whatsock.com> > 
To:        Phill Jenkins/Austin/IBM@IBMUS 
Date:        05/13/2015 11:31 AM 
Subject:        RE: Changing voices in screen readers Re: Múltiplas vozes em leitores de telas 


Have you encountered an issue with doing this in the latest version of JAWS16 on Win7? I’m not sure if this is an issue on my system
or a bug in JAWS. 
1 Press Insert+Control+S 
2 Choose SAPI5 instead of Eloquence. 
This just messes with Eloquence instead of changing the voice, which occurs for all languages listed there. 
Just curious. I have JAWS15 installed on the same machine and it doesn’t have this problem. 
From: Phill Jenkins [ <mailto:pjenkins@us.ibm.com> mailto:pjenkins@us.ibm.com] 
Sent: Wednesday, May 13, 2015 6:56 AM
To: w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> 
Subject: Re: Changing voices in screen readers Re: Múltiplas vozes em leitores de telas 
you can try multiple voices with JAWS (screen reader) and MAGic (screen magnifier with speech), even in "40-minute demo mode". 
see  <http://doccenter.freedomscientific.com/doccenter2/doccenter/rs25c51746a0cc/voiceprofiles/02_voiceprofiles.htm>

For example, one can change the voice in context, such as for any of the following: 
Adjust combo box. The Adjust combo box defaults to All Contexts, but here you can also choose the following voices to change: 

*	PC Cursor Voice 
*	JAWS Cursor Voice 
*	Keyboard Voice 
*	Tutor and Message Voice 
*	Menu and Dialog Voice

So if one changed the settings for the voice for Menu and Dialogs, they would "sound different" from regular text on the page/app.
I've actually done this when training sighted users to user JAWS as a test tool so they "hear" a different voice for different
controls and labels vs regular text; kind of audio styling to match the visual styling.  As you can imagine however, the JAWS voice
is still odd sounding to the first time listener, so we emphasize the visible lists of links and controls list that JAWS displays. 

Having said all this, I still believe that 'voice settings' are generally the assistive technology's (AT's) and end user's
responsibility, and NOT the web author's.  Remember, we're not creating a one-size fits all audio version of a web site; authors and
developers are *enabling* non-visual access to a web app.  Enabling is both a design and coding practice. Novice screen reader users
will "turn on" all the vebosity so they can to "learn", while power screen reader users will turn off most of the verbosity
settings.  Quality AT like JAWS and MAGic allow the end user (and sighted testers) to create "profiles" that they can switch to in
different contexts.  
Phill Jenkins, 
IBM Accessibility, created 
'IBM Screen Reader for DOS' 
'IBM Screen Reader for OS/2' 
'IBM Home Page Reader' 
Received on Wednesday, 13 May 2015 17:24:36 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC