claude-code - 💡(How to fix) Fix [A11y bug] Permission prompts in desktop app are silent to VoiceOver

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The permission dialog in the Claude Code desktop app (the one asking to run a command, edit a file, or call a tool) is not announced by VoiceOver. There is no auditory cue, no focus change, nothing to tell a screen reader user that Claude is blocked waiting on a decision.

Root Cause

The permission dialog in the Claude Code desktop app (the one asking to run a command, edit a file, or call a tool) is not announced by VoiceOver. There is no auditory cue, no focus change, nothing to tell a screen reader user that Claude is blocked waiting on a decision.

Fix Action

Workaround

I built a hook-based workaround using PermissionRequest + say. Setup writeup with full scripts: shared in the Claude users community. Happy to share here on request. It works, but a blind user should not need to build this.

RAW_BUFFERClick to expand / collapse

Summary

The permission dialog in the Claude Code desktop app (the one asking to run a command, edit a file, or call a tool) is not announced by VoiceOver. There is no auditory cue, no focus change, nothing to tell a screen reader user that Claude is blocked waiting on a decision.

Impact

As a blind daily VoiceOver user, this is the single biggest blocker for me using Claude Code productively. If I step away from the keyboard or focus on another window, the session sits idle until I happen to check. The prompt is effectively invisible.

Reproduction

  1. Launch the Claude Code desktop app on macOS with VoiceOver enabled.
  2. Ask Claude to do anything that triggers a permission prompt (e.g. run a shell command).
  3. The dialog appears silently. VoiceOver does not announce it, focus does not move to it in a way that is audible.

Expected

  • Permission dialog fires a native accessibility notification on appearance.
  • Dialog is focusable and labeled so VoiceOver announces it.
  • The action/tool name and any relevant arguments are part of the announcement (e.g. "Permission required: run ping example.com").

Workaround

I built a hook-based workaround using PermissionRequest + say. Setup writeup with full scripts: shared in the Claude users community. Happy to share here on request. It works, but a blind user should not need to build this.

Context

I submitted the same feedback via the in-app /feedback channel and to [email protected] so the team can dedupe.

I am Lead Accessibility Architect at Paramount Streaming. Happy to test fixes, share my hook config, or collaborate on a proper solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING