A11y_30days_Welcome to 30 Days of Learning_Resize: When resize testing is performed in "Menu hamburger icon" , the Close button is only announcing as "BUTTON" using Narrator Screen Reader.

[Ashutoshsahoo164]

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."

GitHub Tags:

#A11yTCS;#A11yMAS;#A11ySev2;#30days;#P3_30days_Dec22;#A11yWCAG2.1;#WCAG1.4.4;#WCAG1.4.10;#DesktopWeb;#Win11;#ChromiumEdge

Environment Details:

Application Name: 30days
#URL: https://microsoft.github.io/30daysof/
Windows Version: Win11
Chromium Edge Version: 110.0.1556.0 (Official build) dev (64-bit)

Pre-Requisite:

To apply Resize resolution, follow the below steps:

Zoom the browser screen to 200%
Refresh the page.

Repro Steps:

1. Hit the URL: https://microsoft.github.io/30daysof/
2. Zoom the page to 200% , turn on Narrator .
3. Tab till "Close button" present in Hamburger Menu.
4. Observe that Narrator is announcing "Button" when the focus comes to Close button.

Actual:

While Navigating the screen with Narrator screen reader, Narrator is announcing "Button" when focus lands on Close button.

Note – This issue is reproducing with NVDA screen reader.
Also this issue is reproducing with Reflow Resolution.

Expected:

Narrator and NVDA Screen reader should announce "Close Button" only.

User Impact:

Screen reader user will be confused when they will navigate to this close button.

Attachment:

Narrator Attachment:

NVDA Attachment:

[nitya]

@Ashutoshsahoo164 - I seem to be missing the narrator attachment (audio walkthrough)? I see only screenshots. Site has been updated for other a11y fixes. Can you verify if this issue is still present and provide recording?

[Ashutoshsahoo164]

Hi @nitya Please check the screenshot with Narrator buddy speech viewer

[nitya]

@Ashutoshsahoo164 we have decided to unpublish the site and deactivate it from internal listings. Can you verify and close this issue now that website is no longer active?

[Ashutoshsahoo164]

As per the above comments , closing this bug.