>>On 03.04.2014 17:55, David Goldfield wrote: >> I’m wondering if someone else who is using the NVDA screen reader could >> confirm the following issue. >> NVDA has a command which allows the user to hear the contents of the >> entire document from the cursor position to the end of the file, unless >> the control key is pressed to silence the speech. This key, by default, >> is insert-down arrow. For folks who aren’t familiar with screen >> readers, the insert key on the numeric keypad is often used as a >> modifier key, just as we often use keys such as the alt or control keys >> to perform specific functions when combined with other keys. Pressing >> the insert key along with the down arrow is NVDA’s continuous read >> command. Make sure numlock is turned off. >> With OpenOffice Beta Writer, NVDA seems to stop reading after a few >> lines. I’m guessing this is an NVDA issue and, if it is, I will see if >> a ticket has been filed on their bug tracker regarding the problem. If >> it has not, I’ll report it. >> If, for some reason, the issue is with OO I wanted to let someone know >> about it in case it can be fixed by an OO developer.
>From: Oliver-Rainer Wittmann <[email protected]> >Sent: Friday, April 04, 2014 6:03 AM > >I am not sure, if the following has impact on NVDA document reading >function. >As far as I remember only the visible part of a text document in Writer >is available to AT tools via the accessibility API. Thus, it might be >that NVDA just read the text which it could retrieve from OpenOffice Writer. > >Could you check, if NVDA reads all the visible text and then stops? Oliver, David NVDA's "say all" (NVDA + down) function at 2013.3 onward is only rendering a single paragraph on both Apache OpenOffice and LibreOffice. Believe it is an NVDA issue with IAccessible2/Symphony module, but Jamie or Mic might have a different perspective. I think Oliver's recollection regards only parsing for AT the displayed portion of a document is correct. But I don't believe that is causing the issue with the NVDA screen reader. So to take this Off Topic for a moment, If I understand the evolution correctly that is a hold over from the Java Accessibility API bridge support originally for Linux, OS X and Windows with the JAB. For both Apache OpenOffice and LibreOffice we've moved AT bridgeLinux moved to a native bridge with ATK/AT-SPI, OS X moved to NSAccessibility (with fallback to Java JRE and JAB). Only Windows had remained bridged exclusively with the JAB--and for performance issues only the buffered screen was rendered into AT for delivery. With implementation of the native bridge for IAccessible2 on Windows, and removal of JRE Java Access Bridge dependencies, I think there is now potential to move toward more complete processing of documents for consumption by Assistive Technology tool support. Stuart --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
