Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

[tdf-discuss] Accessibility (was Java dependency)


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.

Is there a better alternative for Windows users?

And how can LibO be made more accessible in general for all users?

jonathon wrote:
For those that have accessibility requirements, the Java is mandatory.
OTOH, even with Java, LibO is not an accessible program. On the gripping
hand, all office suites fail accessibility requirements.

-- 
"I'm questioning my education
Rewind and what does it show?
Could be, the truth it becomes you
I'm a seed, wondering why it grows"
-- Pearl Jam, Education

-- 
Unsubscribe instructions: Email to discuss+help@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 ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.