Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#129 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell
Área
accessibility, desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Shell
Estrellas
85
Forks
5
Merge medio
2 h 46 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommandCodeAI/desktop

Todos los issues de CommandCodeAI/desktop

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.