Closed 12-shweta closed 2 years ago
“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11yMAS;#A11yTCS;#VisualStudioCode-Win32-Apr2021;#Visual Studio Code Client;#A11ySev3;#WCAG2.1.1;#DesktopApp;#Win10;#Keyboard;
Visual Studio Code Azure Function Operating System: Windows 10 Pro 21H1
The keyboard focus shifts to the "968,137" non-interactive control while navigating using TAB key.
The keyboard focus should not shifts to the "968,137" non-interactive control while navigating using TAB key.
The keyboard users will get confused while navigating using TAB key and will think this is interactive control.
Disagree. This is a way how users discover how many install are there. The focus should land on it. Closing as designed.
“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11yMAS;#A11yTCS;#VisualStudioCode-Win32-Apr2021;#Visual Studio Code Client;#A11ySev3;#WCAG2.1.1;#DesktopApp;#Win10;#Keyboard;
Environment Details:
Visual Studio Code Azure Function Operating System: Windows 10 Pro 21H1
Steps to Reproduce:
Actual:
The keyboard focus shifts to the "968,137" non-interactive control while navigating using TAB key.
Expected:
The keyboard focus should not shifts to the "968,137" non-interactive control while navigating using TAB key.
User Impact:
The keyboard users will get confused while navigating using TAB key and will think this is interactive control.