Around March 17, the browser interface to ChatGPT appears to have changed. I'm on Sequoia using Google chrome. I wanted to describe the behavior and see if it existed on Tahoe, or in other browsers.
After entering a prompt and pressing enter, I now hear "Thinking," followed by silence, until the response is read aloud. I'm certain it used to say something like "ChatGPT is writing a response," and possibly repeat that message after some time had elapsed. But there is no longer a repeated message.
The button below each response used to be labeled "Copy." It is now labeled "Copy response," and the button below user prompts is different, "Copy message." This is actually useful, as it helps me avoid copying the wrong text.
When VoiceOver reads the response, for some reason it now seems to trim the final few words. This is perhaps the most concerning new development. We no longer get complete responses. We must navigate into the response and have VoiceOver repeat it in order to hear the text in full.
After a response is read aloud, VoiceOver focus used to be left in the "Ask anything" prompt field. It's now somewhere else, and I'm unsure where. If I simply begin typing a new prompt, focus jumps to the prompt entry field, so that still works as expected. But if I instead navigate with VO+left or right, I no longer move to the same controls as before.
Finally, four buttons: Copy Response, Good Response, Bad Response, and More Actions now seem to be wrapped in a pointless container or group that announces itself as I enter and leave these four controls. Unnecessary screen reader verbiage that adds no value or clarity to the experience.
So, as I said, I'm just checking to see if these issues persist in other browsers, or if upgrading to Tahoe would somehow magically restore the old functionality.
Comments
same on Safari
It's the same using Safari. I don't even get the message read back to me, like the response from ChatGPT, I have to manually check.
possably a Mac issue?
That sounds like a Mac-specific issue. On Windows, it still says “thinking,” and it will automatically read out the response—but you no longer get the incremental updates every few seconds like before. Instead, it just says “thinking” and then speaks the full result once it’s ready.
What I usually do is stop the speech with Control, then go back and read it manually. They’ve also changed the heading level from level 6 to level 4, which is worth noting.
If the Mac version is anything like iOS, I can understand the frustration. On iOS, it used to be better—you could easily go back and read responses manually. You could also delete conversations quickly using the actions rotor: just delete, delete, delete.
Now it’s much more fiddly. You have to triple-tap the conversation, find “Delete,” and then confirm it each time.
Maybe enable live regions?
This is a setting that, when enabled, will allow VoiceOver to read out dynamic updates to webpages and/or applications. It might help with ChatGPT for Mac. 😊
Same on Safari on 26.3.2
I thought I changed a setting in my VoiceOver settings and that was causing this. On my side, it says "thinking" and doesn't read the answers. Someone was talking about live regions. How do we enable this. I'm happy to know that I'm not alone to have this problem. I am on the latest macOS version: 26.3.2 on a macbook neo.
Best,
Olivier
@Olivier
To enable Live Regions:
1. Open voice over utility on macOS by pressing control plus Option plus FN/Globe key plus F8.
2. Navigate to the "Web" category.
3. Check the box next to "Live Regions".
HTH.
Thoughts
After ChatGPT reads its response, I've discovered that it leaves VoiceOver focus at the bottom of the response. That's actually an improvement, in my opinion, as it makes it easier to navigate through a response with multiple paragraphs.
And for whoever noted that ChatGPT uses headings, thanks. That gives me a quick way to move through the chat.
The iOS app is an option, and it actually works better for long chats than a web browser and MacOS. But if I'm on MacOS, which I am most of the time, then swapping to the iPhone is inconvenient.