search

microsoft / moaw

Grab-and-go resources to help you learn new skills, with all the tools you need to create, host and share your own workshop
https://aka.ms/moaw
Creative Commons Attribution Share Alike 4.0 International
103 stars 77 forks source link

Learn more heading is not associated with the respective field: A11y_Maow_Home Page_Info and Relationships. #114

Closed AnKushSingh05 closed 3 months ago

AnKushSingh05 commented 5 months ago

GitHub Tags

A11yTCS; #A11ySev3; #ChromiumEdge; #WCAG1.3.1; #Win11; #GH_Maow_Web_Mar24; #DesktopWeb; #Maow; #Info and Relationships; #AILimited: #A11yMAS;

Actual:

Learn more heading is not associated with the respective field. Same issue is observed with follow and community heading.

Expected:

Only one H1 heading should be defined on the page.

Environment Details:

Application Name: Maow

URL: https://moaw.dev/

OS: Windows 11 Enterprise 23H2 (OS build 22631.3296) Microsoft Edge: Version 122.0.2365.92 (Official build) (64-bit)

Repro Steps:

  1. Hit the URL https://moaw.dev/
  2. Moaw screen will get open.
  3. TAB till learn more.
  4. Verify that the Learn more heading is associated with the respective field or not.

User Impact:

Screen reader users will not be able to get under which section the controls are present and they are navigating.

Attachment:

Bug114

sinedied commented 4 months ago

@AnKushSingh05 this one has been fixed, could you validate it?

AnKushSingh05 commented 3 months ago

@AnKushSingh05 this one has been fixed, could you validate it?

Verified the issue in below environment https://moaw.dev/ Issue is not fixed. Still we can see that NVDA is not announcing learn more section heading Please reactivate the bug Screenshot (1955)

sinedied commented 3 months ago

Thank you, this time I added the missing landmarks and tested it with NVDA, should be good now. @AnKushSingh05 could you validate it?

AnKushSingh05 commented 3 months ago

Verified the issue in below environment https://moaw.dev/ Issue is fixed. Hence closing the bug. Screenshot (1973)

sinedied commented 3 months ago

:tada: This issue has been resolved in version 1.5.0 :tada:

The release is available on npm package (@latest dist-tag)

Your semantic-release bot :package::rocket: