Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [A11y bug] Missing heading semantics and "response complete" announcements in desktop app

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 Claude Code desktop app does not provide the heading structure or response-completion cues that the Claude.ai web app provides. This is a regression in accessibility parity between two surfaces of the same product.

Root Cause

The Claude Code desktop app does not provide the heading structure or response-completion cues that the Claude.ai web app provides. This is a regression in accessibility parity between two surfaces of the same product.

RAW_BUFFERClick to expand / collapse

Summary

The Claude Code desktop app does not provide the heading structure or response-completion cues that the Claude.ai web app provides. This is a regression in accessibility parity between two surfaces of the same product.

Impact

As a blind VoiceOver user, in the Claude.ai web app I can:

  • Use VoiceOver rotor to jump between headings in a response.
  • Hear a clear announcement when Claude has finished streaming a response.

In the Claude Code desktop app, neither of these works. Claude's output appears as flat text with no navigable heading landmarks, and there is no reliable cue that the response is complete. I end up arrow-keying through the entire output or guessing when it's safe to start typing again.

Expected

  • Markdown headings in Claude's response render as proper heading landmarks (H1/H2/H3) so VoiceOver rotor can navigate them.
  • A clear announcement (live region, system notification, or focus change) fires when Claude finishes streaming a response, matching the Claude.ai behavior.

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.

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…
#request error#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING