Date: prev next · Thread: first prev next last


Hello,

All read and understood.

Thanks for your explanation, I have to say it seems that oo and IBM are dragging there feet with this one.

I have been in touch with malt Timmerman over the last year or so but I have not really gotten anywhere.

I hope you will keep us vi users informed if you hear of ia2 support being added into the code.

The reason that accessibility is not switched on by default in oo is that it does take a bit longer because the program has to shake hands with access bridge and window's.

I am not a programer but I would like to have the program just work out of the box like sinthony does.

This code has been around for quite some time now and for some reason it seems that oo does not seem to want to get on and put it into the program.

The last time i asked about this on the oo list I was told that it will be ready when it's ready not very helpful. I look forward to hearing good news in the near future P.S I use nvda for window's an open source screen reader I am sure you have heard of it but just in case you can check it out..

On 08/09/2011 13:49, Christophe Strobbe wrote:
Hi Kevin, All,

(I'm answering Kevin's question in a separate thread.)

When I browsed the OpenOffice.org source code at
<http://incubator.apache.org/openofficeorg/source.html>, I found a lot
of Java Accessibility code but nothing that looked like IAccessible2
code (which should contain some names starting with IAccessible...).
Unless I looked in the wrong place, there is no IAccessible2 code that
can be reused by LibreOffice. I have asked where the IAccessible2 code
ended up on two mailing lists and contacted someone at IBM (i.e. the
person who seemed to have checked in most of the source code). I have
not received any answers, so I don't know what is going on. In my
opinion, this makes a rather strange impression, especially since IBM
reportedly donated that code to Oracle and an Oracle developer wrote in
June (on the Apache Incubator list) that he was quite sure it would find
its way to Apache OOo...

I hope Oracle and/or IBM will soon clarify the situation. As long as it
remains unclear if the IAccessible2 code will be released or not,
LibreOffice cannot decide whether it should reuse the code or reinvent
that particular wheel.

The LibreOffice bug about enabling AT support during the installation is
still open: <https://bugs.freedesktop.org/show_bug.cgi?id=39803>.


At 13:29 8-9-2011, Kevin Cussick wrote:
"(...) Can someone give a summary to how ia2 support is coming along? or
maybe not? i have heard it is now being worked on is this true? I would
like to be able to just download and install without going threw hoops
to get it working with the access bridge software. If ia2 is not being
worked on at the moment I think the accessibility switch should be on
buy default or if not during install you should be asked do you want
this switched on buy default? and do you want to install the access
bridge? this would be OK until such times the ia2 support that has been
in sinthony for a long time now makes its way into the current code with
thanks as always."


Best regards,

Christophe




--
All The Best
Kevin Cussick

--
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted

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.