You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Programmatic Access - Make code - New Project]: Aria expanded attribute is incorrectly defined when role="option" for the 'Java script' control.
#6120
Open
BURRAshiva01 opened this issue
Mar 17, 2025
· 0 comments
Visually impaired people who depend on screen reader will get impacted if aria-expanded attribute is not defined for the button. Due to which the end users will not be able to know the current state of the button and cannot access it efficiently.
Note: User credentials should NOT be included in the bug.
ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance:
NA
UIA/DOM details available:
Yes (Refer attachment)
Reference Links:
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to an external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this External Bug Process (sharepoint.com). “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
Please reach out to C&AI Teams channel for any process-related queries.
Test Environment:
OS Version:Windows 11 24H2 (OS Build:26100.3037) Browser: Chrome Version 132.0.6834.196 (Official Build) (64-bit) Test Matrix: Chrome URL:https://makecode.microbit.org/.
The text was updated successfully, but these errors were encountered:
BURRAshiva01
changed the title
[Programmatic Access - Make code - New Project]: Aria expanded attribute is incorrectly defined when role="option" for the 'Java script' button.
[Programmatic Access - Make code - New Project]: Aria expanded attribute is incorrectly defined when role="option" for the 'Java script' control.
Mar 17, 2025
User Experience:
Visually impaired people who depend on screen reader will get impacted if aria-expanded attribute is not defined for the button. Due to which the end users will not be able to know the current state of the button and cannot access it efficiently.
Note: User credentials should NOT be included in the bug.
Repro Steps:
Actual Result:
Issue: Aria expanded attribute is incorrectly defined when role="option" for the 'Java script' control.
Expected Result:
aria-attribute and role should be relevant for 'Java script' control.
Title:
WCAG 4.1.2: Ensure an element's role supports its ARIA attributes (#editordropdown)
Issue:
Ensure an element's role supports its ARIA attributes (aria-allowed-attr - https://accessibilityinsights.io/info-examples/web/aria-allowed-attr)
Target application:
Microsoft MakeCode for micro:bit - https://makecode.microbit.org/#editor
Element path:
#editordropdown
Snippet:
How to fix:
Fix all of the following:
ARIA attribute is not allowed: aria-expanded="false"
MAS Reference:
MAS 4.1.2 – Name, Role, Value
ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance:
NA
UIA/DOM details available:
Yes (Refer attachment)
Reference Links:
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to an external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this External Bug Process (sharepoint.com). “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
Please reach out to C&AI Teams channel for any process-related queries.
Test Environment:
OS Version: Windows 11 24H2 (OS Build:26100.3037)
Browser: Chrome Version 132.0.6834.196 (Official Build) (64-bit)
Test Matrix: Chrome
URL: https://makecode.microbit.org/.
The text was updated successfully, but these errors were encountered: