[Accessibility] Two NVDA screen reader issues in the prompt input field (VS Code extension)

Resolved 💬 2 comments Opened Mar 31, 2026 by cdavy2016-hash Closed May 5, 2026

Environment

  • Claude Code VS Code extension
  • Screen reader: NVDA
  • OS: Windows 10

Issue 1 — Character and word echo interrupted while typing

When typing in the prompt input field, NVDA's character and word echo is interrupted. The user cannot hear what they are typing in real time. As a workaround, the user must re-read the entire prompt after writing it and before submitting, which is a significant loss of time and independence.

Issue 2 — Enter key does not reliably activate Forms Mode

When navigating to the prompt input field, pressing Enter does not activate NVDA's Forms Mode (browse mode → forms mode switch). This behavior is intermittent: sometimes Enter works as expected, but it fails randomly, making the field inaccessible for typing.

The only reliable workaround is:

  1. Tab past the field to the "Add" button
  2. Shift+Tab back into the field

This indirectly triggers Forms Mode and allows typing.

Expected behavior

  • NVDA should echo characters and words while typing in the prompt field.
  • Pressing Enter (or focusing the field) should consistently activate Forms Mode, as is standard for input fields.

Impact

These issues make the extension significantly harder to use for blind users relying on a screen reader, affecting basic prompt input workflow.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗