Keyboard navigation is not optional

Every interactive element on this site can be reached and activated with a keyboard. Tab moves forward. Shift-Tab moves back. Enter and Space activate. Escape closes. Arrow keys navigate within groups. This is not a nice-to-have bolted on at the end. It was built into every component from the first commit. Buttons use native button elements. Links use native anchor tags. Dropdowns use proper ARIA roles and manage focus. The hamburger menu traps focus until closed. When you use native HTML semantics and manage focus correctly, keyboard navigation mostly comes for free. The bugs happen when developers reach for divs with onClick handlers instead of real interactive elements.