You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When keyboard focus moves to the "Select Subscription" combo box, JAWS/NVDA announces the name of the "select subscription" list and the currently focused list item: A11y_VS Code_Appling filter on subscription_Screen reader
#245222
Open
kapilvaishna opened this issue
Apr 1, 2025
· 4 comments
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."
Observer that JAWS/NVDA announces the name of the "select subscription" list and the currently focused list item.
Actual Experience
When the keyboard focus moves to the "Select Subscription" combo box after accessing the expanded list with arrow key, JAWS/NVDA announces the name of the "select subscription" list and the currently focused list item.
Expected Experience
When the keyboard focus moves to the "Select Subscription" combo box, JAWS/NVDA should announce about the "Select Subscription" combo box only.
User Impact:
Screen reader user will miss lead as focus lands on "Select Subscription" combo box bug screen reader announcing about the name of the "select subscription" list and the currently focused list item.
Attachment
NVDA:
JAWS:
Code snippet of "select subscription" combo box
The text was updated successfully, but these errors were encountered:
meganrogge
added
bug
Issue identified by VS Code Team member as probable bug
accessibility-sla
Accessibility issue which have to be fixed or lowered severity based on process
labels
Apr 1, 2025
This is behaving as expected and we can't change it. Users, including screen reader users, expect to be able to hit ENTER right as the quick pick opens and so the first item needs to be announced because it is focused by default.
TylerLeonhardt
removed
bug
Issue identified by VS Code Team member as probable bug
accessibility-sla
Accessibility issue which have to be fixed or lowered severity based on process
labels
Apr 2, 2025
@TylerLeonhardt having list name as "type to narrator down result" creating a different issue #245220 issue because when focus move to list we cannot type please check screen shot below and it's misleading the screen reader users. so current name for list should be like "subscription list" for #245220 bug.
Regarding this bug when we navigate to "Select subscriptions" combo box with Shift + TAB" key screen reader should announce the combo box name and role so screen reader user will know that focus is shifted to combo box.
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; #AILimited; #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
Actual Experience
When the keyboard focus moves to the "Select Subscription" combo box after accessing the expanded list with arrow key, JAWS/NVDA announces the name of the "select subscription" list and the currently focused list item.
Expected Experience
When the keyboard focus moves to the "Select Subscription" combo box, JAWS/NVDA should announce about the "Select Subscription" combo box only.
User Impact:
Screen reader user will miss lead as focus lands on "Select Subscription" combo box bug screen reader announcing about the name of the "select subscription" list and the currently focused list item.
Attachment
NVDA:
JAWS:
Code snippet of "select subscription" combo box
The text was updated successfully, but these errors were encountered: