featureMar 24, 2026 · 3 min read

No Mouse Required: Full Keyboard Navigation

Tab, arrow, enter, escape. monk.flights works entirely from the keyboard. Not because accessibility is a checkbox — because good interfaces don't make you reach for the mouse.

0

mouse clicks required to search

Robby Choate

Creative technologist. Ex-CEO. Next.js and AI developer. Product manager. UX strategist. A decade in Latin America. Building things that matter.

Tab to the origin field. Type your airport code. Watch it auto-select. Cursor jumps to destination. Type again. Cursor jumps to date. Pick your date. Tab to the search button. Hit enter. You just searched for flights without touching your mouse. You're welcome.

Arrow Keys in Dropdowns

When the airport dropdown appears, press down-arrow to enter it. Arrow up and down to navigate results. Enter to select. Escape to close and return to the input. Tab auto-selects the first result and moves to the next field. Every interaction has a keyboard equivalent, because mouse-dependent dropdowns are a crime against usability.

ARIA: Not Just a Checkbox

The airport input is a proper ARIA combobox with aria-expanded, aria-autocomplete, and aria-activedescendant. The dropdown is a listbox. Each result is an option with aria-selected. Screen readers get the full picture. We did this because it's right, not because a compliance auditor made us.

The Philosophy

If every interaction can be accomplished with a keyboard, it means the information architecture is sound, the focus management is intentional, and the component hierarchy makes sense. Keyboard navigation isn't a feature. It's a quality signal. It's how you know the interface was designed, not just assembled.

← back to blog

See what the algorithm found.

Every flight ranked by agony. The best one is at the top.

Find your route →

Related stories