microsoft / microsoft/vscode-documentdb
Keyboard focus indicator is not visible when initial focus lands on "Save" button on New Document screen:A11y_DocumentDB for VS Code Extension_Adding a new document_Focus Visible
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; #A11ySev3; #A11yMAS; #WCAG2.4.7; #Focus Visible;
Issue Subcategory
No visible focus indicator
User Experience
Keyboard users cannot determine which element currently has focus. They are navigating blind, unable to know which control will receive their next action.
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 > Double-click the Documents item > Add Document button > New Document tab > Observe the issue: Keyboard focus indicator is not visible when initial focus lands on "Save" button on New Document screen
Actual Result
When the New Document screen is opened for the first time, keyboard focus is automatically placed on the"Save" button. However, the keyboard focus indicator is not visible, making it difficult for keyboard users to determine the currently focused element. When the user navigates away and returns to the"Save" button using keyboard navigation, the focus indicator becomes visible as expected.
Expected Result
Whenever keyboard focus lands on the"Save" button, including when the screen initially opens, a visible focus indicator should be displayed consistently so that users can easily identify the currently focused element.
How to Fix
Ensure all focusable elements have a visible focus indicator. Do not suppress browser defaults without providing a custom alternative (e.g., outline: 2px solid #005fcc or box-shadow).
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/e4e7c0ed-7c25-4799-b34d-f27db3654517
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
Reproduce the issue by opening the DocumentDB extension's New Document screen and observing the initial focus on the Save button. Locate the New Document screen and its Save button focus styling, then verify that the focus indicator is visible both on initial focus and after keyboard navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100