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

Hi :)  
Accessibility features usually work reasonably well in LO but they rely on Java so they do go wrong 
a bit too often.  Recently Stuart Foote put together an Faq page on how to fix it when it goes 
badly wrong.  

The docs team are possibly about to expand the next version of their guides to include links to 
this Faq
and maybe a brief line or so to help experienced experts work it out for themselves.  

Annoyingly IBM gave all their accessibility code to Apache and that was quite a significant chunk 
of the accessibility stuff.  Since Apache have it there might be licensing problems about trying to 
get the code into LO.  I can't imagine the LO devs being happy about the need to re-write it in 
Python or something before getting up to the same level as what is already out there!  However, 
since the IBM stuff seems to depend heavily on Java it's work that they would probably have done 

Anyway.  It's good for us that a total star (Stuart) from the accessibility mailing list has put 
together the Faq-page about getting the "Java Accessibility Bridge" working.  So, now we can show 
off that a small(ish) but significant amount of accessibility stuff will work.  

Regards from
Tom :)  

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.