MozBraille
| resources: | Home Mailing List Documentation Installation Source Code Members Bugs Screenshots |
|---|
What's New
- MozBraille 0.1 is ready. Be careful, it's a beta version. click here
Other Stuff
- Of course we need help so ... send me an email.
- libbraille.org also needs help so if you want to develop some drivers for Braille terminal, click here.
Partners
Overview
MozBraille is an extension to transform Mozilla or Firefox to a stand alone accessible Internet browser designed for blind or partially sighted users . So with mozBraille you don't need a third part program like a screenreader. MozBraille offers its users three displays or outputs :
- A Braille output on a braille terminal,
- A text to speech output,
- A big characters view.
MozBraille is a part of the VICKIE project. The main goal of this project is to create an electronic school bag for visually impaired children. So the main output is the Braille and the less important is the text to speech because students have to listen their teacher ;-).
Note : MozBraille is a beta version, so there are lot of features to add. At the moment, blind or a partially sighted users can't use this software alone.
Main Features
At the moment, MozBraille :- Supports Microsoft SAPI 5 text to speech library. So you can use almost all speech engines under Windows. For more information on SAPI click here.
- Supports libbraille library to drive Braille terminals. So MozBraille supports over 30 Braille displays such as Alva, BrailleLite, brailleNote, Eurobraille, handytech, once, vario... To have all devices click here.
- Displays simple xhtml pages without table.
- Has a fake XUL Braille terminal for developers who don't have a terminal.
- Users can configure how XUL or HTML elements are displayed on the three views.
- Manages the caret movements and selection on the Braille view.
My TODO list
- Creation of the "big character" view output. The "big character" view doesn't work to date.
- Gnome Speech supports. There is no text to speech output under Linux to date.
- Manage more html and XUL tags.
- Improve navigation in XUL and HTML documents.
- Improve time reactions.
- Use more and more Mozilla' accessibility layer features.
- Use CSS files to display node on the three views.
- Change JavaScript XPCOM objects in C++, to have a better speed of execution.