When the keyboard focus is on any list item in the "Select an Azure ML job Schema" list and when user press Shift+tab key, JAWS/NVDA does not announce anything: A11y_VS Code_Appling filter on subscription_Screen reader

[kapilvaishna]

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; #Visual Studio Code Client; #BM-VisualStudioCodeClient-Win32-Jan2024; #WCAG1.3.1; #FTP; #Screen Reader; #NVDA; #JAWS; #Element:Combobox; #STP;

Environment Details:

Application: VS Code
Visual studio code version: 1.96.3
OS: Windows 11 Enterprise 24H2
Build: 26100.2605
Screen reader
JAWS version: 2024.2312.53
NVDA Version: 2024.4.1

Repro Steps

1. Turn on Jaws/NVDA screen reader
2. Launch the VS Code.
3. Install the Azure Machine Learning extension and sign in.
4. Tab until the left toolbar (list of icons). This toolbar has a file icon, search icon, settings, etc.
5. Use the up/down arrow keys to navigate to the "Azure" icon and press enter
6. The Azure panel will now be active next to the toolbar.
7. Tab until the Machine Learning dropdown.
8. TAB till "Create job" button and press ENTER key.
9. Focus will be on "Select an Azure ML job Schema" combo box and.
10. Now press "TAB" than SHIFT + TAB.
11. Observer that JAWS/NVDA does not announce any thing when keyboard focus is on any list item of "Select an Azure ML job Schema" list and pressing shift +TAB key

Actual Experience.

When the keyboard focus is on any list item in the "Select an Azure ML job Schema" list and when user press Shift+tab key, JAWS/NVDA does not announce anything

Similar issue observed with following scenarios.

Scenario1: Creating a job Select an Azure ML job Schema

1. TAB till create job button and press ENTER key
2. TAB till Combo box and press TAB and then SHIF + TAB

Scenario2: Setting Default Workspace

1. Open the Command Palette via the keyboard command Ctrl + Shift + P
2. Type "Set default workspace" and select the option from the dropdown list called "Azure ML: Set Default Workspace") and press enter
3. A list should appear that says "Select a subscription"
4. Use the up/down arrows to navigate the list until "AML V1 Personal 2" is selected, and press enter
5. A list should appear that says "Select a workspace"
6. TAB till Select a workspace combo box and press TAB and then SHIFT + TAB.

Expected Experience

When the keyboard focus is on any list item in the "Select an Azure ML job Schema" list and the Shift + TAB key is pressed, keyboard focus moved to "Select an Azure ML job Schema" combo box but JAWS/NVDA should announce about combo box.

User Impact:

Screen reader user will get confused if they press TAB key and screen reader is not announcing anything and keyboard focus is not visible and then pressing SHIFT + TAB also Screen reader is not announcing anything.

Attachment

NVDA:

JAWS:

Code snippet

Similar issue of scenario 1 and 2

[meganrogge]

Similar to the other issue #245219, I think this is because it lacks a placeholder. Pls create an issue for that extension. cc @TylerLeonhardt in case he disagrees here.

[TylerLeonhardt]

This is because we have the list focused by default (well, an item in the list) via aria-activedescendant. This is because an item is focused for quick usage of hitting ENTER when it shows. We did add a feature that lets you SHIFT+TAB to clear the selection in the list... the intent is that this would read the placeholder and title. Let me know if this does not do that.

Nevertheless, this quick pick is not following our guidelines:
https://code.visualstudio.com/api/ux-guidelines/quick-picks

because there is no placeholder. Please have the extension consult these.

[kapilvaishna]

@TylerLeonhardt You mentioned that pressing SHIFT + TAB would read the placeholder and title. However, in this bug title is given as "input", but the screen reader remains silent and does not announce anything, which creates an issue for screen reader users.

Could you please reopen the bug or provide your input.