What actions to enhance a11y supprt at LOdev 4.0?

I'll throw this out for the Dev community to mull over.

The apparent ESC decision to accelerate adoption of LibO 4.0 and not release
LibO 3.7 would seem to eliminate a potential logical break point for
implementation of several outstanding /a11y/ accessibility changes. Notably
getting the Windows client off of the Java Access Bridge and onto a "native"
bridge implementing IAccessible2 API.

Apache OpenOffice will roll out their 4.0 release with IAccesible2 support
from the /winaccessibility IBM Symphony contribution.

Has there been any effort yet on migrating under ALv2 the  /winaccessibility
contribution from Apache svn to git for  a git build?

And while undertaking integration of a native IAccessibile2 for windows,
would seem to be an excellent time to rework the UNO Accessibility modules
to add additional roles and more completely implement outstanding features
from the /a11y/ ATK/AT-SPI specifications and possibly exposing roles to
Apple NSAccessibility or even Microsoft UIA.

Stuart



--
View this message in context: 
http://nabble.documentfoundation.org/What-actions-to-enhance-a11y-supprt-at-LOdev-4-0-tp4018095.html
Sent from the Dev mailing list archive at Nabble.com.