Date: prev next · Thread: first prev next last

Re: [libreoffice-accessibility] More Inconsistent Accessibility Issues with LibreOffice Calc 4.3 RC1 and Screen readers


Hi :)
Has there been any move on this topic?

Please can someone post a proper bug-report about it?
https://wiki.documentfoundation.org/QA/BugReport

The initial report doesn't need to cover all the things asked for in that
wiki-guide because it's fairly easy to add new comments later.  The
important thing is to get a new report started so that others can add to
it.  The wiki guide helps find if there is already an existing report and
if there is one then adding to it can be much more helpful and easier than
creating a "duplicate thread"

I kinda hope that the devs are not reading all the mailing-lists all the
time because if they are then i'd be annoyed that they aren't working on
"my favourite bug" instead!! :)  (on the other hand it is nice to get a bit
of feedback sometimes so there is probably a balance somewhere)
Regards from
Tom :)





On 27 June 2014 20:26, Kevin Cussick <the.big.white.shepherd@googlemail.com>
wrote:

Hi,   thanks for this post,  this is very useful.  I am not a programer
but I can do the same as you and test things.  I have been wanting open
office and Lo to just work out of the box for years now it is more or less
happening I am excited good post and I am sure someone from the dev team
will read and maybe be able to try and fix with a patch.


On 27/06/2014 17:07, David Goldfield wrote:

I have some additional findings to report regarding screen reader
accessibility of Calc 4.3 and screen readers.
As I indicated in an early message, I receive little or no feedback when
navigating through spreadsheets using the latest Calc RC along with NVDA
2014.2, although accessibility is not broken in OpenOffice 4.1 and I
assumed that both LibreOffice and OpenOffice were using the same code for
Iaccessible2 support.
For kicks, I wanted to see how Calc would interact with the latest build
of JAWS 15.
When I tried navigating through a Calc spreadsheet using JAWS, the
behavior was different and, on the whole, more positive.
When I first opened Calc with JAWS running, JAWS treated the spreadsheet
as though it was a Web page or HTML document and I had to turn off the
virtual cursor.
Once I did this, audible feedback while using arrow keys to navigate the
spreadsheet also yielded no results.
However, when I pressed the alt key to open the menu bar followed by a
second press of the alt key to close it, JAWS read the spreadsheet data and
cell information perfectly, as it would with programs such as Excel.
I was intrigued and closed Calc.
After reopening Calc, JAWS did not go into its Web page browse mode but
still did not produce feedback while navigating through the spreadsheet.
Once again, I pressed the alt key twice, to move focus to and then away
from Calc's menu bar.
As I expected, audible navigation worked perfectly, allowing me to hear
cell coordinates and any data contained within the cell.
Even more curious, I wanted to see if I could get NVDA and Calc to
cooperate by moving focus away from and then back to the spreadsheet.
I closed JAWS and started NVDA.
I opened Calc and pressed the alt key twice, once to access the menu bar
and a second time to move focus away from the menu bar back to the
workbook.  Unfortunately, NVDA would still not read any data or cell
coordinates in the workbook.  I don't know if this information is of any
use to any of the developers who may be reading this but I thought I should
pass this along.
While I don't have JAWS on my home computer, I do have NVDA and would be
happy to run specific tests if I can be of any assistance.
I've also gone into the view menu to try and turn off unnecessary or at
least unneeded toolbars, as this can sometimes make a difference.  As an
example, I vaguely remember that the formula bar might have been
responsible for producing too much audible feedback in one of the earlier
versions of Calc.  Again, if there are specific settings any of you would
like me to try please let me know.  As a user and trainer for other users
of this technology, I am quite excited at seeing more accessibility being
implemented in these suites and I'd like to do anything I can to assist in
making this happen.  I'm not a programmer but I'm happy to test and report
findings.



David Goldfield
Computer Technology Instructor
919 Walnut Street
4th Floor
Philadelphia, PA  19107

215-627-0600 ext 3277
FAX:  215-922-0692

dgoldfie@asb.org<mailto:dgoldfie@asb.org>
www.asb.org<http://www.asb.org>


Serving Philadelphia's and the nation's blind and visually impaired
population since 1874.

  www.asb.org<http://www.facebook.com/pages/Associated-
Services-for-the-Blind/234389409941928>      www.asb.org<http://twitter.
com/ASBPhiladelphia>










--
To unsubscribe e-mail to: accessibility+unsubscribe@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+unsubscribe@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

Context


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.