Skip to content
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

[Automation] Add AutomationProperties.IsAccessible #17692

Open
rabbitism opened this issue Dec 4, 2024 · 1 comment
Open

[Automation] Add AutomationProperties.IsAccessible #17692

rabbitism opened this issue Dec 4, 2024 · 1 comment

Comments

@rabbitism
Copy link
Contributor

rabbitism commented Dec 4, 2024

Is your feature request related to a problem? Please describe.

Currently there is no way to hide an existing control from Automation. We can only derive a new control and override AutomationPeer creation. this should be generally supported.

Describe the solution you'd like

Add new property: AutomationPeer.IsAccessible . Thus AutomationPeer return None if this is false, and others if this is true.

Describe alternatives you've considered

No response

Additional context

No response

@IsaMorphic
Copy link

I disagree with this as a design choice. It acts against the interests of the automation APIs existence in the first place. If I actively hide a control from the automation pipeline, this creates a logical, user-visible element in the interface that can't be traversed at all. This creates a "blindspot" both for testing pipelines relying on UI automation, and an easy "opt-out" for developers that would otherwise be required to consider accessibility in their app's design (something that should ALWAYS be the case).

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

No branches or pull requests

3 participants