Open fernando-jose-silva opened 2 months ago
Hi @fernando-jose-silva,
We couldn't reproduce this locally. I think you need to report this to Google. It seems like their UX is evolving here, as we are getting different A/B environments so this cannot be reproduced easily.
We need a minimal HTML sample to reproduce this using codepen from the developers.
Kind Regards, NV Access Software Developers
Just to mention that I also encounter this issue.
To reproduce with default auto focus mode:
Expected: NVDA should switch to focus mode. Actual: no switch
@seanbudd just to be sure, would you mind re-test it with these steps?
Note: I am not able to provide minimal html samples from an issue seen on a webpage. Have you tutorials/wikis to recommend for this?
Thank you very much for your attention.Cyrille Bougot Enviado do meu iPhoneEm 27 de ago. de 2024, à(s) 05:11, Cyrille Bougot @.***> escreveu: Just to mention that I also encounter this issue. To reproduce with default auto focus mode:
Go to Gemeni webpage and log in if not already You should end up in the edit field and in focus mode Press NVDA+space to switch to browse mode Press control+home to go to the beginning of the page press E to got to the edit field (still in browse mode for now) press space
Expected: NVDA should switch to focus mode. Actual: no switch @seanbudd just to be sure, would you mind re-test it with these steps? Note: I am not able to provide minimal html samples from an issue seen on a webpage. Have you tutorials/wikis to recommend for this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Reopening for investigation with new STR, however I'd encourage directly reporting this to Google. It's unlikely we will fix this unless it seems to be an NVDA issue and it is a persistent issue as the interface evolves.
@Adriani90 are you able to reproduce? If yes, would you be able to create a minimal code example from this?
Steps to reproduce:
go to the gemini website https://gemini.google.com/app
After making the current options such as accepting contracts and logging into google. It is important to mention that my nvda is configured so that it does not automatically switch between focus and navigation mode:
Enable navigation mode when loading page checkbox checked Alt+ e Automatic Continuous Reading when loading page checkbox not checked Alt+ t Include presentation tables checkbox not checked Alt+ a Automatic focus mode when focus changes checkbox not checked Automatic focus mode when application cursor changes checkbox not checked Sound indication of change between focus and navigation mode checkbox not checked Capture everything that is not a command so that it does not reach the document checkbox checked Automatically position system focus on focusable elements checkbox not checked Alt+ f
press ctrl + home to be at the beginning of the page. Press e to be in the first edit box. nvda announces: clickable Enter command here multiline editing Enter a question or command press enter
Actual behavior:
nvda does not enable focus mode
Expected behavior:
nvda enters focus mode. Relevant information, if you force nvda to enter focus mode with nvda + space, the typed text is entered in the gemini text box. If you press the down arrow, nvda will display a blank text, and pressing enter will also enter focus mode.
But I don't think it's ideal, the ideal would be to press the letter e and then enter and nvda will enter focus mode.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
instaled
NVDA version:
nvda.exe, NVDA alpha-33464,df6bd077
Windows version:
10 19045
Name and version of other software in use when reproducing the issue:
chrome.exe, Google Chrome 127.0.6533.120
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
no
If NVDA add-ons are disabled, is your problem still occurring?
yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
yes