Skip to content

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 #770

Description

@kapilvaishna

GitHub Tags

#A11yTCS; #E2E_DocumentDB_Win32_JUNE2026; #DocumentDB for VS Code Extension; #DesktopApp; #FTP; #Win32; #A11ySev2; #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

770_FocusVisiable.mp4

Metadata

Metadata

Assignees

No one assigned

    Labels

    a11yAccessibility Issues

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions