[ossrp-control] Re: screen reading information

Step 1:

Show the need (which I have done.)

2. Find committed minds to examine ways in which it indeed can be done. There are many example examples of hardware chips which have programs, including speech built into them without dependence on hard drives and the like.

And what, indeed, is your problem with a dedicated device, and we are not talking about anything near the bulk and expense of a Braille embosser.

I am sure that there are indeed minds, possibly even as powerful and experienced as your own, who can consider this dilemma in a posative and constructive light.

Hi Doug,

Well a dedicated device is different ... Any braille printer or what not can
do that these days, but the problem is things like tracking and so on and so
forth ... It just reads:

You spoke of prerecorded messages ... Where are you going to put these
messages?

How are you going to capture those keystrokes?

And how will you deal with dynamic information such as harddrive size,
whether a menu option is selected or not, and so on and so forth?

Take care,
Sina

-----Original Message-----
From: ossrp-control-bounce@xxxxxxxxxxxxx
[mailto:ossrp-control-bounce@xxxxxxxxxxxxx] On Behalf Of Doug Parisian
Sent: Tuesday, April 26, 2005 6:38 PM
To: ossrp-control@xxxxxxxxxxxxx
Subject: [ossrp-control] Re: screen reading information


----- Original Message -----
From: "Sina Bahram" <sbahram@xxxxxxxxx>
To: <ossrp-control@xxxxxxxxxxxxx>
Sent: Tuesday, April 26, 2005 4:18 PM
Subject: [ossrp-control] Re: screen reading information Hey, I'm the new kid
on the block.

Sina, seems I recall a device called the "Speaqualizer" Which would read
everything from the bios on up to DOS (yes, before windows, in the days of
the steam engine.) Since the bios consists of a finite number of words and
selections, would it not be possible to use a chip with pre-recorded text
and have the arrow, tab, etc, invoke the appropriate messages?

that is actually technically impossible, I'm afraid.

You see: there's litterally nothing to load from. No ram, no
harddrive, no CD, no thumb drive, no USB device, no firewire, ...
Absolutely nothing exists at bios time.

Take care,
Sina

________________________________

From: ossrp-control-bounce@xxxxxxxxxxxxx
[mailto:ossrp-control-bounce@xxxxxxxxxxxxx] On Behalf Of Dan Tonge
Sent: Tuesday, April 26, 2005 2:32 PM
To: ossrp-control@xxxxxxxxxxxxx
Subject: [ossrp-control] Re: screen reading information


It would be wonderful if a screen reader could be loaded early enough
so that we could use the PC parameters.  I know that is not the
correct name, but I can't think of it right now, but it is the mode
you can go into to make bios and other adjustments right at bootup time.

Dan T

----- Original Message -----
From: Tink Watson <mailto:tink@xxxxxxxxxx>
To: ossrp-control@xxxxxxxxxxxxx
Sent: Tuesday, April 26, 2005 5:35 AM
Subject: [ossrp-control] Re: screen reading information

Naama,

    This isn't really my field, but I suspect it would be difficult to
achieve this. Safe mode works by prohibiting drivers from loading,
whether sound drivers, technology or application specific drivers.
Without these I imagine it would be tricky, even impossible to get a
screen reader loaded and running.

    It certainly would be nice though, the inability to access the
bios, safe mode and other precursor environments is one of the biggest
irritations of using a screen reader.

Tink.
----- Original Message -----
From: "Naama Erez" <diva2@xxxxxxxxxxxxxxxx>
To: <ossrp-control@xxxxxxxxxxxxx>
Sent: Tuesday, April 26, 2005 11:20 AM
Subject: [ossrp-control] Re: screen reading information


> Just wondering, and that can be because my knowledge about this is

> limited, is there any type of screen reader, or any possibility
for a
> screen reader to operate in safe mode?
> ----- Original Message -----
> From: "Will Pearson" <will-pearson@xxxxxxxxxxxxx>
> To: <ossrp-control@xxxxxxxxxxxxx>
> Sent: Monday, April 25, 2005 8:18 PM
> Subject: [ossrp-control] Re: screen reading information
>
>
>> Hi Juan,
>>
>> As far as I know, Beth Mynat's and Keith Edward's paper is the
only one
>> on
>> how screen readers work.  There's been various ones written on
screen
>> reader
>> design, such as a comparison paper written by Beth Mynat et al in
1994,
>> which you can download from the publications section of the
Everyday
>> Computing Lab's website, which is part of the main GA Tech site.
There's
>> also been work done by Alistair Edwards at the University of
York, in the
>> UK, Steve Brewster from the University of Glasgow, in the UK,
various
>> people
>> at the University of Toronto, in Canada, but these have mainly
focused on
>> design rather than implementation.  I did hear that Prof. Gary
Bishop at
>> the
>> University of North Carolina was developing a new type of screen
reader,
>> based more around communication with the user, and any
information on
>> this
>> will likely be on the UNC web site at:
>> http://cs.unc.edu/research/assist
>>
>> Will
>> ----- Original Message -----
>> From: "Juan Hernandez" <juanh@xxxxxxx>
>> To: <ossrp-control@xxxxxxxxxxxxx>
>> Sent: Monday, April 25, 2005 10:17 AM
>> Subject: [ossrp-control] screen reading information
>>
>>
>>> Hello everyone,
>>> First I am glad to say that a project of this kind has finally
started.
>> I've discussed this type of project with other people, and have
written
>> papers and such  for my course work at the univercity, on the
research
>> and
>> development of a free or extremely low cost screen reading
solution.
>>>
>>> I have quite a bit of coding background, but none in the screen
reading
>> area.
>>>
>>> I have downloaded the paper written by: Mynatt, E.D., and
Edwards, W.K.
>> (1992). " Mapping guis to auditory Interfaces, but I would like
to know
>> if
>> anyone has any other information on screen reading development,
consepts,
>> theory, etc?
>>>
>>> Again, I am glad OSAT has started, and I hope to help as much as
I can
>>> in
>> the future.  Thanks
>>>
>>> Juan Hernandez
>>> San Diego, California
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> To post to the list, send a message to:
>> ossrp-control@xxxxxxxxxxxxx
>> To unsubscribe, send a message to:
>> ossrp-control-request@xxxxxxxxxxxxx
>> and set the subject field of the message to "unsubscribe"
(without the
>> quotes
>>
>>
>
> To post to the list, send a message to:
> ossrp-control@xxxxxxxxxxxxx
> To unsubscribe, send a message to:
> ossrp-control-request@xxxxxxxxxxxxx
> and set the subject field of the message to "unsubscribe" (without
the
> quotes
>
>

To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the
quotes





To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the
quotes


To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the
quotes



To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the quotes


To post to the list, send a message to:
ossrp-control@xxxxxxxxxxxxx
To unsubscribe, send a message to:
ossrp-control-request@xxxxxxxxxxxxx
and set the subject field of the message to "unsubscribe" (without the quotes

Other related posts: