When typing on google translator, nvda informs the existence of a menu where it is not possible to interact with the resource

[fernando-jose-silva]

Steps to reproduce:

open the google translator.
start typing some text to translate.
You will hear menu.
Try pressing directional arrows or enter.

Actual behavior:

the nvda will be mute

Expected behavior:

this appears to be a word suggestion feature.
When the nvda announces menu there appears to be a list of word suggestions displayed, and with the arrows below you choose a suggestion.
The nvda must have a way for the user to interact with this menu, without the user also being unable to revise the currently inserted text with the arrows.
Or if convenient, nvda can automatically announce suggestions, and the user must have a way to accept the suggestion perhaps by pressing space like it does on smartphone keyboards.

System configuration

NVDA installed/portable/running from source:

portable

NVDA version:

alfa 19604

Windows version:

10 1909

Name and version of other software in use when reproducing the issue:

chrome 79

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

no
log:
tradutor.txt

[Adriani90]

@fernando-jose-silva on NVDA alpha 19604,7773e8ff and Chrome 79 I cannot reproduce this. There are no suggestions displayed and when I am typing there is nothing like "menu" reported.
Could you elaborate more on your chrome settings? Are you using the translator we app? Or the translator website?

[fernando-jose-silva]

this is on google online translator Enviado do meu iPhone

…

Em 4 de fev de 2020, à(s) 18:40, Adriani90 ***@***.***> escreveu:  @fernando-jose-silva on NVDA alpha 19604,7773e8ff and Chrome 79 I cannot reproduce this. There are no suggestions displayed and when I am typing there is nothing like "menu" reported. Could you elaborate more on your chrome settings? Are you using the translator we app? Or the translator website? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Adriani90]

I can reproduce this in every browser (Chrome 81, Firefox 76 and Edge Chromium 81). It seems NVDA does not recognize the word suggestions and "object replacement character" is reported when pressing enter on a word suggestion.

[Adriani90]

@fernando-jose-silva this menu with the suggestions is now working only in Firefox. in Chrome or Edge there is no menu displayed. Can you test if this issue still occurs for you in Chrome or Edge 112?

[fernando-jose-silva]

in chrome it could be some setting, in my chrome the suggestions are shown in the menu and are announced by nvda.
The problem I encountered is that once in the word suggestion list I couldn't close the suggestions on pressing esc, even if I press esc the word suggestion is entered.
I don't know if nv access can do everything in this case or if it's a problem with the chrome interface.

[Adriani90]

@fernando-jose-silva how is this on your side with NVDA 2023.2 and Chrome 116? Can you still reproduce this? On my end NVDA does not report any suggestions or menu with suggestions at all. I think this feature with suggestions has been removed from translate if i am not wrong.

[fernando-jose-silva]

Thank you very much, I still find nvda's ads very strange in Google Chrome, but that's a subject for new tickets.I can still see the suggestion menus, but nvda now reads them correctly.I believe we can close this call.Enviado do meu iPhoneEm 5 de set. de 2023, à(s) 14:45, Adriani90 ***@***.***> escreveu: @fernando-jose-silva how is this on your side with NVDA 2023.2 and Chrome 116? Can you still reproduce this? On my end NVDA does not report any suggestions or menu with suggestions at all. I think this feature with suggestions has been removed from translate if i am not wrong. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[Adriani90]

Ok thanks, I am closing this as works for me as per comment above.