Making OpenOffice accessible means to make it usable by people regardless of their disabilities.
There are various Accessibility aspects: Keyboard navigation, scheming, AT support and much more.
Details can be found here: https://ui.openoffice.org/accessibility/whitepaper.html.
There are three strategies to make OpenOffice accessible:
Allow the user to control OpenOffice completely with the keyboard so that the use of a mouse is not necessary.
OpenOffice is already controllable in large parts via the keyboard. As open task remain for instance switching into and between dialogs and activating and deactivating OLE objects.
Keyboard enhancements comprise the support of keyboard like input devices that differ from standard keyboards. This support is covered by the operating systems that OpenOffice runs on.
Visual enhancements like enlarged and clearer fonts are already possible with the existing OpenOffice.
Assistive technology comprise such different devices like screen readers and braille terminals. There are several APIs that serve as common abstraction of the various AT input and output devices. We are aiming at the Java Accessibility API as the only truly operating system independent member of that group while at the same time keeping an eye on the Gnome Accessibility API. Both are very similar in the way they represent an application and the kind of information they provide for the individual parts of the (G)UI.
Our approach of supporting AT with the UNO Accessibility API is documented here in detail.
A list of AT known to work with OpenOffice is maintained on https://wiki.openoffice.org/wiki/Accessibility.
To participate in the work of making OpenOffice accessible, ask questions, or make comments you can use the dev@openoffice.apache.org mailing list.