RE: [libreoffice-accessibility] Problem using Libre office accessibility features

2016-05-24 Thread toki
Alan wrote:

>Am I missing anything?

JAWS, at best, had support that could be described as "marginally
acceptable".
Windows Eyes, at best, had support that could be described as "tolerable".

As far as LibO 5.1.1.3 goes, forget about trying to use either of those
programs. It just isn't there.
Both AI Squared and Freedom Scientific claim the problem is with
LibreOffice's failure to support standard AllY protocols and APIs.

jonathon




-- 
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


Re: [libreoffice-accessibility] Problem using Libre office accessibility features

2016-05-24 Thread David Goldfield

Hi.

I have NVDA and Window-Eyes at home and am willing to do a bit of ad hoc 
testing during the long weekend. I'll submit a report, hopefully by May 30.



On 5/24/2016 5:52 PM, V Stuart Foote wrote:

@Alan,


Alan-2 wrote

Good evening,

I've just installed Latest Libre office on my new laptop, runing a
windows 64 operating sistem... I read that it would be accessible using
screen readers like Jaws or NVDA, however, jaws doesn't provide any
speech output when navigating menus, etc. Using nvda, it certainly
brings output, but sometimes strange behaviors appear, for example,
after choosing a suggested option for a misspelled word from the context
menu.

Am I missing anything? Any help would be welcome, thanks in advance!

Sorry--no seat of JAWS or Windows Eyes to test against. But, NVDA functions
"out of the box" with LibreOffice exposing accessible events mapped to the
the Linux Foundations IAccessible2 v1.3 API.  The project does not bridge to
MS UIA. And the old Java Accessibility API "Java Access Bridge" was stripped
out when implementing the native IAccessible2 mappings.

Of course there are issues--announcing cells for tables in Writer, and the
main content  dialogs not sounding, "say all"  top to bottom reading, etc.
but  overall is reasonably usable.

Theoretically, JAWS and Windows Eyes provide the same level of support
reading LibreOffice exposed IAccessible2 events--but I can't verify.

Stuart
  




--
View this message in context: 
http://nabble.documentfoundation.org/libreoffice-accessibility-Problem-using-Libre-office-accessibility-features-tp4184329p4184330.html
Sent from the Accessibility mailing list archive at Nabble.com.




--
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



Re: [libreoffice-accessibility] Problem using Libre office accessibility features

2016-05-24 Thread V Stuart Foote
@Alan,


Alan-2 wrote
> Good evening,
> 
> I've just installed Latest Libre office on my new laptop, runing a 
> windows 64 operating sistem... I read that it would be accessible using 
> screen readers like Jaws or NVDA, however, jaws doesn't provide any 
> speech output when navigating menus, etc. Using nvda, it certainly 
> brings output, but sometimes strange behaviors appear, for example, 
> after choosing a suggested option for a misspelled word from the context 
> menu.
> 
> Am I missing anything? Any help would be welcome, thanks in advance!

Sorry--no seat of JAWS or Windows Eyes to test against. But, NVDA functions
"out of the box" with LibreOffice exposing accessible events mapped to the
the Linux Foundations IAccessible2 v1.3 API.  The project does not bridge to
MS UIA. And the old Java Accessibility API "Java Access Bridge" was stripped
out when implementing the native IAccessible2 mappings.

Of course there are issues--announcing cells for tables in Writer, and the
main content  dialogs not sounding, "say all"  top to bottom reading, etc.
but  overall is reasonably usable.

Theoretically, JAWS and Windows Eyes provide the same level of support
reading LibreOffice exposed IAccessible2 events--but I can't verify.

Stuart 
 



--
View this message in context: 
http://nabble.documentfoundation.org/libreoffice-accessibility-Problem-using-Libre-office-accessibility-features-tp4184329p4184330.html
Sent from the Accessibility mailing list archive at Nabble.com.

-- 
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