[ossrp-control] problems with retrofitting




Obviously no first version of any program is going to have everything that
everyone wants.  Still we must be careful not to overlook the problems of
retrofitting this screen reader for things like braille support.  As was
pointed out there are significant differences in interface design between
braille and speech output.  Most screen readers that had only speech to
start with took a long time to develop the high quality integrated speech
and braille output that users enjoy today.  It took JAWS until version 6 to
properly handle its flash messages produced by its own internal software.
While we do have to husband our resources, we really don't have thetime to
wait several versions to get it right.  The braille drivers can come later
but the initial product should really contain all the essentials for their
inclusion.  If the module for braille is produced later than the interface
may not include the ability to run the screen reader entirely with braille.
This is an absolute requirement for any deaf/blind person and only makes
sense when you consider the fact that since anyone acquiring a braill
display may well have used up their meager resources and it would be a real
shame if they still needed speech after that expense.  You have to have a
few more languages than just English.  This project is going on the
internet and some effort should be made even initially to accomodate a few
other languages.

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: