Screen readers don't speak available options in interactive prompts #20192

Closed
opened 2026-01-31 07:06:12 +00:00 by claunia · 2 comments
Owner

Originally created by @daniel-montalvo on GitHub (Jul 4, 2023).

Tested with latest versions of JAWS, NVDA, and Narrator. Not sure if this is a global issue. My specific use case here is with the gh run view command from GH CLI.

  1. Check out a repo where you know you have several workflow runs available for testing
  2. In the terminal, type gh run view
  3. The terminal outputs a list of runs that you can view. Up and down arro keys would move you through the available options. Typing will filter out the results based on what you typed. Enter will select the currently keyboard focused option.

When using a screen reader and pressing up and down arrow keys, the whole terminal output is spoken instead of the option that is selected.
I would expect screen readers to be able to speak and braille whatever option is selected as the user moves up and down through the interactive prompt results.

Originally created by @daniel-montalvo on GitHub (Jul 4, 2023). Tested with latest versions of JAWS, NVDA, and Narrator. Not sure if this is a global issue. My specific use case here is with the `gh run view` command from GH CLI. 1. Check out a repo where you know you have several workflow runs available for testing 2. In the terminal, type `gh run view` 3. The terminal outputs a list of runs that you can view. Up and down arro keys would move you through the available options. Typing will filter out the results based on what you typed. Enter will select the currently keyboard focused option. When using a screen reader and pressing up and down arrow keys, the whole terminal output is spoken instead of the option that is selected. I would expect screen readers to be able to speak and braille whatever option is selected as the user moves up and down through the interactive prompt results.
claunia added the Resolution-Duplicate label 2026-01-31 07:06:12 +00:00
Author
Owner

@lhecker commented on GitHub (Jul 5, 2023):

This is a known issue (unfortunately). There's no robust solution for this at the moment and there has been a lack of interest among pretty much all terminals to fix this over the past decades. We've begun working on it in #14342, but it's progressing slowly. The issue is effectively a duplicate of #13666. /dup #13666

@lhecker commented on GitHub (Jul 5, 2023): This is a known issue (unfortunately). There's no robust solution for this at the moment and there has been a lack of interest among pretty much all terminals to fix this over the past decades. We've begun working on it in #14342, but it's progressing slowly. The issue is effectively a duplicate of #13666. /dup #13666
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Jul 5, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Jul 5, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20192