Skip to content

fix(a11y): remove aria-hidden from streaming assistant content - #33139

Closed
ashu-choudhury wants to merge 2 commits into
anomalyco:devfrom
ashu-choudhury:fix/accessibility-thinking-content
Closed

ashu-choudhury wants to merge 2 commits into
anomalyco:devfrom
ashu-choudhury:fix/accessibility-thinking-content

Conversation

@ashu-choudhury

@ashu-choudhury ashu-choudhury commented Jun 20, 2026 •

Copy link
Copy Markdown

Issue for this PR

Closes #33137

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

While testing with NVDA, I noticed that assistant content is hidden from the accessibility tree while a response is being generated.

The assistant content container is rendered with:

aria-hidden={workingTurn(assistantPartRow().userMessageID)}

This prevents screen reader users from accessing streamed assistant content, tool activity, and progress information that is visible on screen.

This change removes the aria-hidden attribute from the assistant content container so streamed content remains accessible during generation.

How did you verify your code works?

Tested locally with NVDA on Windows.

Before this change, NVDA could access the thinking status but not the streamed assistant content while generation was in progress.

After this change, NVDA can access the streamed assistant content during generation.

Screenshots / recordings

Not provided.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@github-actions github-actions Bot added needs:compliance This means the issue will auto-close after 2 hours. and removed needs:compliance This means the issue will auto-close after 2 hours. labels Jun 20, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for updating your PR! It now meets our contributing guidelines. 👍

@github-actions

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Screen readers cannot access streaming assistant content while a response is generating

1 participant