Keyboard accessibility is fully supported

Keyboard accessibility is the baseline for all assistive technology: screen readers, switch access devices, voice control, and eye-tracking all depend on the keyboard interaction model. WCAG 2.2 SC 2.1.1 (Keyboard) is Level A — every function reachable by mouse must have a keyboard equivalent. Mouse-only interactions like hover menus, drag-and-drop without alternative, or right-click context menus completely lock out users who cannot use a pointing device.

Audit every interactive element for keyboard operability. Hover-only menus must open on focus; drag-and-drop must have a keyboard alternative; custom widgets must handle Enter and Space.

// Hover menu — also opens on keyboard focus
<div
  onMouseEnter={() => setOpen(true)}
  onFocus={() => setOpen(true)}
  onMouseLeave={() => setOpen(false)}
  onBlur={(e) => {
    // Close only when focus leaves the entire menu subtree
    if (!e.currentTarget.contains(e.relatedTarget)) setOpen(false)
  }}
>
  <button aria-expanded={isOpen} aria-haspopup="true">Products</button>
  {isOpen && <ul role="menu">{/* items */}</ul>}
</div>

For drag-and-drop, provide buttons that move items up/down as a keyboard-accessible alternative. Tab through the entire app to confirm every interactive element is reachable.