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; #A11ySev2; #A11yMAS; #WCAG1.3.1; #Info and Relationship; #ES Chat; #agency:agent=a11y:a11y-agent@company; #A11yMAS; #ChromiumEdge; #AILimited; #MCIO-GDCO-LaborReferenceSystem; #E2E_MCIO-GDCO-LaborReferenceSystem_Web_June26; #Element: Headings; #Narrator; #NVDA; #ScreenReader;
Issue Subcategory:
Headings not programmatically defined
User Experience:
When headings are not properly defined, screen reader users cannot navigate by headings, making content discovery slow and increasing the difficulty of understanding the structure of the interface.
Repro Steps:
Launch URL https://dccentral-test.microsoft.com/workspace --> Workspace--> Select any grid items--> Bulk actions --> Add Note--> Run AI4W for headings.
Actual Result:
Text is styled visually to look like a heading (large, bold) but is not defined as heading elements (e.g., <'h1'>–<'h6'>), nor with heading roles with appropriate aria-levels.
Expected Result:
All visual headings should use semantic heading elements at logical levels matching the visual hierarchy.
How to fix:
Use semantic heading elements (<'h1'> through <'h6'>) at logical, non-skipping levels. If a framework prevents native elements, use role="heading" aria-level="N".
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 1.3.1 – Info and Relationships
Check out MAS 1.3.1: Info and Relationships Guide 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:
2073_A11y_MCIO-GDCO-LaborReferenceSystem_WorkSpace_AI4W.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; #A11ySev2; #A11yMAS; #WCAG1.3.1; #Info and Relationship; #ES Chat; #agency:agent=a11y:a11y-agent@company; #A11yMAS; #ChromiumEdge; #AILimited; #MCIO-GDCO-LaborReferenceSystem; #E2E_MCIO-GDCO-LaborReferenceSystem_Web_June26; #Element: Headings; #Narrator; #NVDA; #ScreenReader;
Issue Subcategory:
Headings not programmatically defined
User Experience:
When headings are not properly defined, screen reader users cannot navigate by headings, making content discovery slow and increasing the difficulty of understanding the structure of the interface.
Repro Steps:
Launch URL https://dccentral-test.microsoft.com/workspace --> Workspace--> Select any grid items--> Bulk actions --> Add Note--> Run AI4W for headings.
Actual Result:
Text is styled visually to look like a heading (large, bold) but is not defined as heading elements (e.g., <'h1'>–<'h6'>), nor with heading roles with appropriate aria-levels.
Expected Result:
All visual headings should use semantic heading elements at logical levels matching the visual hierarchy.
How to fix:
Use semantic heading elements (<'h1'> through <'h6'>) at logical, non-skipping levels. If a framework prevents native elements, use role="heading" aria-level="N".
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 1.3.1 – Info and Relationships
Check out MAS 1.3.1: Info and Relationships Guide 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:
2073_A11y_MCIO-GDCO-LaborReferenceSystem_WorkSpace_AI4W.zip