Got it Stuart, now everithing is clear. So as I supposed I was already using the right configuration (JRE 1.7.0 with no access bridge)
Unfortunately JAWS in my organization is still The screen reader and a switch to NVDA has been evaluated and postoponet when it will be more mature (at least 1 or 2 years). NVDA works great when everithing works, and as a portable screen reader, but Jaws is more capable of making its way trough deep (inaccessible) space. thx Jacopo -----Messaggio originale----- Da: V Stuart Foote [mailto:vstuart.fo...@utsa.edu] Inviato: martedì 25 marzo 2014 16.17 A: ooo-...@incubator.apache.org Oggetto: Re: R: the right Accessibility configuration Deyla, Actually Windows accessibility in Apache OpenOffice no longer makes any use of the Java Accessibility Bridge to interface to the Java Accessibility API installed with a JRE. A native accessibility bridge for Windows has been implemented based on the IAccessible2 API. Apparently JAWS and OpenEyes do not yet correctly support global use of the IAccessible2 API, as I believe they have in the past implemented support as program moudules, i.e. for the old IBM Symphony implementation of IA2. At present, the NVDA project provides more functional support for the IAccessible2 API standard. Stuart -- View this message in context: http://openoffice.2283327.n4.nabble.com/the-right-Accessibility-configuration-tp4660607p4660618.html Sent from the Development mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
