Chrome has over 50 keyboard shortcuts. Ctrl+T opens a new tab. Ctrl+Shift+T reopens a closed one. Ctrl+L focuses the address bar. Ctrl+Shift+N opens incognito. Ctrl+D bookmarks. Ctrl+J opens downloads. Ctrl+H opens history. And those are just the ones most people know.
Nobody memorizes all 50. Most people know five or six, forget the rest, and right-click their way through everything else. That's not laziness — it's a rational response to a system that scales poorly. Keyboard shortcuts are flat: every command lives at the same level, competing for the same limited pool of key combinations. The more you add, the harder they all become to remember.
Context-aware menus work differently. Instead of exposing every possible action at once and asking you to remember the right key combo, they show only the actions that make sense for what you're doing right now. The result is fewer options, faster decisions, and no memorization at all.
The Cognitive Load Problem
Every keyboard shortcut occupies a slot in working memory. To use Ctrl+Shift+T, you need to recall three things: the modifier combination, that this particular combination reopens a tab, and that it exists at all. That recall cost is small for any single shortcut, but it compounds. By the time you've internalized 15 shortcuts, adding a 16th means either displacing one you already know or accepting that you'll sometimes confuse similar combos.
This is why most people plateau at a handful of shortcuts and reach for the mouse for everything else. The learning curve isn't steep — it's wide. There's always another shortcut to learn, and each additional one makes the set incrementally harder to keep straight.
Software that relies on keyboard shortcuts implicitly assumes its users will invest the effort to memorize an arbitrary mapping between key combinations and outcomes. Some will. Most won't. And the ones who won't aren't wrong — they're making a reasonable cost-benefit calculation.
How Context Reduces Choices
Wilee's radial menu shows different actions depending on what your cursor is hovering over. There are four contexts: selected text, links, images, and empty page space. Each context gets its own set of actions, typically four to eight.
When you have text selected, the menu offers Copy, Search, Define, and LLM actions like "Send to ChatGPT" or "Send to Claude." When your cursor is over a link, it offers Open in New Tab, Copy URL, and Open in Background. Over an image: Save, Copy, Open in New Tab. On empty space: Back, Forward, Scroll to Top, Close Tab, New Tab.
The key insight is that most actions only make sense in one context. You don't need "Save Image" when you're looking at a paragraph of text. You don't need "Copy URL" when your cursor is on a blank part of the page. By filtering out irrelevant options before you see them, context-awareness eliminates the need to scan past actions you'd never pick.
Keyboard shortcuts can't do this. Ctrl+C is always Ctrl+C, whether you have text selected, a file highlighted, or nothing at all. The shortcut doesn't adapt — it just does the same thing regardless of state (or fails silently when there's nothing to copy). Context-aware menus, by contrast, never show you an action that doesn't apply.
Hick's Law: Fewer Options, Faster Decisions
In 1952, psychologists William Edmund Hick and Ray Hyman published a finding that became one of the foundational principles of interface design: the time it takes to make a decision increases logarithmically with the number of options. Double the choices, and reaction time goes up by a roughly constant amount. This is Hick's Law, and it explains why menus with 30 items feel paralyzing while menus with four feel instant.
A typical Wilee context shows four to eight actions. Compare that to Chrome's keyboard shortcut sheet (50+), a right-click context menu (10-15 items in a linear dropdown), or an extension toolbar (varies wildly). With fewer options, the time from "I want to do something" to "I've decided which action" drops sharply.
But Hick's Law only tells part of the story. The other part is spatial: in a radial menu, each action occupies a direction — up, up-right, right, down-right, and so on. Directions are easier to distinguish than positions in a vertical list. You don't scan from top to bottom looking for the right label. You recall a direction — "Copy is up-left" — and flick. After a few days, this becomes automatic. You stop reading labels entirely.
Same Gesture, Different Action
One of the more powerful consequences of context-awareness: the same physical gesture can do different things depending on where your cursor is. Flick up-left over selected text and it copies the text. Flick up-left over a link and it opens the link in a new tab. Same muscle movement, different result, always appropriate.
This means your motor vocabulary stays small. You learn four to eight directional flicks, and those same flicks work everywhere. The menu handles the translation from "what I physically did" to "what I probably meant." Instead of memorizing separate shortcuts for copy-text, open-link, and save-image, you learn one gesture that means "do the primary thing" and trust the context system to figure out what "the primary thing" is.
In practice, here's what this looks like across contexts:
- Flick up on text: Copy
- Flick up on a link: Open in new tab
- Flick up on an image: Save image
- Flick up on empty space: Scroll to top
Four contexts, one direction, four different actions — all of them the most logical default for that situation. No need to remember which shortcut does what. The context does the remembering for you.
Why This Matters for Daily Browsing
The average Chrome user doesn't think about keyboard shortcuts. They select text, right-click, choose Copy from a dropdown. They want to open a link in a new tab, so they right-click and pick from a list. Each of these interactions involves reading a menu, scanning for the right option, and clicking precisely on a narrow rectangle.
A context-aware radial menu compresses this. Hold, flick, release. The menu appears at your cursor (no travel distance), offers only relevant actions (no scanning), and accepts a directional flick instead of a precision click (no aiming). The result is an interaction that's faster than a keyboard shortcut for experienced users and far more discoverable for new ones.
Discoverability is underrated. Keyboard shortcuts are invisible — you either know them or you don't, and the application gives you no visual hint that they exist. A radial menu shows you what's available every time you invoke it. New users see the options, learn by doing, and build muscle memory without reading a documentation page.
The Limits of Flat Shortcut Systems
Keyboard shortcuts were designed for an era when applications had fewer commands and users were expected to read manuals. They work reasonably well for a small set of frequent actions — cut, copy, paste, undo, save. They break down when an application has dozens or hundreds of commands, because the flat key-combination namespace doesn't scale.
Browser extensions have made this worse, not better. Each extension might add its own shortcuts, often conflicting with existing ones. Ctrl+Shift+S might be "save as" in one context, "screenshot" in an extension, and "toggle sidebar" in another. The user ends up debugging shortcut collisions instead of working.
Context-aware actions avoid this entirely. There's no global key namespace to collide with. Each context is self-contained, the action set is small, and the interface is spatial rather than combinatorial. Adding a new action means putting it in a wedge — not finding an unused three-key combination that doesn't conflict with anything else.
Trying It
If you've been relying on a mix of keyboard shortcuts, right-click menus, and extension toolbars, try using a context-aware radial menu for a week. The adjustment period is about two days — you'll spend the first day consciously choosing directions, and by the second day you'll start flicking without reading labels. By the end of the week, reaching for Ctrl+C will feel like the slow path.
Wilee's radial menu is free. Context-aware actions across text, links, images, and page space work out of the box. No configuration required — though if you want to rearrange which action sits in which direction, you can do that too.