[BUG] [A11y] VS Code extension 2.1.283: VoiceOver no longer echoes typing in the prompt input (macOS)

Summary

Since the VS Code extension updated to 2.1.283 (installed 26 Sep 2026), VoiceOver no longer echoes typed characters or words in the Claude Code prompt input. Typing works (text appears and is sent), but it is silent. Before the update, typing in the same input was read back normally.

I am a blind user and rely on VoiceOver typing echo to know what I've typed.

Environment

| Item | Value |
|---|---|
| Extension | anthropic.claude-code 2.1.283 (darwin-arm64) |
| VS Code | 1.139.1 |
| macOS | 26.6.2, Apple Silicon |
| Screen reader | VoiceOver, "While typing speak" characters and words (Text tab) on |
| VS Code | editor.accessibilitySupport: "on", status bar shows "Screen Reader Optimized" |
| Claude Code | claudeCode.preferredLocation: "panel" (editor tab) |

Steps to reproduce

1. Turn on VoiceOver with typing echo enabled.
2. Open the Claude Code tab in VS Code and focus the prompt input.
3. Type a few characters and a word.

Expected: VoiceOver speaks each character / word.
Actual: Nothing is spoken.

What I tried to rule out other causes

| Step | Result |
|---|---|
| Typing in TextEdit | Echo works, so VoiceOver itself is fine |
| Restarting VoiceOver | No change |
| Checking VoiceOver Utility > Verbosity > Text | Typing echo already on |
| Typing in a VS Code text editor | Also silent at first; fixed by "editor.editContext": false (separate VS Code EditContext issue). After that the editor echoes, the Claude input still does not |
| Toggling claudeCode.focusView off and fully quitting/reopening VS Code | No change (turned back on) |
| Checking a custom layout shortcut (it only closes side bars and focuses the Claude tab) | Not the cause; a screenshot shows the Claude input focused with nothing covering it |
| Quitting and reopening VS Code | No change |

Notes

In 2.1.283 the prompt input is a contenteditable="plaintext-only" element inside the webview (a microphone button now also appears in it). VoiceOver typing echo in Chromium is unreliable for that kind of element compared with a real <textarea>, which may be the regression. Using Claude Code in the integrated terminal is a workaround, but the panel should work with VoiceOver.