Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Windows Terminal: Set up UIA tree and hook it up properly #634
I am launching the Windows Terminal with the NVDA screen reader active. I then type the
NVDA does not read out the contents of the
Phil was working on the TSF. This is UIA. We know we need to hook this up and get it going, but we haven't got to it yet.
We're pretty sure that the XAML Islands portions of the UI should provide some level of UIA pattern implementation already.
As for the TerminalControl itself, we imagine that we can crib the implementation from conhost.exe that is currently hanging out around interactivity/win32 in the code base starting from
changed the title
New windows terminal is not accesible to screen readers
Jun 20, 2019
I'm just going to spew information out at you, so I hope I don't come off as rude.
Just rebuilt master. The TermControl is exposed as a TextProvider. So, using Inspect.exe, I've seen the data through the TextPattern Explorer.
I've been able to verify that you can access the text through Narrator too. The navigation is definitely wonky though.
Hopefully, what you're seeing is an issue with navigation. Let me know if that's not helping though.
Ah, if I navigate into line mode then I can get some of the text out of it, and this may be my fault, but when I execute the
Also, is there a plan to get live text reading working again? That was what threw me off originally.
Ah, the live text reading is going to get hooked up after the navigation gets fixed up a bit. At least right now, the text from the buffer is accessible. But I need to hook up an event that handles new text appearing and directly passes that to the screen reader. This is definitely worth creating a new issue, for tracking. Mind creating one for me?