Expose more AutomationProperties
- Dominant language
- C#
- Stars
- 7.7k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 61
Description
The currently available AutomationProperties require lots of work to fully control the UI Automation/Accessibility Tree and produce the best possible experience for ALL people using our software.
As an example, if I have a TextBlock containing a symbol (via an appropriate font) that is purely visual and next to another TextBlock that contains displayed text relating to the symbol, there is no easy way to hide the symbol TextBlock from the UIA tree.
The only way to do this seems to be to derive from the TextBlock and access the automation per directly to set `IsControl` and `IsContent` accordingly. That seems complex and unnecessary just to hide a symbol from the UIA Tree.
In UWP there is the [AccessibilityView](https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.automation.peers.accessibilityview) property that makes it easy to set this from XAML.
That would be a start.
Even better would be exposing AutomationProperties for all the [AutomationElementIdentifiers](https://docs.microsoft.com/en-us/dotnet/api/system.windows.automation.automationelementidentifiers?view=netcore-3.1).
Contributor guide
Assessment
This issue has not been assessed yet.