All forms of UIA navigation appear to skip entries when going back and are unable to go forwards #5590

Closed
opened 2026-01-31 00:16:51 +00:00 by claunia · 5 comments
Owner

Originally created by @ghost on GitHub (Dec 16, 2019).

Originally assigned to: @carlos-zamora on GitHub.

Steps to reproduce

  • Hook up the WPF control from the dev/zorio/wpf-uia-tree branch into a simple WPF application.
  • Print text to the screen (e.g. "foo bar baz\r\nfoo2 bar2 baz2")
  • Attempt to navigate said text with NVDA

Expected behavior

Word, character and line navigation should work as expected.

Actual behavior

All navigation forms appear to skip entries moving backwards and get stuck moving forwards, for example, I have observed the following:

  • Reading the line "foo bar baz" from right to left as word units ends up reading out "baz, b, foo"
  • Attempting to read the same line left to right reads out "foo" continuously.
  • Reading the characters in that line will exhibit similar behaviour, unable to navigate rightwards and skipping entries when navigating leftwards.
Originally created by @ghost on GitHub (Dec 16, 2019). Originally assigned to: @carlos-zamora on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Steps to reproduce <!-- A description of how to trigger this bug. --> - Hook up the WPF control from the dev/zorio/wpf-uia-tree branch into a simple WPF application. - Print text to the screen (e.g. "foo bar baz\r\nfoo2 bar2 baz2") - Attempt to navigate said text with NVDA # Expected behavior Word, character and line navigation should work as expected. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior All navigation forms appear to skip entries moving backwards and get stuck moving forwards, for example, I have observed the following: - Reading the line "foo bar baz" from right to left as word units ends up reading out "baz, b, foo" - Attempting to read the same line left to right reads out "foo" continuously. - Reading the characters in that line will exhibit similar behaviour, unable to navigate rightwards and skipping entries when navigating leftwards. <!-- What's actually happening? -->
Author
Owner

@carlos-zamora commented on GitHub (Dec 17, 2019):

@ZoeyR I'm having trouble navigating with NVDA (mostly because I'm not too familiar with how to use it well). I've tested this using Narrator and Inspect.exe and the text ranges seem to be accessible. Could you provide some additional guidance on how to navigate to the terminal's text field using NVDA?

I think I could probably figure out how to navigate within the text field using this. I'm just having trouble getting to it (for now).

@carlos-zamora commented on GitHub (Dec 17, 2019): @ZoeyR I'm having trouble navigating with NVDA (mostly because I'm not too familiar with how to use it well). I've tested this using Narrator and Inspect.exe and the text ranges seem to be accessible. Could you provide some additional guidance on how to navigate to the terminal's text field using NVDA? I think I could probably figure out how to navigate within the text field using [this](https://dequeuniversity.com/screenreaders/nvda-keyboard-shortcuts). I'm just having trouble getting to it (for now).
Author
Owner

@ghost commented on GitHub (Dec 17, 2019):

That reference doesn't have the full list of NVDA shortcut keys, what you want to do is use the desktop keyboard configuration, make sure that "caps lock" is set in preferences->keyboard->modifier keys. And then press Caps lock + numpad 5 to focus the current element.

@ghost commented on GitHub (Dec 17, 2019): That reference doesn't have the full list of NVDA shortcut keys, what you want to do is use the desktop keyboard configuration, make sure that "caps lock" is set in preferences->keyboard->modifier keys. And then press Caps lock + numpad 5 to focus the current element.
Author
Owner

@ghost commented on GitHub (Dec 17, 2019):

NVDA should also be the primary testing method, only 1% of computer users use narrator as their primary screen reader: https://webaim.org/projects/screenreadersurvey8/ I can help more if you're still having issues navigating. Also, you can't use the UWP application since the UIA tree has not yet been hooked up in that.

@ghost commented on GitHub (Dec 17, 2019): NVDA should also be the primary testing method, only 1% of computer users use narrator as their primary screen reader: https://webaim.org/projects/screenreadersurvey8/ I can help more if you're still having issues navigating. Also, you can't use the UWP application since the UIA tree has not yet been hooked up in that.
Author
Owner

@carlos-zamora commented on GitHub (Dec 17, 2019):

NVDA should also be the primary testing method, only 1% of computer users use narrator as their primary screen reader: https://webaim.org/projects/screenreadersurvey8/ I can help more if you're still having issues navigating. Also, you can't use the UWP application since the UIA tree has not yet been hooked up in that.

I'll definitely use it more then. 😊 Just getting caught up in the learning curve haha.

@carlos-zamora commented on GitHub (Dec 17, 2019): > NVDA should also be the primary testing method, only 1% of computer users use narrator as their primary screen reader: https://webaim.org/projects/screenreadersurvey8/ I can help more if you're still having issues navigating. Also, you can't use the UWP application since the UIA tree has not yet been hooked up in that. I'll definitely use it more then. 😊 Just getting caught up in the learning curve haha.
Author
Owner

@ghost commented on GitHub (Feb 13, 2020):

:tada:This issue was addressed in #4018, which has now been successfully released as Windows Terminal Preview v0.9.433.0.🎉

Handy links:

@ghost commented on GitHub (Feb 13, 2020): :tada:This issue was addressed in #4018, which has now been successfully released as `Windows Terminal Preview v0.9.433.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.9.433.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5590