Show tooltips on elements that have keyboard focus

[AccessibilityTestingTeam-TCS]

Environment Details:
VSCode Version : 1.24.0
OS Version : Win10

Additional Details:
MAS Violated: MAS2.1.1,MAS1.1.1

GitHubTags: #A11yMAS; #A11yTCS; #Win32; #DesktopApp #A11y_VSCodeEditor #WCAG2.1.1 #WCAG1.1.1

Repro Steps:

1. Launch VS Code.
2. Go to View menu and Select Problems.
3. Tab till collapse button beside Filter textbox in Problems Tab.

Actual:
Tooltip of buttons(Collapse,Minimize Panel Size, Move to right, Close Panel) in the Problems tab are not available when we navigate using keyboard. Tooltips are only available on mouse hover.

Expected:
When keyboard focus goes on control and for that control if tooltip is present then on keyboard focus tooltip should also appear.

User Impact:
Keyboard only users wont get the information which are conveyed through tooltip.

Attachment for Reference:
A11y VSCode Problems NVDA Tooltipnotaccessible.pptx

Does this issue occur when all extensions are disabled?: Yes

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• [Accessibility]A11y_VSCode_ViewExplorer_Keyboard: Tooltip is not visible to keyboard only users but only visible on mouse-hover. (#51995)
• [Accessibility]A11y_VSCode_Feedback_Keyboard:"Close" button is not accessible through keyboard when NVDA is ON. (#51900)
• [Accessibility]A11y_VSCode_ViewSearch_Keyboard: Tooltip is not visible to keyboard only users but only visible on mouse-hover. (#52012)
• [Accessibility]A11y_VSCode_ViewProblems_Keyboard: Focus moves out of the tree view and goes to the left pane to the Explorer button. (#51990)

[sandy081]

Assigning to @bpasero as this might impact all workbench actions

[bpasero]

@AccessibilityTestingTeam-TCS I cannot reproduce, when I tab over the buttons I get the following:

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[AccessibilityTestingTeam-TCS]

Please refer video attached in the "Attachment for Reference" section. @bpasero I think you are using screenreader that's why it is displaying the tooltip. This issue is only regarding keyboard. On keyboard focus, tooltip should be visible.

[bpasero]

We do not control that, it is the native tooltip.

[bpasero]

@isidorn fyi umbrella bug

[isidorn]

@bpasero thanks

[isidorn]

@bpasero if we introduced some setting for this. Is there some way for us to always trigger the hover as the focus moves.

[bpasero]

@isidorn to my knowledge you cannot programmatically trigger the native tooltip in the browser

[nirmalsahoo]

@isidorn Same issue is observed in below vs code version.It is reproduced for all the controls for which the tooltips are visible by mouse but not by Keyboard.
Version: 1.44.2 (user setup)
Commit: ff91584
Date: 2020-04-16T16:36:23.138Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

[MayuriNaik]

@isidorn Same issue is observed in below vs code version. It is reproduced for all the controls for which the tooltips are visible by mouse but not by Keyboard.
Version: 1.41.0-insider
Commit: 9579eda
Date: 2019-12-10T21:42:59.146Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: MAC_Darwin x64 19.5.0

[isidorn]

From the user perspective we already read the aria label of the element once the user navigates on it. Aria label is usually the same as what is hovered or better, so this issue is covered for blind users.
The only users this makes sense for imho are users who can not use the mouse and are not using a screen reader. Thus they navigate using the keyboard to an action and they would like to know more details about that action. So it would be nice to have an explicit command to trigger this native hover for those users. However web browsers do not support this as far as I know and it is not possible to trigger a native hover.

We can maybe look into this once MS Teams starts supporting this.
The only solution I see is to build a custom hover which I would not do for a feature which none of the users requested.

[Tanushagottipati]

GitHubTags: #A11ySev2;

[isidorn]

As per my comment above and because none of our users ever requested this I am closing this as designed. We will not change this.

[isidorn]

Duplicate of #132344