Skip to content

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

Closed
isidorn opened this issue Jun 9, 2022 · 3 comments
Closed

Does NVDA depend on IAccessible API #13782

isidorn opened this issue Jun 9, 2022 · 3 comments

Comments

@isidorn
Copy link
Sponsor

isidorn commented Jun 9, 2022

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

Thanks a lot
Isidor

@Brian1Gaff
Copy link

Brian1Gaff commented Jun 9, 2022 via email

@isidorn
Copy link
Sponsor Author

isidorn commented Jun 9, 2022

Thanks. But that means that NVDA does use IAccessible2?
@feerrenrut can you maybe confirm when you find time. Thanks you

@lukaszgo1
Copy link
Contributor

@isidorn I'm not sure your question can be answered as it stands. You wrote:

Currently accessibility clients of Chrome use legacy IAccessible MSAA or the new IAccessible2 UIAutomation.

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

  1. How exactly you're detecting screen readers now?
  2. What you're trying to change and
  3. What problem you're trying to solve

we would be able to provide a more complete answer.
If you're asking about IAccessible2, then yes, NVDA, and for that matter all Windows screen readers except Narrator, rely on it to access Electron based applications, as it offers access far superior to what UIA allows.

@nvaccess nvaccess locked and limited conversation to collaborators Jun 10, 2022
@feerrenrut feerrenrut converted this issue into discussion #13784 Jun 10, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants