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
[BITV] 9.4.1.2/2.3 - The "Open settings menu" menu - The aria-expanded attribute was correctly applied to the menu button, but the attribute always has the value "true" which is incorrect. (9)
#37095
Also, the use of the "nav" element only for the list of menu items is not correct. The "nav" element should also contain the menu button itself. See https://inclusive-components.design/menus-menu-buttons/ for more information.
Additionally, it is recommended not to use the status (open/close) of the menu as part of the accessible name. This status is communicated through the aria-expanded attribute.
The user's online status ("online", "do not disturb" etc.) should be reflected in the accessible name (e. g. instead of "open settings menu" the name should be something like "settings menu - BB - do not disturb" or "BB, do not disturb - settings").
AndyScherzinger
changed the title
[BITV] 9.4.1.2/2.3 - The "Open settings menu" menu - The aria-expanded attribute was correctly applied to the menu button, but the attribute always has the value "true" which is incorrect. Also, the use of the "nav" element only for the list of menu items is not correct. The "nav" element should also contain the menu button itself. See https://inclusive-components.design/menus-menu-buttons/ for more information. (9)
[BITV] 9.4.1.2/2.3 - The "Open settings menu" menu - The aria-expanded attribute was correctly applied to the menu button, but the attribute always has the value "true" which is incorrect. (9)
Sep 7, 2023
The "Open settings menu" refers to a FlyOut menu, and you can find guidance on how to implement it at https://www.w3.org/WAI/tutorials/menus/flyout/. ARIA roles "menu" and "menuitem" are typically used for application menus, which we do not have in this context. You can refer to https://www.w3.org/TR/wai-aria-1.2/#menu, which states, "The menu role is appropriate when a list of menu items is presented in a manner similar to a menu on a desktop application." Additionally, it's important to note that in application menus, navigation is typically done using arrow keys rather than the TAB key.
Also, the use of the "nav" element only for the list of menu items is not correct. The "nav" element should also contain the menu button itself. See https://inclusive-components.design/menus-menu-buttons/ for more information.
Additionally, it is recommended not to use the status (open/close) of the menu as part of the accessible name. This status is communicated through the aria-expanded attribute.
The user's online status ("online", "do not disturb" etc.) should be reflected in the accessible name (e. g. instead of "open settings menu" the name should be something like "settings menu - BB - do not disturb" or "BB, do not disturb - settings").
Details
https://report.bitvtest.de/default-en/d63601ac-cb34-4645-8256-66bec78964a0.html#checkpoint-bfbf07e5c3-v2-n3
The text was updated successfully, but these errors were encountered: