Skip to content

Accessibility: Signaling Model #2447

@carlos-zamora

Description

@carlos-zamora

Description of the new feature/enhancement

UIA has signal events (link). ConHost supported them. WindowUiaProvider was an integral part to that.

Windows Terminal currently doesn't support them. We have some architecture in place to do so though.

Proposed technical implementation details (optional)

WindowUiaProvider already has the groundwork for that. It might be that we don't even need a WindowUiaProvider and just have XAML do some of it.

For reference, the signaling model for conhost was as follows:

<ConHost Event (i.e.: new text)>
--> Signal WindowUiaProvider
--> Signal ScreenInfoUiaProvider
--> Raise UiaAutomationEvent to Client

The client then responds to these events with more actions (i.e.: recreate object, etc...)

EDIT: The functionality for signaling includes...

  • Selection Events (selection changed) PR
  • Text Buffer Events (new output)
  • Scroll Events

I may possible need...

  • Resize events
  • Cursor Events

Metadata

Metadata

Assignees

Labels

Area-AccessibilityIssues related to accessibilityIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Priority-1A description (P1)Product-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions