New Chat GPT Desktop app has accessibility issues including Jaws (screen reader for the blind) not reading chat names in history, and not treating new messages as headings users can easily navigate to
Open 💬 5 comments Opened Jul 19, 2026 by ShreyBhatt-108
What version of the Codex App are you using (From “About Codex” dialog)?
26.715.31251
What subscription do you have?
Chat GPT +
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
ChatGPT Desktop App Accessibility & Usability Issues
Accessibility
- New ChatGPT Desktop app has accessibility issues including JAWS (screen reader for the blind) not reading chat names in history.
- New messages are no longer exposed as headings, unlike the previous app where each turn had headings such as "You said" and "ChatGPT said". This prevents blind users from quickly navigating conversations using the H key in JAWS.
- The reasoning/model picker is not properly announced by JAWS, making it difficult to determine which option is currently selected or to interact with it confidently.
- Much of the Settings interface is inaccessible with JAWS. Beyond the General and About sections, many settings cannot be reached or read properly, and even finding the app version is difficult.
Feedback ID:
no-active-thread-019f7b91-001f-7f42-b1ca-2a0d8d6bdedf
What steps can reproduce the bug?
Feedback ID: no-active-thread-019f7b91-001f-7f42-b1ca-2a0d8d6bdedf
What is the expected behavior?
Jaws should be able to see each responce fromt the model and each responce from the human as new headings, so users can navigate to each message in the thred. This was not an issue in classic, only Codex. It is now an issue in the chat and codex sections of the new app. For the chat history, it should read "link {chat name}" not "archive chat delete chat" without a name. Again, this used to be a Codex only issue, now in chat, work, and codex.
Additional information
_No response_
5 Comments
I am a JAWS screen reader user who is also very disappointed with the direction of Codex and accessibility. I can confirm and have validated all the things you pointed out. In Antigravity, there is proper implementation that allows JAWS to even read the AI response automatically. For me, in codex, the inability to read recent chat is most frustrating of it all. These are regressive as the app was getting better and better until recent releases.
Thanks for confirming it is an issue for you too. And yes, the worst of it is the inability o read recent chat names. Though the chats not being headings is not easy either. Its a shame both AG and Claude Code are superior for accessibility, in UI and in Claude code's case, in TUI too.
Update: I’m very happy to confirm that most of the accessibility issues reported here have now been resolved.
JAWS correctly reads the chat names in the history, and messages within conversations are now exposed as headings, allowing screen-reader users to navigate between them efficiently. These changes make a meaningful difference for blind users, and I sincerely appreciate everyone who contributed to the improvements.
One issue still remains: the model picker is not especially clear or intuitive when using a screen reader. It can be difficult to determine the currently selected model and understand the available options confidently.
Since that issue is still present, I’m leaving this report open for now. Thank you again to OpenAI for the accessibility improvements that have already been made.
Hi! It's great to hear that many of these issues have been resolved.
I agree that it's difficult to tell which model is currently selected. My workaround is to open the model picker a couple of times and simply select the model I want again. It's not ideal, but at least it makes me reasonably confident that the correct model is selected. 😊
The Reported issues were resolved! They were resolved very quickly. Thank you to the Codex team for your commitment to accessibility.
From: Mina @.*>
Sent: Monday, July 27, 2026 2:14 PM
To: openai/codex @.*>
Cc: Ralcidonis @.>; Comment @.>
Subject: Re: [openai/codex] New Chat GPT Desktop app has accessibility issues including Jaws (screen reader for the blind) not reading chat names in history, and not treating new messages as headings users can easily navigate to (Issue #34211)
<https://avatars.githubusercontent.com/u/309846625?s=20&v=4> Hekland-M left a comment (openai/codex#34211) <https://github.com/openai/codex/issues/34211#issuecomment-5095062269>
Hi! It's great to hear that many of these issues have been resolved.
I agree that it's difficult to tell which model is currently selected. My workaround is to open the model picker a couple of times and simply select the model I want again. It's not ideal, but at least it makes me reasonably confident that the correct model is selected. 😊
—
Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/34211?email_source=notifications&email_token=AQCIPTYRQMLI6WD453A6EL35G6LXNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGUYDMMRSGY42M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5095062269> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQCIPT6CSJ2JTZSC7L2UZAT5G6LXNAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TIOJSGM4DQMJRGM3KC5QC> .
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AQCIPT32MQFG7PQJRR7SAG35G6LXPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGUYDMMRSGY42M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AQCIPTYXWQ3DIBFE4UXX4PD5G6LXPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBZGUYDMMRSGY42M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI> . Download it today!
You are receiving this because you commented. <https://github.com/notifications/beacon/AQCIPT5IIFTEB7FPMGZOPZD5G6LXPBFCNFSM6AAAAAC35ZBMN2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTYAAAAACL5QPL62M4TFMFZW63VHMNXW23LFNZ2A.gif> Message ID: @. @.> >