[Menu] Accessibility audit

[DanielleRameau]

Provide a general summary of the issue here

Test menu component on accessibility.

👤 Your name

DR

🧢 Your Product/Team

SLDS

[KatarzynaWM]

testing environment and tools:

Windows 11
Chrome version 140.0.7339.81
screen reader: NVDA
Color Contrast Analyser from TPGi

---

For variant with Keyboard shortcuts: currently screen reader user is not informed, that part of the read text refers to a keyboard shortcut. Some kind of visually hidden label is needed to pass this information.

@DanielleRameau create issue

issue created: #2665

[KatarzynaWM]

Submenu variant:
Before the first opening of the submenu, the menu item lacks aria-expanded attribute (so the screen reader user is not informed, that there is a submenu there):

The attribute appears only after first opening of the submenu:

@DanielleRameau create issue
issue created: #2666

[KatarzynaWM]

I have doubts on how disabled elements are handled. Right now, there are not announced by screen reader (which is ok), but they are counted within the total number of existing elements. So, the user can guess that there is something there, but can't get the information, what is it (it can be reached by changing reading mode to "browse", but in this mode you don't get information about the number of elements). Maybe disabled elements shouldn't be "counted"?

👩‍💻 Unfortunately, we can not change this. This behavior is not based on our code but this is how the screenreader interperates basic HTML.