Accessibility: NVDA cannot read or navigate text in Codex prompt input; missing VS Code change cues during edits

What version of the IDE extension are you using?

26.5318.11754

What subscription do you have?

ChatGPT Pro

Which IDE are you using?

VSCode

What platform is your computer?

Microsoft Windows NT 10.0.26300.0 x64

What issue are you seeing?

I am a screen reader user (NVDA on Windows) using Codex in VS Code and am encountering accessibility issues that make it difficult to use effectively.

---

Issue 1: Cannot review prompt text with arrow keys

Steps to reproduce

1. Open Codex in VS Code
2. Type text into the prompt input box
3. Use arrow keys (left/right/up/down) to move through previously typed text

Expected behavior

• NVDA should read characters, words, or lines as I navigate with arrow keys
• Standard text navigation should work as it does in other VS Code inputs

Actual behavior

• NVDA says "blank" when using arrow keys
• I cannot review what I’ve typed using normal keyboard navigation
• In the prompt input box, backspacing over typed text does announce characters correctly
• The only reliable workaround is NVDA object navigation, which is significantly slower

---

Issue 2: Missing accessibility cues for file edits

Steps to reproduce

1. Ask Codex to edit a file
2. Allow it to apply changes

Expected behavior

• VS Code should provide its usual accessibility cues for file changes

(e.g., sounds or indicators for inserted or modified lines)

Actual behavior

• Changes are applied, but no accessibility cues are announced
• NVDA does not indicate what content has changed
• This makes it difficult to understand what Codex modified

---

Impact

• Makes it difficult to review prompts before sending
• Reduces awareness of what Codex changed in files
• Requires slower, more effortful workarounds (e.g., object navigation)
• Overall significantly impacts usability for screen reader users

---

Environment

• OS: Windows 11 x64
• Screen reader: NVDA
• Editor: VS Code
• Codex extension: 26.5318.11754

---

Additional notes

• These issues appear specific to Codex UI elements
• Standard VS Code editing and navigation work correctly with NVDA
• This suggests the problem is with how Codex implements its input and change presentation, rather than VS Code itself

What steps can reproduce the bug?

Prompt input issue

1. Open Codex in VS Code
2. Type text into the prompt input box
3. Use arrow keys (left/right/up/down) to move through previously typed text

File edit issue

1. Ask Codex to edit a file
2. Allow it to apply changes

What is the expected behavior?

• NVDA should read characters, words, or lines when navigating text with arrow keys in the prompt input box
• Standard text navigation should work as it does in other VS Code inputs
• VS Code should provide its usual accessibility cues for file changes (e.g., sounds or indicators for inserted or modified lines)

Additional information

• Screen reader: NVDA
• Standard VS Code editing and navigation work correctly with NVDA
• The issue appears specific to Codex UI elements