Date: prev next · Thread: first prev next last

Hi Michael, All,

(Apologies if this message has too many addressees; I'm not sure which ones I should drop.)

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 )
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: but nothing similar 
for IAccessible2.
This calls for some LibreOffice testing with JAWS; I hope to do some of that next weekend.

Best regards,

Christophe Strobbe

On 07 June 2022 at 11:25 Michael Weghorn <> wrote:


One other aspect that came to my mind:

For Windows, we currently support IAccessible2, but not UIA.
That's fine for NVDA, but I have heard/read at times that other screen 
readers/AT rely more on UIA. (But I haven't done any further research so 
Does anybody know more about this and whether it would actually be 
necessary to implement native UIA support in LO for those AT to properly 
interact with LO?
(Or is it more about having proper plugins/app modules/scripts for LO 
for the single AT, since e.g. NVDA and JAWS appear to rely heavily on 
those to properly support specific apps?)

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.