[DOCS] Accessibility env var docs omit dialog tab cursor tracking

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/env-vars

Section/Topic

CLAUDE_CODE_ACCESSIBILITY environment variable and dialog tab navigation

Current Documentation

The docs currently say:

CLAUDE_CODE_ACCESSIBILITY | Set to 1 to keep the native terminal cursor visible and disable the inverted-text cursor indicator. Allows screen magnifiers like macOS Zoom to track cursor position

They also separately document dialog tab navigation:

Left/Right arrows | Cycle through dialog tabs | Navigate between tabs in permission dialogs and menus

tabs:next | Tab, Right | Next tab tabs:previous | Shift+Tab, Left | Previous tab

What's Wrong or Missing?

The current docs explain two pieces separately, but not the accessibility behavior that connects them.

A. The accessibility entry is too narrow

The CLAUDE_CODE_ACCESSIBILITY entry only mentions keeping the native terminal cursor visible so screen magnifiers can track cursor position. It does not say that the native cursor is also expected to follow the currently selected tab in dialogs and menus.

B. Screen reader support is not mentioned

The docs do not mention screen readers at all for this feature, even though changelog v2.1.94 describes dialog-tab cursor tracking specifically as an accessibility improvement for both screen readers and magnifiers.

C. The tab-navigation docs lack the accessibility prerequisite/context

The dialog tab shortcut docs explain how to move between tabs, but they do not tell assistive-technology users that CLAUDE_CODE_ACCESSIBILITY=1 is the relevant setting for making tab selection trackable via the native terminal cursor.

Changelog v2.1.94 confirms this is intended user-facing behavior:

Fixed native terminal cursor not tracking the selected tab in dialogs, so screen readers and magnifiers can follow tab navigation

Suggested Improvement

Update the CLAUDE_CODE_ACCESSIBILITY documentation to state that accessibility mode keeps the native terminal cursor synchronized with focus changes in tabbed dialogs/menus, not just text input.

Specifically, the docs should mention that when CLAUDE_CODE_ACCESSIBILITY=1 is set, the selected tab in dialogs can be followed by assistive technologies during Left/Right or Tab/Shift+Tab navigation.

Add a short cross-reference or note in the tab-navigation docs (interactive-mode and/or keybindings) so users looking up dialog shortcuts can discover the accessibility setting.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/env-vars | 53 | CLAUDE_CODE_ACCESSIBILITY mentions magnifiers tracking cursor position, but not screen readers or dialog tab focus |
| https://code.claude.com/docs/en/interactive-mode | 37 | Documents Left/Right arrows for dialog tabs without accessibility guidance |
| https://code.claude.com/docs/en/keybindings | 202-203 | Documents tabs:next / tabs:previous without noting assistive-technology cursor tracking |

Total scope: 3 pages affected

Source: Changelog v2.1.94

Exact changelog entry:

Fixed native terminal cursor not tracking the selected tab in dialogs, so screen readers and magnifiers can follow tab navigation