القائمة وMenubar وزر القائمة

An ARIA menu is an app-style list of commands, like the File or Edit menus in desktop software, not your site's main navigation. 🍔

Page links belong in a nav with normal anchors. Use the menu role only for true command sets, or you will confuse screen reader users.

The pattern uses role="menu" for the container, role="menuitem" for each command, and role="menubar" for a horizontal always-visible bar.

A menu button is a real button that opens a menu. Give it aria-haspopup="true" so users know a popup is coming.

The menu button toggles aria-expanded between true and false as its menu opens and closes, just like any disclosure control.

When the menu opens, move focus into it, onto the first menu item. The button no longer holds focus while the menu is active.

Inside a vertical menu, Up and Down Arrow move between items. In a menubar, Left and Right Arrow move along the top-level bar.

Only one menu item is in the tab order at a time. With roving tabindex, the focused item has tabindex 0 and the rest have -1.

Enter or Space runs the focused command and closes the menu. The menu should dismiss itself after a command is chosen.

Escape closes the menu without acting and sends focus back to the menu button, so the user lands exactly where they started.

A flyout submenu uses aria-haspopup on its parent menuitem, and Right Arrow opens it while Left Arrow closes it and returns.

You add a button that opens a list of commands. What signals to assistive tech that a menu will appear?

Menus are for commands, not page links: open with a haspopup button, move focus in, navigate with arrows and roving tabindex, and let Escape return focus. ✅