Screen reader does not announce toggle state for front‑end button.: A11y_Aspire website_Aspire page_Screen reader

[PoojaNamde]

GitHub Tags:

#A11yTCS; #A11yMAS; #A11ySev2; #A11yWCAG; #DesktopWeb; #ChromiumEdge; #Win11; #Developer Community Partners; #SH_AspireWebsite_Web_Jan26; #WCAG4.1.2; #Name, Role, Value; #ES Chat;

"Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification."

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.

Environment Details:

Application Name: Aspire website
URL: https://aspire.dev/
Chromium Edge: Version 145.0.3775.0 (Official build) dev (64-bit)
Edition: Windows 11 Enterprise Insider Preview
Version: 24H2
OS build: 26540.1001

Repro steps:

1. Start Narrator/ NVDA screen reader.
2. Hit the URL: https://aspire.dev/.
3. TAB to "Front end" button and other buttons present under "Build your AppHost" section.
4. Observe the issue that Screen reader does not announce toggle state for all the buttons present under "Build your AppHost".

Actual Result:

Regarding the front-end button and other buttons located in the Build your AppHost section, the screen reader does not indicate whether a button is toggled on or off.

Expected Result:

Narrator screen reader should announce the button role and its current toggle state, such as: “Button, pressed” or “Button, not pressed”

User Impact:

Screen‑reader users cannot determine the current state of the button, leading to confusion and reduced usability. This makes it difficult to interact with toggle‑based functionality independently.

Attachment:

259_Narrator.mp4

259_NVDA.mp4