Visible label "Documents" is not included in the accessible name of the tree item:A11y_DocumentDB for VS Code Extension_Tree Grid_Label in Name

GitHub Tags

#A11yTCS; #E2E_DocumentDB_Win32_JUNE2026; #DocumentDB for VS Code Extension; #DesktopApp; #FTP; #Win32; #A11ySev2; #A11yMAS; #WCAG2.5.3; #Label in name; 

Issue Subcategory

Accessible name does not contain visible text

User Experience

Speech input users cannot activate a control by saying its visible label because the accessible name is completely different. They must guess the programmatic name or use fallback navigation.

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 > Observe the issue:

Actual Result

The tree item is visually displayed as"Documents", however Accessibility Insights exposes and screen readers announce the accessible name as"Double-click to open the collection view". The accessible name does not contain the visible label text "Documents", resulting in a mismatch between the visual label and the programmatically exposed name.

Expected Result

The accessible name of the tree item should match or at least contain the visible label text"Documents".

How to Fix

Ensure the aria-label or accessible name includes the visible text. If additional context is needed, append it: aria-label="Submit order form" (starts with the visible “Submit”).

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

Start in the DocumentDB for VS Code extension's collection tree implementation and inspect how the Documents tree item gets its accessible name. Reproduce the issue through the database and collection tree, then verify with Accessibility Insights that the exposed name contains “Documents” while retaining any needed context.