[gui-talk] [j-say list] Re: FW: wireless access

Ankers, Dave (UK) Dave.Ankers at baesystems.com
Tue May 1 07:17:31 CDT 2007


Charles,

Please find comment below from someone who uses J-Say and a wireless
headset.
 
Dave

If you'd like to forward some of our comments to the list from which
this message originated I think that might be a good thing.

Here are my comments:

I've worked in the field of assistive technology for over ten years.
When I first entered this field the conventional wisdom was that speech
input was okay but only if you had absolutely no other choice.  I began
using Dragon Naturally Speaking when I started my current job at the VA
medical center in Birmingham.  We have plenty of veterans who are unable
to use their hands due to a variety of situations.  At this time the
J-Say interface is a effective and accurate method of using the
computer.  I have absolutely no problem using my hands.  However,
because of the work I've done with blind veterans who are also unable to
use the keyboard I have started using J-Say in my personal life.

I do this purely by choice, not necessity.  I do it because it's a
really effective way to use a computer and because I can work wherever I
like while using a wireless headset.  If I want to sit in front of the
fire and continue to listen to the movie, book, or TV show I've just
downloaded I can do that.  If the weather is nice and I want to lie in
the hammock on the front porch for a while and continue to listen to
whatever, or read the newspaper , or check my E-mail I can do that.  I
just get up and go, no strings, or wires, attachedAnd I do it because
I'ts fun..

The author of the message below is clearly speaking without possessing
the knowledge of that of which he speaks.





----- Original Message -----
From: "Charles Oppermann" <chuckop at exchange.microsoft.com>
To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
Sent: Tuesday, April 17, 2007 8:18 PM
Subject: Re: [gui-talk] wireless access


> Using your voice as the sole input mechanism when using speech output
is a 
> difficult task.  One of the problems is input accuracy.  As you speak,
the 
> system will mis-recognize occasionally, putting in words or phrases
you 
> didn't intend.  There is a correction user interface that is similar
in 
> concept to spell checkers.
>
> The keyboard is the most accurate input mechanism, and I would hazard
a 
> guess that is even true more so for blind and low-vision users.  It's
my 
> opinion that a screen reader user who can use a keyboard will find it
a 
> less frustrating.
>
> A major part of my work at Microsoft is on speech recognition (and
speech 
> output), so I would be interested in any of your own experiences.
>
> Charles Oppermann | Program Manager | Speech Components | Microsoft






********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************



More information about the gui-talk mailing list