Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!samsung!olivea!oliveb!bunker!hcap!hnews!115!778!Chip.Orange
From: Chip.Orange@f778.n115.z1.fidonet.org (Chip Orange)
Newsgroups: misc.handicap
Subject: speech and windows
Message-ID: <16594@bunker.UUCP>
Date: 7 Jan 91 18:06:49 GMT
Sender: wtm@bunker.UUCP
Reply-To: Chip.Orange@f778.n115.z1.fidonet.org
Distribution: misc
Organization: FidoNet node 1:115/778 - COPH-2 (BGMS), Chicago IL
Lines: 25
Approved: wtm@bunker.UUCP

Index Number: 12668

[This is from the Blink Talk Conference]

My place of employment is likely to begin to convert to windows 386 3.0 
in six months or so, so I have been wondering exactly what I'm going to 
do for speech access.  As many of you know, I have written a graphical 
user int3erface speech program for the Amiga, which is an environment 
similar to that of MS windows, and it seemed like I was going to have to 
start down that road again, since I couldn't find anyone who was 
expecting to produce a windows speech program any time soon.  Then I 
contacted an old friend of mine an IBM, and he put me onto the head of 
the screen reader development project, who told me that they plan to 
start a version of screen reader for MS-windows next month, and it should 
be ready for beta-testing in six months or so.  In addition, you can now 
get an interface card to allow you to use the external keypad screen 
reader requires for control, so you no longer need a PS/2 machine to use 
screen reader.
     Just thought I'd pass this along for those of you in a similar bind.
  
     Chip Orange

--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!115!778!Chip.Orange
Internet: Chip.Orange@f778.n115.z1.fidonet.org