microsoft / microsoft/vscode-documentdb
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
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 22
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 21
Description
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
- Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.
- "Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
Attachment
https://github.com/user-attachments/assets/e5a1d890-ee31-481e-bcb0-59e9df1efd3f
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the query execution flow in the DocumentDB VS Code extension: open a Query Playground, run a query with Ctrl+Enter, and inspect how the result tab is created. Done means focus moves to the newly opened result tab or its first meaningful content, with the behavior verified using keyboard navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- accessibility, desktop-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100