Date: prev next · Thread: first prev next last

As I stated in a previous reply which I sent to this list, I'm running Windows 10 Pro, 64-bit edition with NVDA 2016.1 and Window-Eyes 9.3. Thankfully, the accessibility experience appears to be what I'm used to with older versions of LibreOffice. There is an odd issue with Calc which I initially thought was corrected but, as I now remember, I think the fix was only a partial one. When using Calc, I am able to easily navigate from one cell to the next using arrow keys and NVDA reads the contents of the cell if "report table cell coordinates is enabled in the Document Settings dialog. However, when I open a new workbook at that point, NVDA may read the first two cells but then stops reading as I move arrow keys. If I alt-tab to the last open window and then alt-tab back into the workbook, cells are read normally as I use arrow keys. Window-Eyes 9.3 still causes Writer and Calc to crash when they are opened. When running Window-Eyes, the first time I opened Writer it told me that Writer crashed and would save recovered files but subsequent attempts to open Writer yield no output. It's as if the program never opened. This behavior occurred with a previous version of Window-Eyes and I will therefore report this to AI Squared, the developer of this particular screen reader.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.