A11y_VscodeWebviewUiToolkit_AllComponents_ProgressBar_ScreenReader: NVDA does not announces any information about "default progress bar" when navigating using down arrow key in browse mode.

[Shivamd1]

Actual:

NVDA does not announces any information about "default progress bar" when navigating using down arrow key in browse mode.

Similar issue is observed with Jaws

Similar issue is with "Default Progress ring"

Expected:

NVDA should be announcing information about "default progress bar" when navigating using down arrow key in browse mode. It should be announcing like "loading"

GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#SH_VscodeWebviewUiToolkit_Aug2021;#Webview UI Toolkit for Visual Studio Code;#Win32;#FTP;#DesktopApp;#WCAG1.3.1;#NVDA;#Jaws;#STP;#AINotInScope;

Environment Details:

Application Name: Vscode Webview Ui Toolkit
Windows Version: Win10
Screen Reader: NVDA(2021.1), Jaws(2021.2102.34)

Repro Steps:

1. Launch VS Code
2. Open WebView UI Toolkit: All Component extension
3. Tab to "Progress bar"
4. Start NVDA in browse mode, use down arrow to navigate to "default progress bar" and check the announcement

User Impact:

Screen Reader users will not get the proper information about the "default progress bar"

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”

[hawkticehurst]

@Shivamd1 Please note we removed the progress bar from the toolkit, but have updated the progress ring to announce itself. I've sent an updated build with that fix.

[Shivamd1]

@hawkticehurst I have verified and the progress ring is still not announced. nvda only announces its label

[daviddossett]

@Shivamd1 I have a proposed change to include aria-live="assertive" on the progress ring. This announces "Loading" when the spinner is rendered.

Before I send a build for verification, can you confirm that this is solving for the missing announcement? Tested with VoiceOver and NVDA—this is what the screen readers announce:

[Shivamd1]

@daviddossett yes it is fine. This will wor. Please provide environment so that we can close the bug

[Shivamd1]

@daviddossett The issue still reproduces in the provided build over the mail. Could you please confirm from your side once? i have pinged you the repro attachment offline.

[daviddossett]

Thanks for the heads up—I'll check again