Receiving focus does not cause unexpected navigation

When tabbing to an element automatically triggers navigation, form submission, or a dialog, keyboard users lose control over when actions happen. WCAG 2.2 SC 3.2.1 (On Focus) is a Level A requirement: receiving focus must never automatically cause a context change. Users with motor disabilities who accidentally land on a focusable element before their intended target will trigger unintended actions — potentially submitting forms or navigating away from work in progress.

Remove onFocus handlers that trigger navigation or submission. Separate the display of options from their activation — selection should require an explicit action like clicking a button.

// Bad — navigates on focus, no user confirmation
<select onFocus={(e) => router.push(e.target.value)}>
  <option value="/">Home</option>
  <option value="/settings">Settings</option>
</select>

// Good — selection updates state; navigation requires an explicit action
<select value={dest} onChange={(e) => setDest(e.target.value)}>
  <option value="/">Home</option>
  <option value="/settings">Settings</option>
</select>
<button onClick={() => router.push(dest)}>Go</button>

Search the codebase for onFocus event handlers. Any that call router.push, window.location, or form.submit are WCAG 2.2 SC 3.2.1 violations.