Hi
Two things, first:
I noticed that after I enter a cells edit mode by double clicking the
mouse and then escape, I actually get reports of cell coordinates and
cell values when I use the arrow keys. I don't now exactly what gets
initialized when I double click on a cell but I'll keep digging.
Secondly:
I did a patch for the problem with zero being announced and it has been
pushed to master. It would be nice if somebody could verify that it
actually works especially if you could test with another Windows screen
reader than NVDA. Note that this is only pushed to master at this point.
You can download and try out the patch here:
http://dev-builds.libreoffice.org/daily/master/Win-x86@51-TDF/current/master~2014-10-19_01.56.13_LibreOfficeDev_4.4.0.0.alpha0_Win_x86_en-US_de_ar_ja_qtz.msi
The focus issue is still not fixed so you need to use the workaround to
double click a cell and pressing the escape button to get announcements.
But after that you should be able to test that cell content other than
numerical values are presented correctly.
Let's keep our fingers crossed that we can nail this focus issue soon.
Regards,
Niklas Johansson
David Goldfield skrev 2014-10-15 14:28:
Hi. While pressing the f2 key in Calc does provide cell coordinates, pressing
escape to return to the worksheet does not allow arrow keys to announce any
cell info. What is odd, if this will be of any help, is that OpenOffice works
perfectly in NVDA.
I can also tell you that it is important that NVDA users enable the "report table
cell coordinates" checkbox in the NVDA document settings checkbox.
-----Original Message-----
From: Niklas Johansson [mailto:sleeping.pil...@gmail.com]
Sent: Wednesday, October 15, 2014 3:52 AM
To: accessibility@global.libreoffice.org
Subject: Re: [libreoffice-accessibility] Re: Calc and Accessibility
V Stuart Foote skrev 2014-10-14 19:44:
Also when cells are empty NVDA sounds a Zero rather than blank--that is an NVDA
issue.
Hm... I'm not so sure it is a bug in NVDA. I'd rather think that it is an issue in
LibreOffice. It also seems related to the issue with only values being announced. I
believe that a big part of the issue lies within the fact that the IA2 code from
OpenOffice abuses the IAccessibleValue interface (that should only return numerical
values) by returning string values as well. It also goes against OpenOffice/LibreOffice
api (XAccessibleValue) which probably was "fixed"
on integration into LibreOffice leaving us in this unfortunate state of non
working accessibility in Calc on Windows.
Regards,
Niklas Johansson
--
To unsubscribe e-mail to: accessibility+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
--
To unsubscribe e-mail to: accessibility+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
