Answer: The known limitations include that screen reader mode doesn't turn on automatically when a screen reader is running, Claude Code doesn't announce a permission mode change made with a command such as entering plan mode with /plan, attaching to a background session enters the terminal's alternate screen with no native scrollback, costs are announced in the summary at exit rather than per turn, and screen reader mode doesn't change non-interactive mode with the -p flag. Status: Confirmed Entry: tool/claude-code/troubleshooting/screen-reader-limitations Revision: 1 Digest: sha256:62be9d95f8f6cd6f (changes whenever the content changes) Timeline: Created: 2026-11-15T12:15:32Z Last changed: 2026-11-15T12:15:32Z Last verified: 2026-11-20T12:16:07Z Next check: 2026-11-21T12:16:07Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of auto-enable limitation | Screen reader mode doesn't turn on automatically when a screen reader is running. | [1] | 2026-11-20 permission mode announcement limitation | Claude Code doesn't announce a permission mode change you make with a command | [1] | 2026-11-20 background session limitation | enters the terminal's alternate screen, which has no native scrollback | [1] | 2026-11-20 cost announcement limitation | Claude Code announces costs in the summary it prints at exit, not per turn. | [1] | 2026-11-20 Sources: [1] Anthropic. "Use Claude Code with a screen reader". https://code.claude.com/docs/en/accessibility.md Role: primary. Accessed: 2026-11-20T12:16:07Z Quote: "Screen reader mode doesn't turn on automatically when a screen reader is running." (Supports: auto-enable limitation) Quote: "Claude Code doesn't announce a permission mode change you make with a command" (Supports: permission mode announcement limitation) Quote: "enters the terminal's alternate screen, which has no native scrollback" (Supports: background session limitation) Quote: "Claude Code announces costs in the summary it prints at exit, not per turn." (Supports: cost announcement limitation) Published: 2026-11-20T04:10:57Z Snapshot SHA-256: 4a617a2206f1b87f8cf2ce101b0f6ecfdf32bcea5a06ded8ac8e84df8256962b (captured 2026-11-13T03:02:32Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-15T12:15:32Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:16:07Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:16:07Z Last attempt: 2026-11-20T12:16:07Z Notes and limitations: Extracted automatically from a single official source (section "Known limitations"). Related: https://latestn.com/tool/claude-code/troubleshooting/simulator-pane-not-opening Why doesn't the iOS Simulator pane open when Claude runs my app in Claude Code? https://latestn.com/tool/claude-code/troubleshooting/skill-not-triggering Why is my Claude Code skill not triggering? https://latestn.com/tool/claude-code/troubleshooting/slack-repo-not-showing Why isn't my repository showing in Claude Code in Slack? https://latestn.com/tool/claude-code/troubleshooting/run-test-loop How do I run the test loop to verify a self-hosted runner image in Claude Code? https://latestn.com/tool/claude-code/troubleshooting/sandbox-troubleshooting How do I fix Claude Code sandbox errors like host-not-allowed or commands failing to reach localhost? https://latestn.com/tool/claude-code/troubleshooting/scheduled-tasks-limitations What are the limitations of session-scoped scheduled tasks in Claude Code? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-15T12:15:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/troubleshooting/screen-reader-limitations/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/troubleshooting/screen-reader-limitations POST: https://latestn.com/dispute/tool/claude-code/troubleshooting/screen-reader-limitations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/troubleshooting/screen-reader-limitations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the known limitations of using Claude Code with a screen reader? Revision 1, last verified 2026-11-20T12:16:07Z. https://latestn.com/tool/claude-code/troubleshooting/screen-reader-limitations (accessed 2026-11-21T09:54:08Z). @misc{LatestN_tool_claude_code_troubleshooting_screen_reader_limitations_r1, title = {What are the known limitations of using Claude Code with a screen reader?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/troubleshooting/screen-reader-limitations}}, note = {Revision 1; digest sha256:62be9d95f8f6cd6f; last verified 2026-11-20T12:16:07Z; accessed 2026-11-21T09:54:08Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/troubleshooting/screen-reader-limitations