[ossrp-control] Re: Features So Far

Hi,

Here's my two cents worth:

1.  Dictionaries:
Graphics, Colour, pronunciation, phrase and character.

2.  Magnification
The ability for partially sighted to use the screen reader.

3.  Scripting:
I agree with Jamal for the power user to get the best out of the screen reader 
we should look at a commercial scripting language.  This does not mean that 
other easier methods should not be implemented.  On this front, the screen 
reader should work with multiple languages and should be highly configureable.

4.  Command prompt:
The ability to work with the command prompt.  We should also have the ability 
to use software speech in the command prompt.

5.  TTS:
The ability to use voices from more than one TTS engine similtaneously, such as 
Kurzweil.  Language switching should be done on the fly.

These are just some requirements from some one that comes from Africa and see 
all these problems on a daily basis.

Thanks.
  ----- Original Message ----- 
  From: Will Pearson 
  To: ossrp-control@xxxxxxxxxxxxx 
  Sent: Wednesday, April 27, 2005 12:02 PM
  Subject: [ossrp-control] Features So Far


  Hi,

  Here's my understanding of the important features that should be investigated 
for version 1.  It doesn't feature everything, but then there'll be versions 
after 1 in which more things can be brought in.

  Functional requirements:
  * ability to read *windows* login screen
  * ability to work with widely used types of applications, e.g. word 
processors, spreadsheets
  * support for TTS engines that use the SAPI interface, as some of these 
provide clearer speech than current formant synthesisers
  * ability to use mouse or equivalent functionality
  * must work with User Interface Automation
  * ability to update components over the web
  * support for Braille devices

  Architectural requirements:
  * based on .Net Framework/WinFX
  * component based architecture

  * Research requirements
  * investigate mechanisms to provide more efficient interaction mechanics
  * investigate techniques to convey all the semantic information contained 
within a GUI through auditory and tactual/haptech transmission media.
  * investigate means for clearer speech
  * investigate perceptual psychology techniques for semantic conversion of web 
based graphical turing tests to text

  Project management requirements:
  * risk analysis
  * avoid scope creep
  * requirements management
  * beta 1 to be made publically available April 2006

  These are fairly high level requirements, and if anyone feels anything is 
being missed or would like to include anything, then say now.

  Will

Other related posts: