codex - 💡(How to fix) Fix Accessibility: screen reader focus jumps to the top while Codex is generating output

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…

I am reporting a serious accessibility issue affecting screen reader users in Codex.

When I write a prompt and send it, then try to read the model output while it is being generated, the interface repeatedly moves my screen reader/reading position back to the very beginning of the conversation.

This makes it extremely difficult to follow the latest generated output, because I have to keep navigating back down to the end of the conversation again and again.

Root Cause

This makes it extremely difficult to follow the latest generated output, because I have to keep navigating back down to the end of the conversation again and again.

RAW_BUFFERClick to expand / collapse

Summary

I am reporting a serious accessibility issue affecting screen reader users in Codex.

When I write a prompt and send it, then try to read the model output while it is being generated, the interface repeatedly moves my screen reader/reading position back to the very beginning of the conversation.

This makes it extremely difficult to follow the latest generated output, because I have to keep navigating back down to the end of the conversation again and again.

Steps to reproduce

  1. Open Codex.
  2. Use a screen reader.
  3. Write a prompt and submit it.
  4. While Codex is generating the response, try to read/follow the latest output in the conversation.
  5. Press the button/control that should jump to the latest message or bottom of the conversation.

Actual behavior

  • The reading position/focus is repeatedly moved back to the top or beginning of the conversation.
  • The latest output becomes difficult to follow while it is being generated.
  • The jump-to-latest or scroll-to-bottom control does not keep the user at the latest output reliably.
  • This creates a very frustrating experience for screen reader users.

Expected behavior

  • Screen reader focus/reading position should not be reset to the top while Codex is generating output.
  • The user should be able to stay near the latest generated output.
  • The jump-to-latest or scroll-to-bottom control should work reliably with keyboard and screen readers.
  • New generated content should remain reachable/readable without stealing focus or resetting the reading position.

Impact

This is a major accessibility issue because it prevents screen reader users from reliably reading and following active Codex output as it is generated.

Environment

I can provide more details if needed, but the main issue is reproducible while using Codex with a screen reader and trying to read the generated output in real time.

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…

FAQ

Expected behavior

  • Screen reader focus/reading position should not be reset to the top while Codex is generating output.
  • The user should be able to stay near the latest generated output.
  • The jump-to-latest or scroll-to-bottom control should work reliably with keyboard and screen readers.
  • New generated content should remain reachable/readable without stealing focus or resetting the reading position.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Accessibility: screen reader focus jumps to the top while Codex is generating output