You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
go to https://chat.openai.com/
signin with your preferred method. You'll see that NVDA fall out into a "dialog" and you can't write anything. You must press ctrl-nvda-space for exiting object. Then you can write, but when ChatGpt composes an answer, the cursor return to the invisible dialog.
Other screen reader doesn't have this behaviour.
Expected behavior:
NVDA should ignore the invisible dialog.
System configuration
NVDA 2024.4 all versions.
Windows version:
win10 and win11.
Name and version of other software in use when reproducing the issue:
Chrome, Edge Firefox, Brave, all versions.
I'm aware that this is probably not a real NVDA bug, but as mentioned, all other screen readers ignore the dialog that appears, and I had to point it out somehow!
The text was updated successfully, but these errors were encountered:
This is very likely a problem with the implementation of the application/website, as a starting point please submit feedback to the authors to let them know about the problem.
Steps to reproduce:
Actual behavior:
go to
https://chat.openai.com/
signin with your preferred method. You'll see that NVDA fall out into a "dialog" and you can't write anything. You must press ctrl-nvda-space for exiting object. Then you can write, but when ChatGpt composes an answer, the cursor return to the invisible dialog.
Other screen reader doesn't have this behaviour.
Expected behavior:
NVDA should ignore the invisible dialog.
System configuration
NVDA 2024.4 all versions.
Windows version:
win10 and win11.
Name and version of other software in use when reproducing the issue:
Chrome, Edge Firefox, Brave, all versions.
I'm aware that this is probably not a real NVDA bug, but as mentioned, all other screen readers ignore the dialog that appears, and I had to point it out somehow!
The text was updated successfully, but these errors were encountered: