Pressing F6 from new document editor moves focus to non-visible static content and focus indicator is not visible::A11y_DocumentDB for VS Code Extension_Adding a new document_Focu Order

Reproduce the issue through the documented VS Code path, opening a new document in the DocumentDB extension. Start by inspecting the new document editor's focusable elements and any tabindex="0" usage. Verify that F6 skips non-visible static content, the focus indicator is visible, and Tab and Shift+Tab reach Save and Go Back in a logical order.

GitHub Tags

#A11yTCS; #E2E_DocumentDB_Win32_JUNE2026; #DocumentDB for VS Code Extension; #DesktopApp; #FTP; #Win32; #A11ySev2; #A11yMAS; #WCAG2.4.3; #Focus Order; 

Issue Subcategory

Static content in tab order

User Experience

Static content, such as text, headings, and static labels, is focusable via the Tab key, making it take extra Tab presses to reach actual interactive controls.

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 > Document Editor > Observe the issue: Pressing F6 from new document editor moves focus to non-visible static content and focus indicator is not visible:

Actual Result

When keyboard focus is in the new document editor, pressing F6 moves focus to non-visible, non-interactive static content. The focus indicator is not visible, making it difficult for users to determine the current focus location. After focus lands on this hidden content, pressing Shift+Tab moves focus to the Save button, while pressing Tab moves focus to the Go Back button, indicating that focus was placed on an unintended intermediate element. This results in an illogical and confusing focus sequence.

Expected Result

When users press F6 from the document editor, focus should move directly to the next visible and meaningful focusable region. Focus should never land on non-visible, non-interactive static content. The focused element should remain visible on screen and provide a clearly distinguishable focus indicator. Keyboard navigation using F6, Tab, and Shift+Tab should follow a logical and predictable order.

How to Fix

Remove tabindex="0" from non-interactive elements; if content needs to be programmatically focused (e.g., for focus management), use tabindex="-1" instead so it is not in the natural tab order

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/c6ffae99-3bff-4a24-9a95-414e1a3b9a04