OpenOffice 4.1 and Screen Reader Support/A Quick Status Report

The release of OpenOffice 4.1 is not only a good thing for sighted users but it is particularly exciting for computer users with visual impairments. Up until now, Microsoft Office and perhaps the WordPerfect suite were the only robust office programs which would work well with screen readers. Forgive this small diversion but I have to ask … does anyone use Wordperfect anymore? I haven’t actually known of anyone who has been using it and I’m curious.
I have nothing against these programs and, in fact, I use Microsoft Word and Outlook while I’m at work. However, these programs aren’t free and many consumers can’t easily afford them and they should be able to enjoy the same free alternatives as their sighted counterparts. OpenOffice now makes this a possibility, with Libreoffice soon to follow with their upcoming 4.3 release.
I’ve done a bit of preliminary testing with the latest versions of NVDA, JAWS and Window-eyes and I would like to report my findings, such as they are. As screen readers continue to evolve and incorporate further enhancements and bug fixes, this information will likely change and very quickly at that. I’ll post updates as this occurs. My testing was done using Writer, which is OpenOffice’s word processor similar to Microsoft Word and Calc, the spreadsheet similar to Excel.

Version 2014.1
NVDA is able to properly track menus and dialogs as well as properly reporting text at the position of the cursor or caret. When performing a continuous read command using the insert-down arrow command, I have noticed that NVDA consistently stops speech after reading a few lines of text. I think this has been going on for some time and I have reported this in the NV Access bug tracker and it appears as ticket 4119.
In Calc, NVDA reads cell data and coordinates properly as you move using arrow keys. When you enter data into a cell and then move away from that cell with arrow keys, NVDA reads extra data which it probably should not be reading. I’ve gotten so used to this that I simply press the control key and ignore it but I suppose it should be reported. I’ll try and get around to doing this today.

Version 15.0.9023
This latest build of JAWS 15, released on April 29 of this year, contains a fix to a bug that I reported to Freedom Scientific where JAWS was reading some odd messages while in Writer. In the previous build, support for Calc was inconsistent, with some cells being voiced while others were not. The latest build did a good deal of clean-up and JAWS seems to handle Calc beautifully. However, while in Writer JAWS reads the odd message “edit has flows to” when I move focus away from and then back to the text in the document editing window. As an example, while in a Writer document press the alt key to move focus from the document area to the menu bar. Press the alt key a second time to bring focus back to the document and you’ll hear the message. I have reported this issue to their technical support email address and they have responded to me very quickly and have asked to speak with me so that I can give them more information about the bug. It is my hope that the next build of JAWS will have a fix for this minor but noticeable issue.

Version 8.4
window-eyes kept producing errors whenever I tried opening Writer. This issue was very consistent, even with the OpenOffice 4.1 beta. When I contacted GW Micro, the tech support rep that I spoke to indicated that the bug was not reproducible with a test build of the upcoming Window-eyes version. This is good news, as this should mean that the next version of Window-eyes should provide better support for OpenOffice.

As I don’t have copies of JAWS or Window-eyes loaded on my machine at home, my ability to perform testing with those screen readers is somewhat limited but I’ll certainly do more of it when I can and will provide an updated post as things change.
I would like to end this post by encouraging my readers to consider testing OpenOffice 4.1 with your screen reader or enlarger of choice. If you find a bug, please report it to the manufacturer of your access technology software. The more users report bugs the sooner we’ll have a robust, free and fully accessible office suite.


4 thoughts on “OpenOffice 4.1 and Screen Reader Support/A Quick Status Report

  1. Pingback: The Latest LibreOffice and Apache OpenOffice Updates | Frugal Guidance 2

  2. Hello David Goldfield,
    I recently purchased a new computer, Assus brand with Windows 7, 64-bit, NVDA 2015, Firefox as browser. Open Office was installed late last week on my computer. From your article, it sounds like using NVDA commands are how one works within Writer. Is that correct?
    Can you recommend a general tutorial on how to use Open Office, and general shortcut commands, that would cater to keyboard users?
    Currently, using the basic Jarte program for my word processing purposes.

    Thanks for your time and assist in advance.
    David Russell

  3. Hi, David.
    Yes, using the standard reading commands should work from within Writer, just as you’re used to with Jarte. The “say all” command (insert down-arrow) had a problem where it would prematurely stop reading after a paragraph or two and I think this is an issue with OpenOffice and LibreOffice. You can find a Web page with keyboard shortcuts at
    I don’t know how current the list is but my guess is that most if not all of them will work with the current version.

  4. Hi David Goldfield, are there any ways to get NVDA to speak the colum of the tables as we tab around? It works in Microsoft office, but not in the latest Open Office. I am using NVDA 2016.2.

Please feel free to leave a comment. I'd love to hear from you.

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s