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

Allow appModules to prefer UIA for certain windows #7961

Closed
leonardder opened this Issue Feb 6, 2018 · 2 comments

Comments

Projects
None yet
4 participants
@leonardder
Collaborator

leonardder commented Feb 6, 2018

It is currently possible to implement isBadUIAWindow on the appModule level to use IAccessible for windows that are reported as native UIA. I also propose the opposite of this feature, i.e. an isGoodUIAWindow function that takes a window handle as a parameter and returns True if UIA should be used in all cases. I think this feature can be justified as follows:

  1. It seems there are windows that do not report as native UIA even though they are, for example the window class of the Windows Defender Application Guard.
  2. It makes it much easier to inspect within NVDA how an application behaves is UIA is used for a particular control.

Other arguments welcome of course. CC @dkager @michaelDCurran @josephsl

@bramd

This comment has been minimized.

Show comment
Hide comment
@bramd

bramd Feb 7, 2018

Contributor

Sounds reasonable to me, but it might be better to combine these two methods to a useUIAForWindow method that returns True/False?

Contributor

bramd commented Feb 7, 2018

Sounds reasonable to me, but it might be better to combine these two methods to a useUIAForWindow method that returns True/False?

@leonardder

This comment has been minimized.

Show comment
Hide comment
@leonardder

leonardder Feb 8, 2018

Collaborator

@bramd commented on 7 Feb 2018, 19:49 CET:

Sounds reasonable to me, but it might be better to combine these two methods to a useUIAForWindow method that returns True/False?

That would be problematic if the appModule wants to leave the decision to core instead. We also want to keep isBadUIAWindow for backwards compatibility.

Collaborator

leonardder commented Feb 8, 2018

@bramd commented on 7 Feb 2018, 19:49 CET:

Sounds reasonable to me, but it might be better to combine these two methods to a useUIAForWindow method that returns True/False?

That would be problematic if the appModule wants to leave the decision to core instead. We also want to keep isBadUIAWindow for backwards compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment