Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!bunker!wtm
From: campbell%hpdmd48@hplabs.HP.COM (Gary Campbell)
Newsgroups: misc.handicap
Subject: Re: Vocal-Eyes quick review
Message-ID: <13780@bunker.UUCP>
Date: 4 Sep 90 02:05:24 GMT
References: <13690@bunker.UUCP>
Sender: wtm@bunker.UUCP
Reply-To: campbell%hpdmd48@hplabs.HP.COM (Gary Campbell)
Distribution: misc
Lines: 26
Approved: wtm@bunker.UUCP
Fidonet: Blink Talk Conference

Index Number: 10040

A possible feature for whatever screen reader writer wants to
consider it:  I haven't investigated the architecture of Windows
yet, but I have thought of how we might try to gain access to it.
If there were a place in the architecture where a user-supplied
driver could be inserted that could intercept text before it turns
into bits, one might be able to make a fake screen buffer of text
that would follow the bitmap screen.  If the screen reader had an
option that would allow the user to specify an arbitrary address
for the video memory, then someone who came up with such an
adaptation for Windows or anything else could tell the screen
reader to look at this fake video buffer instead of the screen.

I also think that the ability to programatically execute speech
reader functions would allow someone to write programs which could
control the speech system to make an integrated solution without
reimplementing screen reading functions.  One could, for example,
set a window to a particular area of the screen needed for a given
program function, etc.  The access could be an interrupt, possibly
a user-specified one to allow one to avoid something used by
another program.

--
Gary Campbell
campbell%hpdmd48.BOI.HP.COM@hplabs.HP.COM