Date: prev next · Thread: first prev next last

Michael Stahl and Dennis Hamilton are right wrt IA2 CWSes listed below.

accfixes2 is ready for QA, but was intended to be integrated _after_ 3.4 just to make sure we don't break Accessibility on some other platform short before the release.

But feel free to integrate, and do some testing on Windows, GNOME and Mac. It will not introduce any IA2 stuff.

accia2bridge is not critical to integrate, as this is Windows-only (UAA IA2 bridge) and can't break anything on other platforms. But it will remove the Java Accessibility stuff on Windows, so better do this as the last step.

accfixes3 was intended to be the last CWS with IA2 stuff. All remaining changes where in accstuff, and my plan was to migrate (adapted) changes from accstuff to accfixes3, or delete not wanted stuff in accstuff, and never integrate accstuff itself.

Unfortunately somebody already did it the other way round and moved a larger, not reviewed chunk of code from accstuff from accfixes3 (276449:e44059869aa9).

accstuff (+accfixes3 with 276449:e44059869aa9) still contains changes made in a way I wouldn't integrate them in OOo, but now it's up to other people to decide whether or not to integrate stuff as it is.

It's not up to me anymore to have an eye on OOo architecture. (But note that also the people "responsible" for the modules with remaining changes didn't want to integrate them as they are)

Once stuff above is integrated, there is still some minor work missing. I might be able to help on that, but I don't plan to do the integration work for accfixes*, at least not for LibreOffice, because there will be many conflicts. Integration into AOOo should be quite smooth.

For the remaining changes, I guess I would like to do it the same way like my old friend, the "Pseudo Engineer and itinerant idiot" ;) A little bit of poking around, hacking, and providing a patch compiled and tested only on my primary platform :)


PS: I don't read the mailings lists regularly, and the accessibility list is the only one I really look into. But chances to miss something are high. If you have questions on the OOo IA2 stuff here, and I don't answer them in a timely manner, drop me a note w/o cc-ing a mailing list so it will make it to my inbox.

On 09.09.2011 21:45, Michael Stahl wrote:
On 02.09.2011 11:56, Christophe Strobbe wrote:

The code is now available on Apache:
<>. Yesterday,
the Apache OOo blog published an article on developer education, so
the code should be ready for attempts to compile it on Linux:

Since we have a bug on IAccessible2 at
<>  I wanted to find
out where the code relevant to IAccessible2 can be found in the
repository at Apache and add some information about that to the bug.
Can anybody help?
(I have only browsed the repository in my web browser; I have not
checked out the code from SVN.)

the Apache SVN currently contains only the OOO340 head (i.e. everything
that was integrated until OOO340_m1).

apparently the IA2 stuff is in a not-yet-integrated CWS on the OOo HG

it currently looks like this (like most open CWSes) won't be integrated
into ApacheOOo for quite some time, as it is not in scope for the 3.4
release, and there is unfortunately some work to do first to comply with
Apache's annoying licensing policies etc.

there are some more not-yet-integrated CWSes that look a11y related:

but i've never worked on a11y myself, so don't ask me what the status of
any of this is.


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.