Claude Code Now Works With Screen Readers: A Deep Dive

Claude Code now works with screen readers thanks to a new dedicated mode from Anthropic. This update replaces the visual terminal interface with flat, linear text. Consequently, tools like VoiceOver and NVDA can parse output effectively. The engineering behind this feature goes deeper than a simple accessibility checkbox.

How Claude Code Now Works With Screen Readers

Standard terminal interfaces often confuse assistive technology. Box-drawing characters and spinners create meaningless noise when read aloud. Therefore, screen reader mode strips these visual elements away entirely.

Claude Code writes flat text without color-only cues or content redraws. Progress spinners become static text labels. Additionally, tables reformat into clear header-value sentences. Output accumulates in the scrollback buffer for easy review.

Every transcript section receives a searchable label. Prefixes include you:, claude:, and tool:. These labels help users jump between sections quickly during long sessions.

Activation Methods and Requirements

Anthropic provides three ways to enable this feature. First, use the --ax-screen-reader flag for single sessions. Alternatively, set the CLAUDE_AX_SCREEN_READER=1 environment variable for all shell sessions.

For machine-wide settings, add "axScreenReader": true to user settings. This method covers VS Code integrated terminals as well. The system confirms activation status on startup to prevent ambiguity.

Note that this mode requires Claude Code v2.1.181 or later. However, table reformatting specifically needs version v2.1.198. Remote SSH users should prefer environment variables over flags.

Navigation and Permission Prompts

Permission prompts transform into numbered lists in this mode. Developers type a number and press Enter instead of using arrow keys. Yes-or-no prompts accept typed y or n input.

The terminal bell signals important events audibly. It rings when replies finish or permission prompts appear. Furthermore, it alerts users when long-running tools complete. This prevents the need for continuous transcript monitoring.

Supported terminals also emit shell-integration markers at turn boundaries. This enables jump-to-previous-prompt navigation in iTerm2 and Windows Terminal. Such features improve quality of life for all users.

Additional Accessibility Settings

Other accessibility levers complement the new screen reader support. For example, CLAUDE_CODE_ACCESSIBILITY=1 keeps the cursor visible for magnifier users. The prefersReducedMotion setting disables animations without altering the interface.

Colorblind-friendly themes are also available via the theme setting. These options work alongside screen reader mode rather than replacing it. Thus, developers can combine multiple accessibility preferences without conflict.

Known Limitations and Future Steps

Anthropic remains transparent about current gaps. The mode requires explicit opt-in and does not activate automatically. Also, attaching to background sessions lacks native scrollback support.

Session costs appear only in the exit summary currently. Despite these limits, getting fundamentals right is a meaningful step. For a tool that has seen reliability issues, this progress matters. It opens agentic coding to developers previously excluded from the wave.