[Screen Reader - PWA Builder - PWA Builder Generate] : Screen Reader Not reading the heading level of "Key Features" heading in PWA builder dialogue box

[Priyanka-Chauhan123]

User Experience:
If headings are not clear and descriptive, it would be difficult for screen reader dependent users to find the information they seek , and cannot understand the relationships between different parts of the content. Also if labels are not Descriptive users can not identify specific components within the content.

Test Environment:
OS: Windows 10 build 19608.1006
Browser: Edge - Anaheim - Version 85.0.545.0 (Official build) dev (64-bit)
URL: https://preview.pwabuilder.com/generate

Repro Steps:

1. Open URL: https://preview.pwabuilder.com/generate in Edge Anaheim dev browser.
2. Navigate to Download PWA Builder button and press enter
3. Now with scan mode on move focus to the  key features heading and observe what screen reader reads.
4. Observe the issue.

Actual Result:
The screen reader reads the heading as "Key Features" only

Expected Result:
The screen reader should read the heading as "Heading level 3, Key features".

MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0cf80872-800d-4643-90cf-0c1c3d3e6260}

Note:
Same bug was found on the "Description" heading on the same modal box.

2.4.6 Heading and Labels Headings.zip

[ghost]

Hello Priyanka-Chauhan123, thank you for opening an issue with us!

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

[ghost]

This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.

[lee-leonardo]

no repro, but the buttons in the install component for close and the carousel are missing descriptive labels.

[Ajesh-k]

Issue has been fixed on below Test Environment as:
OS: Version 2004 (OS Build20190.1000)
Browser:Version 86.0.608.2 (Official build) dev (64-bit)
Hence, closing the bug