Investigate Removal of WindowUiaProvider #4466

Closed
opened 2026-01-30 23:48:26 +00:00 by claunia · 1 comment
Owner

Originally created by @carlos-zamora on GitHub (Oct 15, 2019).

Description of the new feature/enhancement

The WindowUiaProvider might actually not be useful in Windows Terminal. This is the case because XAML handles just about all of the accessibility we need at a XAML control level. Since we already have TermControlAutomationPeers, I doubt we'll need a WindowUiaProvider.

Removing an unused provider also ensures that we don't crash on changing an object we're not really ever caring for either.

Our signaling model may be confined to the TermControl layer, as well. That solves the issue of passing the HWND up/down layers.

Originally created by @carlos-zamora on GitHub (Oct 15, 2019). # Description of the new feature/enhancement The WindowUiaProvider might actually not be useful in Windows Terminal. This is the case because XAML handles just about all of the accessibility we need at a XAML control level. Since we already have TermControlAutomationPeers, I doubt we'll need a WindowUiaProvider. Removing an unused provider also ensures that we don't crash on changing an object we're not really ever caring for either. Our signaling model may be confined to the TermControl layer, as well. That solves the issue of passing the HWND up/down layers.
claunia added the Issue-TaskNeeds-Tag-FixProduct-TerminalArea-Accessibility labels 2026-01-30 23:48:26 +00:00
Author
Owner

@carlos-zamora commented on GitHub (Jan 23, 2020):

Closing in favor of #3564

@carlos-zamora commented on GitHub (Jan 23, 2020): Closing in favor of #3564
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4466