Keyboard navigation is blocked between “Resources” expandable control and “Views and more actions” using VO navigation (Ctrl+Option keys):A11y_VS code_VoiceOver

[kapilvaishna]

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification.

Leveraging Agency Copilot can help accelerate this accessibility bug fix; review and validate all AI generated changes before merge.

Try ES Chat to learn more about the MAS rule and how to fix the issue. If you need more help, use our Teams channel or office hours.

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

GitHub Tags

#A11yTCS; #Visual Studio Code Client; #agency:plugin=a11y@company; #ES chat;#E2E_VisualStudioCodeClient_MAC_Dec2025;#DesktopApp; #FTP; #Mac; #Device; #A11ySev2;#A11yMAS;#WCAG2.1.1; #VoiceOver; #SCIM:5271834;

Issue Subcategory

Element not reachable via keyboard

User Experience

Keyboard-only users (including screen reader users and those with motor disabilities) cannot access or interact with the control at all. This creates a complete barrier to that functionality.

Repro Steps

Open VS code in MAC > Turn on Voice Over > Resources expandable control > Views and more actions control > Observe the issue: Keyboard navigation is blocked between “Resources” expandable control and “Views and more actions” using VO navigation (Ctrl+Option keys)

Actual Result

When keyboard focus is placed on the Resources expandable control, navigating backward to the “Views and more actions” control using Control + Option + Left Arrow requires an excessive number of keystrokes.
After reaching the “Views and more actions” control, the user is unable to navigate forward using Control + Option + Right Arrow, causing focus to get stuck at this control.

Expected Result

Users should be able to navigate efficiently and consistently between interactive controls using Control + Option + Arrow keys.
Focus should move logically in both forward and backward directions without requiring excessive keystrokes or getting stuck on any control.

How to Fix

Use natively focusable elements (button, a href, input). For custom controls, add tabindex="0" and implement keyboard event handlers for activation.

Environment Details:

Application: VS Code
OS: MAC M2
macOS: 15.3

Attachment

320381.mp4

[meganrogge]

@kapilvaishna what extension is installed to reproduce this?

Also, I see you navigating using the keyboard to the buttons, not sure I'm following the issue.

[kapilvaishna]

@meganrogge This issue is not specific to extension, It's happening in explorer as well please find attachment below

This issue occurs when using VoiceOver navigation (VO keys – Control + Option + Arrow keys), not normal Tab navigation.

While I am able to reach the buttons using the standard keyboard (Tab), the issue appears specifically when navigating using VoiceOver commands.

When using Control + Option + Arrow keys:

• When focus is on “Views and more actions”, pressing Control + Option + Right Arrow does not move focus forward as expected.
• When focus is on the “Resources” expandable control, navigating backward using Control + Option + Left Arrow requires multiple keystrokes to reach “Views and more actions”.

So, the problem is related to screen reader interaction, not basic keyboard navigation.

Attachment

Screen.Recording.2026-06-09.at.1.42.37.PM.mp4

[meganrogge]

While I am able to reach the buttons using the standard keyboard (Tab), the issue appears specifically when navigating using VoiceOver commands.

Given this, I suggest closing this as it is accessible via keyboard navigation. This seems specific to VoiceOver and not something VS Code can address.

[kapilvaishna]

@meganrogge I did some research on this behavior in Copilot and found that it appears to be an issue with VS Code. Could you please check again, Thanks!

This behavior indicates an issue with how the UI is exposed to the macOS accessibility framework:

• VoiceOver navigation does not rely on Tab order.

• It follows the accessibility hierarchy (AX tree) provided by the application.

• If controls are:

• improperly grouped

• nested inside multiple containers

• or not structured logically

VoiceOver requires users to enter/exit groups and traverse multiple intermediate elements, resulting in excessive or inconsistent navigation.

VoiceOver documentation confirms that users must interact with groups and nested containers to navigate their contents, which can increase navigation steps when hierarchy is not optimized.