Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#129 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
shell

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
Shell
星标
85
派生
5
平均合并
2 小时 46 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CommandCodeAI/desktop 的其他 Issue

查看 CommandCodeAI/desktop 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。