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
Keyboard focus does not move to newly opened Query Playground Result tab after executing a query:A11y_DocumentDB for VS Code Extension_New Query Playground_Focus order #774
#A11yTCS; #E2E_DocumentDB_Win32_JUNE2026; #DocumentDB for VS Code Extension; #DesktopApp; #FTP; #Win32; #A11ySev2; #A11yMAS; #WCAG2.4.7; #FocusOrder;
Issue Subcategory
Focus not managed on view/page change
User Experience
Users navigating within a single-page application may not realize that a new view has loaded if focus remains on the previous control instead of moving to the new content.
Repro Steps
Open VS code > Install the DocumentDB for VS Code Extension and open it > Add new Connections > Expand one of the databases > Expand a collection within that database > Open context menu for restaurants collection tree item > New Query Playground menu item > Run button > Observe the issue: Keyboard focus does not move to newly opened Query Playground Result tab after executing a query
Actual Result
After pressing Ctrl + Enter, the Query Playground Result tab opens successfully, but keyboard focus remains in the Query Playground editor. Focus is not moved to the newly opened result tab, requiring users to manually navigate to the result editor.
Expected Result
When a new Query Playground Result tab is opened as a result of executing a query, keyboard focus should move to the newly opened result tab, or users should be notified.
How to Fix
After rendering the new view, programmatically move focus to the main heading or first meaningful element of the new content; alternatively, use aria-live to announce the page change.
Environment details
Application Name: VS Code
Extension: DocumentDB for VS Code
Extension Version: 0.9.1
Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8390
Note
Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.
GitHub Tags
#A11yTCS; #E2E_DocumentDB_Win32_JUNE2026; #DocumentDB for VS Code Extension; #DesktopApp; #FTP; #Win32; #A11ySev2; #A11yMAS; #WCAG2.4.7; #FocusOrder;
Issue Subcategory
Focus not managed on view/page change
User Experience
Users navigating within a single-page application may not realize that a new view has loaded if focus remains on the previous control instead of moving to the new content.
Repro Steps
Open VS code > Install the DocumentDB for VS Code Extension and open it > Add new Connections > Expand one of the databases > Expand a collection within that database > Open context menu for restaurants collection tree item > New Query Playground menu item > Run button > Observe the issue: Keyboard focus does not move to newly opened Query Playground Result tab after executing a query
Actual Result
After pressing Ctrl + Enter, the Query Playground Result tab opens successfully, but keyboard focus remains in the Query Playground editor. Focus is not moved to the newly opened result tab, requiring users to manually navigate to the result editor.
Expected Result
When a new Query Playground Result tab is opened as a result of executing a query, keyboard focus should move to the newly opened result tab, or users should be notified.
How to Fix
After rendering the new view, programmatically move focus to the main heading or first meaningful element of the new content; alternatively, use aria-live to announce the page change.
Environment details
Application Name: VS Code
Extension: DocumentDB for VS Code
Extension Version: 0.9.1
Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8390
Note
Attachment
774_Keyboard.mp4