It had all those issues until last friday for me as well; but now whatever the response is I can read it with voiceover without needing to refresh the page.
What I just realized is that VoiceOver still skips some list items if there’s a list in ChatGPT’s response. Another problem is VoiceOver announcing groups that aren’t actually groups; it’s just the written ChatGPT response. But this is much better than being unable to read the response entirely without refreshing the page.
For me, I've wasn't able to read the response at all until last friday, now the issue is mostly gone; it's just lists that are kind of still problematic.
After updating to macOS 15.5 beta 4, the problem still occurs, although now the responses from GPT are accessible partially. The issue still occurs even when the GPT response is not formatted as a list, but when it's just a text.
Totally annoyed, I sent them today a rather long report describing the whole situation. BTW, I also mentioned the poor optimization of the GPT app on macOS for VoiceOver and its various other shortcomings taking into account the inaccessibility of the sidebar and thus the conversation history, projects or Custom GPTs. In the web version, projects used to be more accessible and now they aren't actually at all.
It's definitely VoiceOver specific and interconnected with an issue that prevents VoiceOver from accessing elements in one navigation order (from top to bottom) in DOM navigation mode. WebKit experience is full of bugs regarding accessibility, unfortunately, with some of them are long-standing issues, and some are fixed for a few months and then come back.
I'm using Chrome. I've seen a lot of changes in how I'm able to navigate, read, and not read ChatGPT's output. I get very different results whether I navigate forward or backward. My usual strategy is to use the VO+U web rotor, Form Controls menu to find the Copy button so I can paste the text for review in another app.
ChatGPT seems to format its output with markdown. The problem is that the server isn't converting from markdown to html, so all the raw markdown syntax is presented to the user, such as asterisks for emphasis and hashtag symbols for headings. The screen reader verbalizes the markdown, which impedes comprehension. Does anyone know a way to turn it off?
I've found I can tell ChatGPT to turn it off, which is partially effective for the remainder of the current conversation. But this isn't a setting it remembers.
As of macOS Sequoia 15.5, may 21st.
I haven't done anything but the issue with VO is completely gone, even bullet list. Don't need to refresh the page anymore after each prompt.
EDIT: I was again too early. Partially gone, in a random list of 6 elements it reads only the first and last element... Very weird.
yes it now works as expected and the accessibility is progressed a lot in chatgpt. I did not need to refresh the page and even navigate sections when in a proper conversation. So there are bug fixes introduced for sure.
I want to start by noting that I can read the plain text output, but I still have problems with the lists, so the issue isn't resolved for me yet. I'm still on macOS 15.4.1, though. What I don't understand is, during all this time we've had these bugs with the ChatGPT website using VoiceOver on Safari, Windows/NVDA users or even Chrome users on Mac didn’t have this issue. So, I understand this is likely a problem with WebKit, or whatever engine Safari/VoiceOver uses. But then—what fixed the issue, and who did it? Did OpenAI release an update specifically for VoiceOver users on Safari? Apple couldn’t have done it, since they haven’t released a software update or anything else that could have fixed it. So who's to blame?
So I had cleared my history and cache.
I have tried with single and multiple tabs (well 2 tabs actually ).
Till now it is working. And yes it absolutely needed refresh before I upgraded the OS today.
I have never used gpt on Safari, only on iOS through the app, and as a PWA on Windows. And from the sound of it, I made the right call not even attempting it on the mac with how buggy it can get from day to day.
I thought the issue was fixed for a while, but It's impossible once again to navigate between the list items in ChatGPT's output… This is one of the most nonsensical bugs. The other ridiculous one was the playback speed menu on YouTube on iOS.
Today with safari, after cleen reboot, latest stable version, on chatgpt with lits even when after refreshing the page lists items are partially read when navigating from left to right with vo right arrow, I have to go one item next to it, then vo left arrow again to have the previous item fully read.
It also seems to be related to the fact that the bullet is viewed as a separate item before the actual list item announced. I can't really use arrow keys and option left and right arrow to read in lists because the words are half trimmed and/or concatenated, which is a long standing bug present when I started my mac experience on Ventura.
Thanks for reading :(
While I am pretty much still able to use chatgpt without a refresh now, I do face the partial reading or "not reading " of lines as others have reported. I am able to structurally navigate the headings and also able to copy properly. But partial skipping of lines still happens. By the way it is curious that anything to do with source code (I being a software engineer ) is read correctly.
I'll let you decide yourself whether upgrading to Tahoe is worth it or not.
But now I don't have any problem (so far) reading chatgpt output, short, long, lists, nested lists, on safari. No refresh needed.
Comments
I really, really hope you…
I really, really hope you are right on this one.
Incredibly strange...
It had all those issues until last friday for me as well; but now whatever the response is I can read it with voiceover without needing to refresh the page.
Oh noo...
What I just realized is that VoiceOver still skips some list items if there’s a list in ChatGPT’s response. Another problem is VoiceOver announcing groups that aren’t actually groups; it’s just the written ChatGPT response. But this is much better than being unable to read the response entirely without refreshing the page.
Yay.
Yay.
@theBlindGuy07?
Wait, is the issue mostly gone for you as well?
@Oliver
For me, I've wasn't able to read the response at all until last friday, now the issue is mostly gone; it's just lists that are kind of still problematic.
Unfortunately, i've stil this problem!
After updating to macOS 15.5 beta 4, the problem still occurs, although now the responses from GPT are accessible partially. The issue still occurs even when the GPT response is not formatted as a list, but when it's just a text.
Totally annoyed, I sent them today a rather long report describing the whole situation. BTW, I also mentioned the poor optimization of the GPT app on macOS for VoiceOver and its various other shortcomings taking into account the inaccessibility of the sidebar and thus the conversation history, projects or Custom GPTs. In the web version, projects used to be more accessible and now they aren't actually at all.
It's just terrible to me!
It's back
It's back guys, this is soooooo weird.
It's definitely VoiceOver…
It's definitely VoiceOver specific and interconnected with an issue that prevents VoiceOver from accessing elements in one navigation order (from top to bottom) in DOM navigation mode. WebKit experience is full of bugs regarding accessibility, unfortunately, with some of them are long-standing issues, and some are fixed for a few months and then come back.
Not just Safari
I'm using Chrome. I've seen a lot of changes in how I'm able to navigate, read, and not read ChatGPT's output. I get very different results whether I navigate forward or backward. My usual strategy is to use the VO+U web rotor, Form Controls menu to find the Copy button so I can paste the text for review in another app.
The coppy button
No need to reach for the coppy button all the time, do command plus shift plus C instead and the output will be copied!
Any way to turn off formatting?
I apologize for this slight tangent.
ChatGPT seems to format its output with markdown. The problem is that the server isn't converting from markdown to html, so all the raw markdown syntax is presented to the user, such as asterisks for emphasis and hashtag symbols for headings. The screen reader verbalizes the markdown, which impedes comprehension. Does anyone know a way to turn it off?
I've found I can tell ChatGPT to turn it off, which is partially effective for the remainder of the current conversation. But this isn't a setting it remembers.
Gone now on safari
As of macOS Sequoia 15.5, may 21st.
I haven't done anything but the issue with VO is completely gone, even bullet list. Don't need to refresh the page anymore after each prompt.
EDIT: I was again too early. Partially gone, in a random list of 6 elements it reads only the first and last element... Very weird.
Happy to note that it works perfectly.
yes it now works as expected and the accessibility is progressed a lot in chatgpt. I did not need to refresh the page and even navigate sections when in a proper conversation. So there are bug fixes introduced for sure.
The thing messes with me...
I want to start by noting that I can read the plain text output, but I still have problems with the lists, so the issue isn't resolved for me yet. I'm still on macOS 15.4.1, though. What I don't understand is, during all this time we've had these bugs with the ChatGPT website using VoiceOver on Safari, Windows/NVDA users or even Chrome users on Mac didn’t have this issue. So, I understand this is likely a problem with WebKit, or whatever engine Safari/VoiceOver uses. But then—what fixed the issue, and who did it? Did OpenAI release an update specifically for VoiceOver users on Safari? Apple couldn’t have done it, since they haven’t released a software update or anything else that could have fixed it. So who's to blame?
Just updated to the mac OS 15.5 and the issue still exist
Yeah... Great!
Still working for me, but may be
So I had cleared my history and cache.
I have tried with single and multiple tabs (well 2 tabs actually ).
Till now it is working. And yes it absolutely needed refresh before I upgraded the OS today.
I emptied the cache, and the issue is gone now.
Title says it all... I hope it never comes back again.
I have never used gpt on…
I have never used gpt on Safari, only on iOS through the app, and as a PWA on Windows. And from the sound of it, I made the right call not even attempting it on the mac with how buggy it can get from day to day.
@Oliver
If you enable the developer tools on safari; you'll find the option in safari menu/develop/empty cache...
It's back...
I thought the issue was fixed for a while, but It's impossible once again to navigate between the list items in ChatGPT's output… This is one of the most nonsensical bugs. The other ridiculous one was the playback speed menu on YouTube on iOS.
Today with safari, after…
Today with safari, after cleen reboot, latest stable version, on chatgpt with lits even when after refreshing the page lists items are partially read when navigating from left to right with vo right arrow, I have to go one item next to it, then vo left arrow again to have the previous item fully read.
It also seems to be related to the fact that the bullet is viewed as a separate item before the actual list item announced. I can't really use arrow keys and option left and right arrow to read in lists because the words are half trimmed and/or concatenated, which is a long standing bug present when I started my mac experience on Ventura.
Thanks for reading :(
Lines getting partially skipped.
While I am pretty much still able to use chatgpt without a refresh now, I do face the partial reading or "not reading " of lines as others have reported. I am able to structurally navigate the headings and also able to copy properly. But partial skipping of lines still happens. By the way it is curious that anything to do with source code (I being a software engineer ) is read correctly.
@kk_macker
Yes :)
By the way it is curious that anything to do with source code (I being a very bad student lol) is read correctly.
*Seemed* fixed on Tahoe
I'll let you decide yourself whether upgrading to Tahoe is worth it or not.
But now I don't have any problem (so far) reading chatgpt output, short, long, lists, nested lists, on safari. No refresh needed.