Hi Michael,
JAWS does support IAccessible2, but only if it needs to, like in Firefox, and some parts of
Chromium-based browsers. However, with the UI Automation implementation for the latter becoming
stronger, there might be a time when JAWS moves to UIA for web content support in Chromium
browsers. But you never know what plans Vispero actually has for which version of JAWS, ZoomText,
and Fusion. All I notice is that, with Windows 11 having an even stronger UIA implementation than
10, more things are being done through that interface rather than traditional MSAA or IAccessible2
channels where possible. And as has been said elsewhere, UIA properties and events are even very
accessible from within the JAWS scripting language, which makes this even more compelling because
the end user experience can be customized further. As IAccessible2 is an extension of MSAA, and
MSAA is largely deprecated by Microsoft, it will probably never get the same treatment.
Marco
-----Original Message-----
From: Michael Weghorn <m.weghorn@posteo.de>
Sent: Tuesday, June 7, 2022 1:27 PM
To: Christophe Strobbe <strobbe@hdm-stuttgart.de>; libreoffice@lists.freedesktop.org;
accessibility@global.libreoffice.org
Cc: libreoffice-qa@lists.freedesktop.org
Subject: Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 [IAccessible2 support
in JAWS]
Hi Christophe,
On 07/06/2022 12.14, Christophe Strobbe wrote:
After some online searching, it seems that JAWS at least used to support IAccessible2, originally
mainly for IBM Lotus Symphony.
According to a tweet by Marco Zehe from December last year, JAWS
handles Chromium and Edge via IAccessible2. (See
https://twitter.com/MarcoInEnglish/status/1471523578805997570 )
That sounds promising, JAWS was what I vaguely had in mind about having been mentioned of
presumably not supporting IAccessible2 (well) in the past.
Twitter is not an ideal source, but I couldn't find any documentation related to IAccessible2 on
Freedom Scientific's website. They do have documentation on to use script access to UIAutomation:
https://support.freedomscientific.com/support/jawsdocumentation/UIAScriptAPI but nothing similar
for IAccessible2.
This calls for some LibreOffice testing with JAWS; I hope to do some of that next weekend.
Thanks a lot, that's much appreciated!
Best regards,
Michael
--
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/
Privacy Policy: https://www.documentfoundation.org/privacy
--
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/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 (continued)
Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 · Caolán McNamara
Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 · Caolán McNamara
Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 · Michael Weghorn
Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 · Jason White
[libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 · Colomban Wendling
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.