Keyboard shortcuts are documented and non-conflicting

Custom keyboard shortcuts that override browser defaults — Ctrl+W, Ctrl+T, Ctrl+L — can trap users who reach for familiar browser actions and instead trigger in-app behavior. WCAG 2.2 SC 2.1.4 (Character Key Shortcuts) is a Level A requirement: any keyboard shortcut using only printable characters must be remappable, togglable, or active only on focus. Undocumented shortcuts are also inaccessible to AT users who need to know what keyboard controls are available.

Document all custom keyboard shortcuts in an in-app help panel, avoid overriding critical browser shortcuts, and add the ability to disable or remap shortcuts.

// Keyboard shortcut registry — avoids browser-reserved combinations
const SHORTCUTS = [
  { key: '?', action: 'Open keyboard shortcuts help' },
  { key: 'Ctrl+K', action: 'Open command palette' },
  // Avoid: Ctrl+W (close tab), Ctrl+T (new tab), Ctrl+L (address bar)
]

export function KeyboardShortcutsHelp() {
  return (
    <dialog aria-labelledby="shortcuts-title">
      <h2 id="shortcuts-title">Keyboard shortcuts</h2>
      <ul>
        {SHORTCUTS.map(s => (
          <li key={s.key}>
            <kbd>{s.key}</kbd> — {s.action}
          </li>
        ))}
      </ul>
    </dialog>
  )
}

Open the help panel with ? and link to it from the app's navigation so users know shortcuts exist. Per WCAG 2.2 SC 2.1.4, single-character shortcuts must be disableable or remappable.