T. J. Brumfield wrote:
I'm moving this into another thread. Jonathon suggested that LibO fails at
accesibility requirements. Doing a few quick Google searches, it seems that
OOo and thusly LibO uses the Java Accessibility API to enable the use of
screen readers and braille devices. This is primarily used for Windows.
On Mac OSX, the built-in screen reader in the OS is used. On Linux, the
Gnome Accessiblity tools are used.
Yet the OOo wiki suggests the reason you must use the Java Accessiblity API
is that it is multi-platform, yet OOo doesn't appear to be using it on two
of their platforms.
When OOo was a Sun project I think the use of Java was a case of what is
called dog-fooding. With LO there is no longer any compelling reason to
use Java.
--
Unsubscribe instructions: Email to discuss+h...@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
