A11y Agency plugin is available to help with accessibility bug remediation.
The required tag has already been added: agency:agent=a11y:a11y-agent@company. Assign the bug to Agency to use it.
Please try it and share feedback on whether the remediation guidance was useful at CAIA11yAgency@microsoft.com.
GitHub Tags:
#A11yTCS; #DesktopWeb; #FTP; #Win11; #A11ySev3; #A11yMAS; #WCAG4.1.2; #Status Messages; #ES Chat; #agency:agent=a11y:a11y-agent@company; #A11yMAS; #ChromiumEdge; #AILimited; #MCIO-GDCO-LaborReferenceSystem; #E2E_MCIO-GDCO-LaborReferenceSystem_Web_June26; #Narrator; #NVDA; #ScreenReader;
Issue Subcategory:
Success/error message not announced
User Experience:
Screen reader users are not informed of form submission success, validation errors, or important status changes. They must manually search the page to discover what happened.
Repro Steps:
Start NArrator/NVDA --> Launch URL https://dccentral-test.microsoft.com/workspace?DDUROUTE=true --> Workspace --> Edit Workspace --> Add widget
Actual Result:
After adding a widget, Narrator does not announce whether the widget has been successfully added.
A success or error message appears visually after a form submission or action, but the message container lacks ARIA live region attributes. Screen readers do not announce it.
Expected Result:
Status messages should be automatically announced to assistive technology users without requiring focus to move to them.
How to fix:
Use ARIA live regions: role="status" with aria-live="polite" for non-urgent messages, or role="alert" (implicitly aria-live="assertive") for urgent errors. Ensure the live region exists in the DOM before content is injected.
Environment details:
Application Name: MCIO-GDCO-LaborReferenceSystem
URL: https://dccentral-test.microsoft.com/workspace?DDUROUTE=true
Chromium Edge version: Microsoft Edge version 149.0.0.0 (Official Build) (64-bit)
OS: Windows 11 Enterprise Insider Preview 26200.8655
MAS reference:
MAS 4.1.3 – Status Messages
Check out MAS 4.1.3: Status Messages for resources and suggestions.
Note:
"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification."
"Contact CAI Accessibility Support Channel for Accessibility queries on design, development, test, usability or any processes"
Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
"Try ES Chat to learn more about the MAS rule and how to fix the issue. If you need more help, use our Teams channel or office hours."
Attachment:
2066_A11y_MCIO-GDCO-LaborReferenceSystem_Workspace_NVDA.zip
2066_A11y_MCIO-GDCO-LaborReferenceSystem_Workspace_ScreenReader.zip
A11y Agency plugin is available to help with accessibility bug remediation.
The required tag has already been added: agency:agent=a11y:a11y-agent@company. Assign the bug to Agency to use it.
Please try it and share feedback on whether the remediation guidance was useful at CAIA11yAgency@microsoft.com.
GitHub Tags:
#A11yTCS; #DesktopWeb; #FTP; #Win11; #A11ySev3; #A11yMAS; #WCAG4.1.2; #Status Messages; #ES Chat; #agency:agent=a11y:a11y-agent@company; #A11yMAS; #ChromiumEdge; #AILimited; #MCIO-GDCO-LaborReferenceSystem; #E2E_MCIO-GDCO-LaborReferenceSystem_Web_June26; #Narrator; #NVDA; #ScreenReader;
Issue Subcategory:
Success/error message not announced
User Experience:
Screen reader users are not informed of form submission success, validation errors, or important status changes. They must manually search the page to discover what happened.
Repro Steps:
Start NArrator/NVDA --> Launch URL https://dccentral-test.microsoft.com/workspace?DDUROUTE=true --> Workspace --> Edit Workspace --> Add widget
Actual Result:
After adding a widget, Narrator does not announce whether the widget has been successfully added.
A success or error message appears visually after a form submission or action, but the message container lacks ARIA live region attributes. Screen readers do not announce it.
Expected Result:
Status messages should be automatically announced to assistive technology users without requiring focus to move to them.
How to fix:
Use ARIA live regions: role="status" with aria-live="polite" for non-urgent messages, or role="alert" (implicitly aria-live="assertive") for urgent errors. Ensure the live region exists in the DOM before content is injected.
Environment details:
Application Name: MCIO-GDCO-LaborReferenceSystem
URL: https://dccentral-test.microsoft.com/workspace?DDUROUTE=true
Chromium Edge version: Microsoft Edge version 149.0.0.0 (Official Build) (64-bit)
OS: Windows 11 Enterprise Insider Preview 26200.8655
MAS reference:
MAS 4.1.3 – Status Messages
Check out MAS 4.1.3: Status Messages for resources and suggestions.
Note:
"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification."
"Contact CAI Accessibility Support Channel for Accessibility queries on design, development, test, usability or any processes"
Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
"Try ES Chat to learn more about the MAS rule and how to fix the issue. If you need more help, use our Teams channel or office hours."
Attachment:
2066_A11y_MCIO-GDCO-LaborReferenceSystem_Workspace_NVDA.zip
2066_A11y_MCIO-GDCO-LaborReferenceSystem_Workspace_ScreenReader.zip