[Accessibility] [Screen reader -Microsoft Graph Toolkit Playground - Feedback]: Multiple <H1> headings are defined in the 'Feedback' page. [Sev3][WCAG2.4.6] #1525

[SrujanaAnaganti]

Test Environment: OS Build: Windows 11 Version: 21H2 (OS Build 22000.318) Browser: Edge Version 96.0.1054.43 (Official build) (64-bit) URL: https://mgt.dev/next Screen reader: Narrator Tool: Accessibility insights for web

Repro Steps:

Open the above URL and login with valid credentials. 'Microsoft Graph Toolkit Playground' home page will get displayed. Navigate to 'Feedback' tab and activate it. Now, enable headings toggle button in AI tool and check the whether the multiple headings are defined in the page or not. Now, turn on narrator and press 'CapsLock+Space' key to enter scan mode. Now, press headings shortcut keys 'H' to check for the headings in the page.

Actual: Multiple 'H1' headings are defined in the Microsoft Graph Toolkit Playground 'Feedback' page. Both 'Microsoft Graph Toolkit Playground' and 'Feedback' defined under heading level 'H1'.

Expected: Only one 'H1' heading should be defined in the Microsoft Graph Toolkit Playground page. Only 'Microsoft Graph Toolkit Playground' should be defined under 'H1' heading and 'Fee back' should be defined under 'H2'.

User Impact: Assistive technologies use headings to help people quickly orient their location within and navigation through a page. When headings are not structured in logical manner it becomes difficult to user to understand the heading structure in the page so that they will get confused.

WCAG Reference: https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels

[ghost]

Hello SrujanaAnaganti, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[musale]

@Laxmidurga This issue is fixed in production and next playgrounds. We can close it once you test it's satisfactory. I can't track down the fix that fixed this.

[Laxmidurga]

@musale @sebastienlevert As verified, issue does not repro in the below URL. Hence, closing the issue. URL: https://mgt.dev/next/?path=/story/feedback--page