Date: prev next · Thread: first prev next last


I've done it before.  They didn't seem to care.  The guy told me LO needed to be written to use 
UIA.  Very depressing.  So, I gave up and started using IBM Lotus Symphony on Windows and only use 
LibreOffice on Linux ever since.

-----Original Message-----
From: David Goldfield [mailto:dgoldfield1211@gmail.com] 
Sent: Friday, May 4, 2018 4:19 PM
To: V Stuart Foote <VStuart.Foote@utsa.edu>; accessibility@global.libreoffice.org
Subject: Re: [libreoffice-accessibility] Windows LO with JAWS

This is distressing. Several years ago, JAWS was working reasonably well with LibreOffice, if my 
memory is correct, but I have also encountered the same problem with more recent versions. As you 
say, NVDA offers much better support. While NVDA has been my screen reader of choice for nine years 
I would encourage users of JAWS to contact VFO at support@vfo.com to let them know your feelings 
regarding the lack of support being offered by JAWS for this excellent suite.



David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com On 5/4/2018 2:59 PM, V 
Stuart Foote wrote:
Bryen Yunashko wrote
... A couple of months ago, I installed LibreOffice and had great 
difficulty because often when I started up LO, Jaws would stop 
working and then restart itself.

A number of buttons and fields didn't work either.   So, I put it aside
for a while.   This week I decided to try again and asked someone to
update the latest LO as the inplace update button wasn't accessible 
for me.

Now, when I start LO, it does not even speak anything.  It is completely
"hidden."   But I know LO is actually running because I will randomly type
some text, then press Alt+F4 to close the program and I get a prompt 
to save or discard my file.

But while LO is open, nothing works.  No menu button, tabs, arrow 
keys, nothing.

Is this a known problem?
Completely normal...

LibreOffice implements a native Windows accessibility bridge based on 
the opensource IAccessible2 API

Reference:
http://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/

Unfortunately for JAWS users Freedom Scientific has never seen fit to 
implement modular support for IA2, so the short answer is it is known 
and JAWS willl not work with LibreOffice.

You will need to install NVDA as a free and open source Windows backup 
to JAWS. The screen reader navigation is a bit different--but fidelity 
of IA2 accessible content is much better.  LibreOffice accessible 
event based support is pretty complete--and its screen review/Graphics 
API "screen scraping" rounds things out.

Available here:
https://www.nvaccess.org/

Let us know how you make out.





--
Sent from: 
http://nabble.documentfoundation.org/Accessibility-f2006038.html



--
To unsubscribe e-mail to: accessibility+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://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? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://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.