Create separate UIA parent objects for standard and alt conhost buffers #7471

Open
opened 2026-01-31 01:04:53 +00:00 by claunia · 2 comments
Owner

Originally created by @codeofdusk on GitHub (Apr 18, 2020).

Description of the new feature/enhancement

In https://github.com/microsoft/terminal/issues/5309#issuecomment-615040262:

Ideally, in the long term, we would have different UIA parent objects for the different text buffers.

This would make things much better for UIA clients like NVDA.

Originally created by @codeofdusk on GitHub (Apr 18, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement In https://github.com/microsoft/terminal/issues/5309#issuecomment-615040262: > Ideally, in the long term, we would have different UIA parent objects for the different text buffers. This would make things much better for UIA clients like NVDA. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). -->
claunia added the Product-ConhostIssue-TaskPriority-2Area-Accessibility labels 2026-01-31 01:04:53 +00:00
Author
Owner

@codeofdusk commented on GitHub (Apr 29, 2020):

Do you still intend to look at this for 21H1?

@codeofdusk commented on GitHub (Apr 29, 2020): Do you still intend to look at this for 21H1?
Author
Owner

@codeofdusk commented on GitHub (Jul 8, 2020):

Do you still plan to get to this for 30 July (21H1)? Cc @carlos-zamora.

@codeofdusk commented on GitHub (Jul 8, 2020): Do you still plan to get to this for 30 July (21H1)? Cc @carlos-zamora.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7471