vscode-azurefunctions icon indicating copy to clipboard operation
vscode-azurefunctions copied to clipboard

A11y_Azure Tools for VS Code_Azure Function_Create New Project_Keyboard: The user is unable to access the tooltip info using keyboard when keyboard focus lands on 'Create new project' button.

Open bbarik06 opened this issue 2 years ago • 7 comments

GitHubTags: #A11yMAS;#A11yTCS;#A11ySev3;#BM_AzureToolsforVSCodeMAC_May2022;#Azure Tools for VS Code;#MAC;#FTP;#DesktopApp;#WCAG1.1.1;#Keyboard;#AINotInScope;#CEACCReviewed;#A11YCAIOH;

Environment Details:

Application Name: Azure Tools for VS Code Application Version: 1.66.2 (Universal) Mac Version: macOS Monterey 12.3.1

Repro Steps:

  1. Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after verification of the fix.
  2. Launch Visual Studio Code.
  3. Click on extension button and search for "Azure Functions".
  4. Click on install and tab to the "Azure" button.
  5. Tab till 'Functions' button and hit enter.
  6. Tab till 'Create new project' button.
  7. Use keyboard to observe the tooltip info.

Actual:

The user is unable to access the tooltip info using keyboard when keyboard focus lands on 'Create new project' button.

The issue can be observed for 'Create function, 'Deploy to function app', 'refresh', 'Collapse All' button.

Expected:

The user should be able to access the tooltip info using keyboard when keyboard focus lands on 'Create new project' button.

User Impact:

Keyboard users will lose out important tooltip information and will not understand what the control is about by only looking at the buttons.

Attachment:

1_A11y_Visual Studio Code for MAC_Azure Function_Create New Project_Keyboard

bbarik06 avatar May 06 '22 07:05 bbarik06

This should be covered by this issue: https://github.com/microsoft/vscode/issues/52016.

This is a special case that only affects users who are using keyboard and are not using a screen reader. This comment sums up this case quite well: https://github.com/microsoft/vscode/issues/52016#issuecomment-641096443

Basically, VS Code team has not received any user requests to add a custom hover feature and it is not supported by modern web browsers, so there is no plan to pursue this at the current time. Thank you.

MicroFish91 avatar May 12 '22 20:05 MicroFish91

@MicroFish91 this duplicate bug https://github.com/microsoft/vscode/issues/52016. is opened in windows - win11 this bug is for MAC

The issue addressed in the above bug is for native controls or known controls like close min max

the issue in this bug is referred to controls that are not unique, so the bug https://github.com/microsoft/vscode/issues/52016. cant be linked to this

fsteffi avatar May 20 '22 06:05 fsteffi

@MicroFish91 this duplicate bug microsoft/vscode#52016. is opened in windows - win11 this bug is for MAC

My interpretation of isidorn's comment would be that his response was OS agnostic. He seems to be entertaining the idea of whether or not this should be pursued and has come to the conclusion that it doesn't really make sense to pursue this. MacOS doesn't seem like a key point in this context.

The issue addressed in the above bug is for native controls or known controls like close min max the issue in this bug is referred to controls that are not unique, so the bug microsoft/vscode#52016. cant be linked to this

I'm not sure I understand, neither the linked issue nor this issue refer to a unique tooltip. The examples used ('Create function, 'Deploy to function app', 'refresh', 'Collapse All') are used to demonstrate that tooltips in general are not shown when hovering over with keyboard. This is extremely similar to the linked issue, so I'm not sure why the determination would not apply here as well.

In either case, this is not something that can be fixed at the extension level. Thank you!

MicroFish91 avatar Jun 10 '22 22:06 MicroFish91

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.

comment from external team for ref to discuss with SME

fsteffi avatar Jun 13 '22 04:06 fsteffi

@MicroFish91 Please join office hour call for further clarification: https://outlook.office365.com/owa/calendar/[email protected]/bookings/s/liYlILD8qUK6LE24eXV-Vg2

bbarik06 avatar Jun 22 '22 07:06 bbarik06

Informational Note - Upstream issue, open for tracking purposes: https://github.com/microsoft/vscode/issues/132344

MicroFish91 avatar Dec 06 '22 01:12 MicroFish91