[email protected] wrote:
Matthias wrote:
This is not true. I agree that the a11y support could be better, but you
should know the code better before you make claims like this.
I've looked at the code
Select an operating system --- any operating system.
Keep your monitor.
Throw away your standard keyboard.
Throw away your mouse.
Install a Perkins Keyboard
Then do the following:
* Create a ten page presentation using Impress;
* Create one drawing of a house, using draw;
* Write a five page letter.
Simply speaking, OOo uses the a11y support from Java and so only
That does not even begin to scratch the surface of what an a11y
program needs.
If there was another platform independent standard OOo wanted to support
There is a lot more to a11y than platform support.
As OOo is currently implemented, for complete support for Braille,
Moon Language, and ASL, there would need to be 5,000 selections for
locale data --- just for the currently supported languages. If OOo
supported all of the languages in ISO 639-4, there would be roughly
50,000 selections for language/locale data.
Do you want to have to scroll through that many selections, every time
you create a new style, in a different language?
The problem on Windows is that there is no native a11y support. When MS
That barely covers toggle switch input. [Can you even do toggle
switch input on a Linux Box?)
It doesn't cover Braille, ASL, or Moon Language output.
It doesn't cover the fact that the icons do not have meaningful names.
It doesn't cover the fact that for a person who can not use a mouse,
Navigator is a non-existent tool.
It doesn't cover the fact that OOo does not have full keyboard menuing.
Those are why I said OOo needs a complete rewrite from the ground up.
a11y is not something that can be retrofitted into a program. It has
be designed into a program from day one. OOo was not designed with
a11y in mind.
xan
jonathon
I would like to give Brandon something which may be useful to him.
This does seem to be a complex subject and, from my superficial
research, it seems that OpenOffice along with others is working on it.
OpenOffice has an Accessibility Project and its home page is
http://ui.openoffice.org/accessibility/index.html
The page dealing with assistive technology is
http://ui.openoffice.org/accessibility/disabilities.html
There are mailing lists. To subscribe, you first have to register with
OpenOffice here:
http://www.openoffice.org/servlets/Join
The mailing lists are on this page:
http://ui.openoffice.org/servlets/ProjectMailingListList
You have to login (after registering) before you can subscribe to a
mailing list.
None of that deals with the immediate requirement, of course, but it
seems to be the best that OpenOffice can offer at present.
As for testing KOffice, possibly, when time permits. I'm not sure that
I even have the hardware required. Kde does have a text to speech tool
called Kmouth but I seem not to have any software to use with it.
Having made the transition from M$ to Linux, I would never return.
There is a lot to learn but I believe it is worth the effort.
--
If you're seeking, check out http://www.rci.org.au
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
