Codex Desktop: slash-command picker is invisible to NVDA on Windows

Reproduce the issue in Codex Desktop with NVDA on Windows by typing / in the composer, then locate the implementation that renders the slash-command picker. Verify the picker’s accessibility exposure while opening, navigating, selecting, and closing. Done means NVDA announces the popup and commands and provides focused-item and state feedback without changing slash-command execution.

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop client 26.715.52143 (Windows package path reports 26.715.7063.0)

What subscription do you have?

Authenticated ChatGPT subscription (exact tier is not displayed in the current UI)

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

The slash-command picker is rendered visually when / is typed in the Codex Desktop composer, but it is not exposed or announced to the NVDA screen reader. A sighted person confirmed that the picker and its entries are visible.

NVDA does not announce that a popup/listbox opened, does not announce the available commands, and keyboard navigation provides no accessible feedback. Known commands still execute correctly when typed in full, for example /status.

Screen reader: NVDA 2026.1.1 portable, ProductVersion 2026.1.1 / FileVersion 2026.1.1.55980. This is the latest stable NVDA release as of July 20, 2026.

What steps can reproduce the bug?

1. Start NVDA 2026.1.1 on Windows.
2. Open the Codex Desktop app and focus the chat composer.
3. Type / into an otherwise empty composer.
4. Observe that NVDA announces only the typed slash and does not announce a popup, listbox, item count, or focused command.
5. Have a sighted user inspect the screen: the slash-command picker is visibly open.
6. Type /status in full and submit it: the command executes successfully.

What is the expected behavior?

When the slash-command picker opens, NVDA should announce that the popup/listbox opened, expose its command items through the Windows accessibility tree, announce the focused item while navigating, and announce selection/closure state. The implementation should provide appropriate accessible semantics and focus/active-descendant updates.

Additional information

This is specifically an accessibility defect in the visual command picker, not a slash-command parsing failure. It is related to, but distinct from, #16412 and #16535, where the picker did not appear visually or commands were not parsed.

The official slash-command documentation says typing / should display a selectable command list: https://learn.chatgpt.com/docs/reference/slash-commands