Does NVDA depend on IAccessible API #13784
-
|
We are having a discussion on the VS Code since we want to improve the screen reader detection. Does NVDA depend on the legacy Thanks a lot |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
I think that most screenreaders keep it as a fall back for some purposes, as
I see it mentioned in log files here and there.
Brian
…--
***@***.***
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
***@***.***, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Isidor Nikolic" ***@***.***>
To: "nvaccess/nvda" ***@***.***>
Cc: "Subscribed" ***@***.***>
Sent: Thursday, June 09, 2022 3:07 PM
Subject: [nvaccess/nvda] Does NVDA depend on IAccessible API (Issue #13782)
We are having a discussion on the VS Code since we want to improve the
screen reader detection.
Currently accessibility clients of Chrome use legacy IAccessible MSAA or
the new IAccessible2 UIAutomation.
We would like to drop support for auto detecting screen readers that
support the legacy IAccessible MSAA.
Does NVDA depend on the legacy `IAccessible`API?
Thanks a lot
Isidor
--
Reply to this email directly or view it on GitHub:
#13782
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks. But that means that NVDA does use |
Beta Was this translation helpful? Give feedback.
-
|
@isidorn I'm not sure your question can be answered as it stands. You wrote:
That is not really true. IAccessible2 and UIAutomation are two separate API's. For more explanation see this SO question Perhaps if you would tell us
we would be able to provide a more complete answer. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I can confirm the answer by @lukaszgo1. NVDA uses a mix of (depending on scenario):
Historically for Chromium IAccessible2 has been used (supplementing MSAA/IAccessible), however support for UIA is also available and can be enabled / forced via the advanced settings menu of NVDA. You may have to ensure that the browser is exposing it with command line flags. That said, IAccessible2 based implementation for browsers is more battle tested, essentially the same implementation is used for Firefox, Chrome and Edge. Although there are regular changes, the core implementation has existed for many years. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much, this confirms that NVDA uses IAccessible2 for Chromium, which is what we were interested in. |
Beta Was this translation helpful? Give feedback.
Yes, I can confirm the answer by @lukaszgo1. NVDA uses a mix of (depending on scenario):
Historically for Chromium IAccessible2 has been used (supplementing MSAA/IAccessible), however support for UIA is also available and can be enabled / forced via the advanced settings menu of NVDA. You may have to ensure that the browser is exposing it with command line flags. That said, IAccessible2 based implementation for browsers is more battle tested, essentially the same implementation is used for Firefox, Chrome and Edge. Although there are regular changes, the core impl…