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
- Open Codex.
- Use a screen reader.
- Write a prompt and submit it.
- While Codex is generating the response, try to read/follow the latest output in the conversation.
- 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.
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
Actual behavior
Expected behavior
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.