Skip to content

Keyboard focus not visible Immediately after opening "Edit Selected Document": A11y_DocumentDB for VS Code Extension_focusOrder #385

@AnKushSingh05

Description

@AnKushSingh05

GitHub Tags

#A11yTCS; #A11yMAS; #A11ySev2; #DesktopApp; #FTP; #Win32; #DocumentDB for VS Code Extension; #SH_DocumentDB_Win32_NOV2025; #WCAG2.4.3; #FocusOrder;

Environment Details:

Application Name: DocumentDB for VS Code Extension
Version 0.6.0
OS: Windows 11[Version 23H2(OS Build 22631.3593)]

Repro Steps:

  1. Open VS code
  2. Install the DocumentDB for VS Code Extension and open it
  3. Navigate to the DocumentDB Connections area.
  4. Click the New Connection action.
  5. Select Connection String as the connection method.
  6. Paste the connection string when prompted.
  7. Choose to authenticate with username/password and enter the credentials
  8. Confirm to create the connection.
  9. Locate the desired cluster in the DocumentDB Connections list.
  10. Expand the cluster entry to initiate the connection.
  11. Expand one of the databases under the cluster.
  12. Expand a collection within that database.
  13. Select the Documents item for that collection.
  14. Collection View will open
  15. Observe that Keyboard focus not visible Immediately after opening "Edit Selected Document

Actual Result:

Keyboard focus not visible Immediately after opening "Edit Selected Document

Expected Result:
When the modal opens, focus should immediately move to the first interactive element or text field. This ensures users can begin interacting with the modal without needing to press Tab multiple times.

User Impact:

Users relying on keyboard navigation may not know where the focus is immediately after opening the "Edit Selected Document" modal, as the focus becomes visible only after pressing Tab three times. This creates confusion and disrupts the logical flow of interaction for users with visual or motor disabilities.

Attachment

Focus.mp4

Metadata

Metadata

Assignees

No one assigned

    Labels

    a11yAccessibility Issues

    Type

    No type

    Projects

    Status

    Planned

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions