Skip to content

Tool tips are not appearing for Explore, Search, Source Control, Run and Debug, Extensions, Account and Settings Tab controls as soon as Keyboard focus Lands on controls: A11y_VisualStudioCodeClient_ Menu bar Options_Keyboard. #250997

Closed
@keerthiduvvuri

Description

@keerthiduvvuri

Please do not close this bug. This bug should only be closed by Trusted Tester after verification.
"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

GitHub Tags:

#A11yMAS; #A11yTCS; #Win32; #DesktopApp; #A11ySev2; #BM_VisualStudioCodeClient_Win32_Jun2025; #Visual Studio Code Client; #WCAG2.1.1; #FTP; #Keyboard; #AILimited; #Win11; #Benchmark; #VSCode2025;

Environment Details:

App Name: Visual Studio Code Client
#URL: Visual Studio Code Insider
Microsoft Windows 11 Enterprise
OS Build: 26100.4202

Repro Steps:

  1. Open Visual Studio Code Insider editor.
  2. Start navigating with Tab key from all the Menu items.
  3. Once the Keyboard focus lands on Explore tab item Observe that Tool tips are not appearing for Explore, Search, Source Control, Run and Debug, Extensions, Account and Settings Tab controls as soon as Keyboard focus Lands on controls.

Actual Result:

Tool tips are not appearing for Explore, Search, Source Control, Run and Debug, Extensions, Account and Settings Tab controls as soon as Keyboard focus Lands on controls

Expected Results:

Tool tips should be appearing for Explore, Search, Source Control, Run and Debug, Extensions, Account and Settings Tab controls as soon as Keyboard focus Lands on controls.

User Impact:

Keyboard users wont be able to get the tooltip information if tooltips does not appear as soon as keyboard focus lands on it.

Attachment:

250997_A11y_VisualStudioCodeClient_.Menu.bar.Options_Keyboard.webm

Metadata

Metadata

Labels

accessibility-slaAccessibility issue which have to be fixed or lowered severity based on processbugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberregressionSomething that used to work is now broken

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions