Menu items in Explore section are missing indexing information for screen reader users:A11y_Visual Studio Code Client_Editor_Screen Reader
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.4k
- PR merge metrics
- PR metrics pending
Description
## GitHub Tags:
#A11yTCS;#Visual Studio Code Client;#GradeB_VisualStudioCodeClient_Win32_Feb2026;#DesktopApp;#FTP;#Win32;#A11yUsable;#A11ySev3; #Screen Reader;
## Environmental Details:
App Name: Visual Studio Code Client
URL: Visual Studio Code Insider
Microsoft Windows 11 Enterprise
OS Build: 26200.7392
## Repro Steps:
Turn on NVDA > Open Visual Studio Code editor > Explorer button > New File > Observe the issue: Menu items in Explore section are missing indexing information for screen reader users
## Actual Results:
In the Explore section menu (for example: New file, New folder, etc.), menu items do not provide positional indexing (such as “item 1 of X”). As a result, screen readers announce only the menu item name without conveying its position within the menu.
## Expected Results:
Menu items in the Explore section should expose indexing/position information (for example, “New file, menu item 1 of X”), and screen readers should announce this information so users understand the item’s position within the menu.
##User Impact:
Screen reader users lack awareness of how many menu items are present and where they are within the list. This makes navigation less predictable, increases cognitive load, and reduces usability for users who rely on auditory feedback to understand menu structure and context.
## Note:
"[Check out Accessibility Insights](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-stfe%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458850501301&sdata=mxhokIKNMb22llsjXHLgU3XZibj1Qfx37rpY4PU2sfE%3D&reserved=0)! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
## Attachments:
https://github.com/user-attachments/assets/e1e69b74-cb2e-4172-9e68-2364ed76bd02
Contributor guide
Assessment
This issue has not been assessed yet.