-
-
Notifications
You must be signed in to change notification settings - Fork 626
-
-
Notifications
You must be signed in to change notification settings - Fork 626
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does NVDA depend on IAccessible API #13782
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: ***@***.***>
|
Thanks. But that means that NVDA does use |
@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. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
The text was updated successfully, but these errors were encountered: