Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: [Accessibility] Screen reader arrow key navigation does not follow chat message order

Open
  • Is something wrong?
#129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
accessibility, desktop

Research direction

Start by reproducing the chat-history navigation problem in Command Code Desktop on Windows with a screen reader, following the listed conversation and “Jump to latest message” steps. Trace the chat display and navigation order, then verify that Arrow keys follow the full visual message order, including messages revealed after jumping to the latest message.

Written by the indexing model from the issue text.

Description

bug
GUI version

0.1.45

Operating system

Windows

Reproduction steps
  1. Open Command Code Desktop and start a chat.
  2. Have several rounds of conversation, including a relatively long Agent response.
  3. Use a screen reader in browse mode and use the Up/Down Arrow keys to navigate through the chat history.
  4. Observe that arrow key navigation no longer follows the visual order of the conversation.
  5. Activate the "Jump to latest message" button.
  6. Observe that the latest messages are displayed in the chat window, but the screen reader still cannot reach them by using the Arrow keys.
Expected behavior

The screen reader should allow users to navigate through the entire chat history with the Arrow keys in the same order as the messages are visually displayed, including the latest messages.

Actual behavior

After several rounds of conversation, Arrow key navigation no longer follows the visual order of the chat messages.

The message content itself can be read correctly by the screen reader, but the navigation order becomes incorrect. The screen reader may return to an earlier part of the conversation instead of continuing to the following messages.

The "Jump to latest message" button is accessible. After activating it, the latest messages are visibly displayed in the chat window, but using the Arrow keys still cannot navigate to those latest messages and instead returns to an earlier part of the conversation.

The issue occurs with both NVDA 2026.2 and 争渡读屏 26.10.1, although their behavior differs.

Screenshots, recordings, or sanitized logs

No response

Safety check
  • I removed credentials and private project information from this report.
Dominant language
Shell
Stars
85
Forks
5
Avg merge
2h 46m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommandCodeAI/desktop

All issues in CommandCodeAI/desktop

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.