bad accessibility #9143

Closed
opened 2026-01-31 01:47:05 +00:00 by claunia · 6 comments
Owner

Originally created by @ahmedthebest31 on GitHub (Jun 19, 2020).

i want to use the new windows termenal in my daly work but it doesn't work with my NVDA screen reader and it give me a bad accessibility errors inshort the terenal like plank page normaly i use git bash as a termenal but doesn't have that mutch feachers <!--
🚨🚨🚨🚨🚨🚨🚨

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!
-->

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

Originally created by @ahmedthebest31 on GitHub (Jun 19, 2020). i want to use the new windows termenal in my daly work but it doesn't work with my NVDA screen reader and it give me a bad accessibility errors inshort the terenal like plank page normaly i use git bash as a termenal but doesn't have that mutch feachers <!-- 🚨🚨🚨🚨🚨🚨🚨 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. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? -->
Author
Owner

@zadjii-msft commented on GitHub (Jun 19, 2020):

You're gonna have to give us a few more details than that - what version of NVDA are you using? What exactly are you trying to do, what do you expect to happen, and what's actually happening? Having specific repro steps is the only way we can help investigate an issue. @carlos-zamora has done a ton of work in the last year to make sure the Terminal supports NVDA and Narrator, so if there's anything wrong, I'm sure he'd be happy to help fix it ☺️

@zadjii-msft commented on GitHub (Jun 19, 2020): You're gonna have to give us a few more details than that - what version of NVDA are you using? What exactly are you trying to do, what do you expect to happen, and what's actually happening? Having specific repro steps is the only way we can help investigate an issue. @carlos-zamora has done a _ton_ of work in the last year to make sure the Terminal supports NVDA and Narrator, so if there's anything wrong, I'm sure he'd be happy to help fix it ☺️
Author
Owner

@carlos-zamora commented on GitHub (Jun 19, 2020):

Hi @ahmedSamy31,

We've been working with NVDA. They added support for Windows Terminal in NVDA 2020.2 Beta 1. You can download the updated version at https://www.nvaccess.org/post/nvda-2020-2beta1/.

You might have to enable the following on NVDA:

  • Go to Preferences, then Settings
  • Select the "Advanced" category
  • Under "Microsoft UI Automation", enable "Use UI Automation to access the Windows Console when available".

Tagging @codeofdusk to verify if I'm missing anything.

Separately, @cinnamon-msft maybe we should add this to our docs page under troubleshooting?

@carlos-zamora commented on GitHub (Jun 19, 2020): Hi @ahmedSamy31, We've been working with NVDA. They added support for Windows Terminal in NVDA 2020.2 Beta 1. You can download the updated version at https://www.nvaccess.org/post/nvda-2020-2beta1/. You might have to enable the following on NVDA: - Go to Preferences, then Settings - Select the "Advanced" category - Under "Microsoft UI Automation", enable "Use UI Automation to access the Windows Console when available". Tagging @codeofdusk to verify if I'm missing anything. Separately, @cinnamon-msft maybe we should add this to our docs page under troubleshooting?
Author
Owner

@codeofdusk commented on GitHub (Jun 19, 2020):

Hi @ahmedSamy31,

We've been working with NVDA. They added support for Windows Terminal in NVDA 2020.2 Beta 1. You can download the updated version at https://www.nvaccess.org/post/nvda-2020-2beta1/.

You might have to enable the following on NVDA:

  • Go to Preferences, then Settings

  • Select the "Advanced" category

  • Under "Microsoft UI Automation", enable "Use UI Automation to access the Windows Console when available".

Tagging @codeofdusk to verify if I'm missing anything.

Separately, @cinnamon-msft maybe we should add this to our docs page under troubleshooting?

Nope, no need to enable UIA in console for Windows Terminal – it always uses UIA as the implementation is good. That setting is only for conhost.

@codeofdusk commented on GitHub (Jun 19, 2020): > Hi @ahmedSamy31, > > > > We've been working with NVDA. They added support for Windows Terminal in NVDA 2020.2 Beta 1. You can download the updated version at https://www.nvaccess.org/post/nvda-2020-2beta1/. > > > > You might have to enable the following on NVDA: > > - Go to Preferences, then Settings > > - Select the "Advanced" category > > - Under "Microsoft UI Automation", enable "Use UI Automation to access the Windows Console when available". > > > > Tagging @codeofdusk to verify if I'm missing anything. > > > > Separately, @cinnamon-msft maybe we should add this to our docs page under troubleshooting? Nope, no need to enable UIA in console for Windows Terminal – it always uses UIA as the implementation is good. That setting is only for conhost.
Author
Owner

@ahmedthebest31 commented on GitHub (Jun 19, 2020):

i'm using NVDA2020.1 and i had this satings enabled the problem is when i type any command NVDA can't read the outbot of this command like when i type "novd -v" to chick node js version it prented on the screen but NVDA doesn't read any thing and i can't navigate the result or the oll window

@ahmedthebest31 commented on GitHub (Jun 19, 2020): i'm using NVDA2020.1 and i had this satings enabled the problem is when i type any command NVDA can't read the outbot of this command like when i type "novd -v" to chick node js version it prented on the screen but NVDA doesn't read any thing and i can't navigate the result or the oll window
Author
Owner

@zadjii-msft commented on GitHub (Jun 22, 2020):

@ahmedSamy31 Can you try NVDA 2020.2 Beta 1 instead of NVDA 2020.1?

@zadjii-msft commented on GitHub (Jun 22, 2020): @ahmedSamy31 Can you try NVDA 2020.2 Beta 1 instead of NVDA 2020.1?
Author
Owner

@ahmedthebest31 commented on GitHub (Jun 22, 2020):

i tried nvda2020.2 and it works realy thank you

@ahmedthebest31 commented on GitHub (Jun 22, 2020): i tried nvda2020.2 and it works realy thank you
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#9143