When we are pressing the tab key, Keyboard focus moves to hidden control and gets lost completely on dismissing 'Find & Replace' popup:A11y_Monacoeditor_Focusorder.

[AnKushSingh05]

GitHubTags:

#A11yTCS;#Desktopweb;#Win11;#Visual Studio Code Client;#VisualStudioCode-Web-Apr2021;#a11y-monacoeditor;#Keyboard;#WCAG2.4.3;#A11yMAS;#A11ySev2;#SCIM:bug29252070;

Environment Details:

#URL: Monaco Editor (microsoft.github.io)
Monaco Editor
Chromium edge Version: 126.0.2592.68 (Official build) (64-bit).

Repro Steps:

1. Hit the URL: https://microsoft.github.io/monaco-editor/playground.html?source=v0.40.0-dev.20230707#XQAAAAJzAQAAAAAAAABBqQkHQ5NjdMjwa-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWSxW3yscwzfibW_1uhs0-3YGTBOsVJ4S4FwfCDQb5-2uUHXTVAefbVSd9IzaZ_vv9VR9KugsKimARHSWlrTPOQHROITHxmAetfeRrm3VHdSe7_Etv6WpgzlH4vE8EOD3EPhJDl6tDpOO8RxKZbUytKns3T0NFFloo9Q21KsEBT298I6cyZc5-Glup9UHU6QTpv2Hjab6pZzB3ZO2RH-WGhzXse2-hNlgz6zCgsG8AjiqGg0ZzWzND7z09NmCQOQd6pfkNvO2zmMzFvHpTY8RFEy1urlQcQMb1HHLEESBi8m3Rr3UzFlKzY51hfYcz__QCePc and press enter
2. Tab till Monaco editor code.
3. Press Ctrl+F to open the find and replace popup
4. Verify whether When we are pressing the tab key, Keyboard focus moves to hidden control and gets lost completely on dismissing 'Find & Replace' popup

Actual Behavior

When we are pressing the tab key, Keyboard focus moves to hidden control and gets lost completely on dismissing 'Find & Replace' popup

Expected Behavior

Keyboard focus should be visible properly on dismissing 'Find & Replace' popup and navigating using the tab key.

User Impact:

Keyboard users will get confused where the keyboard focus is going if it is going to hidden control.

Attachment:

Bug_4670_Focusorder1.mp4

[AnKushSingh05]

SCIM:bug
29252070

[meganrogge]

This seems like an invalid issue. After you escape the find widget, focus moves to the editor. Then you press the tab key and it probably goes to the browser. Where are you expecting tab focus to move in this case?

I suggest closing this.

[meganrogge]

I cannot reproduce this issue.

Can you reproduce this in VS Code? If so, pls create an issue for that. Otherwise, I suggest closing this.