Health

How to Use a Mac With One Hand: A One-Handed Workflow That Actually Works

When I had to use my Mac with one hand for six weeks, Sticky Keys and Voice Control weren't enough. Here's the one-handed workflow — trackball, gestures, and setup — that kept me shipping code.

9 min read
On this page
  1. Most "one-handed" advice assumes a permanent condition. Mine was temporary
  2. The macOS tools that help (and where each one falls short)
  3. Pick hardware that doesn't fight a single hand
  4. Map a small gesture vocabulary onto one hand
  5. Make gestures context-aware
  6. The setup that kept me shipping
  7. What a one-handed workflow doesn't solve
  8. Frequently asked questions
Luis Luis

Using a Mac with one hand — six weeks with my left arm in a sling after a distal radius fracture — taught me that macOS’s accessibility presets get you about 40% of the way. The one-handed workflow that actually kept me shipping code combined three things: a thumb-driven trackball, a small set of mouse gestures mapped to the shortcuts I could no longer two-hand, and Sticky Keys as a backstop. Here’s what worked, what failed, and the exact setup.


Most “one-handed” advice assumes a permanent condition. Mine was temporary

Search for “how to use a Mac with one hand” and almost every result is written for permanent motor impairments. That advice is valuable, but it misses the far larger group: people who are temporarily down to one hand. A wrist fracture, a post-surgical sling, a sprained thumb, a newborn you’re holding, a burned dominant hand. You’re not re-learning computing for life — you’re trying to hit a shipping deadline for the next month and a half with half your usual input.

Wrist fractures alone are extraordinarily common. Distal radius fractures are among the most frequently broken bones in adults under 65, and recovery in a cast or sling routinely means four to eight weeks of one-handed computing (American Academy of Orthopaedic Surgeons). Layer in every sprain, surgery, and new parent, and you have a large, transient population that the accessibility canon barely addresses.

The difference matters because temporary users can’t justify re-learning everything. You won’t remap your entire muscle memory for a six-week window. You need a setup you can build in an afternoon, that gets you to maybe 80% of normal speed, and that you can throw away when the cast comes off. That’s the workflow this post describes.

The macOS tools that help (and where each one falls short)

macOS ships a real accessibility toolkit. None of it is bad; each piece solves one problem and creates another. Apple documents all of these under Mac accessibility settings, and I spent my first disabled week living inside them.

ToolWhat it doesOne-handed verdict
Sticky KeysPress modifiers sequentially instead of holding themEssential. Turns Cmd+W into “press Cmd, release, press W.” Slower, but the only way to fire a modifier shortcut with one hand.
Mouse KeysMove the pointer with the keyboard (numpad)A last-resort fallback. Precise but glacial — you will not use it for real work.
Voice ControlSpeak commands: “click File,” “switch to Xcode,” “press return”Remarkably capable, unusable for fast work. ~1–1.5s latency kills flow state.
Full Keyboard AccessTab through every on-screen UI elementThorough. Turns a 0.5s click into a 5s tab-fest. Good insurance, bad default.
Dwell / Hover TextDwell on a target to click it; zoom text under the cursorUseful when pressing a physical button itself hurts. Niche.

The pattern: every tool trades speed for safety. That’s the right call for permanent accessibility needs and the wrong call for a six-week deadline. Sticky Keys earned a permanent spot in my setup. The rest I kept as fallbacks I almost never touched.

The honest bottleneck is the modifier key. Cmd, Ctrl, Option, Shift live on the left side of the keyboard, and they’re designed to be held while a second key fires. With one hand — and especially if that hand is your non-dominant one — the hold-and-reach motion is exactly what you can’t do. Sticky Keys removes the holding, but it roughly doubles the number of keypresses. The real win is to stop reaching for the keyboard at all.

Pick hardware that doesn’t fight a single hand

This is the part that mattered more than any software setting. My everyday Magic Mouse was suddenly the worst possible tool: it’s a single button whose “right click” and gestures require precision finger work, and nothing on it is remappable in a way that helps.

DeviceOne-handed verdict
Magic Mouse / Magic TrackpadPoor. Single-button precision is slow one-handed; no physical buttons to repurpose.
Standard two-button mouse with side buttonsDecent. Remap the two side buttons to your two most common actions and you’ve bought back real speed.
Thumb trackball (Logitech MX Ergo, Kensington SlimBlade)Best, for most people. The ball stays put; you drive it with the fingers of one hand while modifier duty falls to Sticky Keys. No need to move your arm across the desk.
Vertical mouse (Logitech Lift, MX Vertical)Good, especially if you also care about prevention. Remappable buttons, one-handed friendly.

I landed on a thumb trackball and never went back, even after the sling came off. When only one hand is available, the killer feature is that the pointer doesn’t require arm movement — your hand parks in one spot and the fingers do the work. That leaves your single hand free to stay on the trackball instead of shuttling between mouse and keyboard.

Map a small gesture vocabulary onto one hand

This is the core of it. With one hand permanently on the pointing device, drawn mouse gestures solve the exact problem the keyboard can’t: firing a modifier-based action without a second hand to hold anything.

I timed the common actions three ways, once I was healed and could compare honestly:

ActionTwo-handed shortcutOne-handed via Sticky KeysOne-handed via gesture
Switch to last appCmd+Tab (~1.0s)Cmd, release, Tab (~1.8s)Draw left (~0.7s)
Close tab / windowCmd+W (~0.9s)Cmd, release, W (~1.6s)Draw down-right (~0.6s)
Spotlight / searchCmd+Space (~1.0s)Cmd, release, Space (~1.5s)Draw up (~0.7s)
Switch desktopCtrl+←/→ (~1.1s)Ctrl, release, arrow (~1.7s)Sweep left / right (~0.8s)

Read the table carefully: in three of four cases, a one-handed gesture is faster than my original two-handed shortcut, and in all four it beats the Sticky Keys sequence. That’s not marketing — it’s that a single drawn shape fires in one motion instead of a hold-and-reach. When you only have one hand, gestures stop being a productivity trick and start being the only input modality that doesn’t punish you.

Keep the vocabulary small. I mapped twelve gestures, total, across every app — and a smaller gesture vocabulary builds muscle memory faster and cuts needless repetition. Twelve is enough to cover navigation, window management, and the handful of destructive actions (close, quit, force-quit) you want one motion away.

Make gestures context-aware

The same gesture meaning the same thing in every app sounds efficient, but it’s wrong. In Xcode, “draw up” should run the build; in Safari, it should open a new tab; in Figma, zoom to fit. With one hand, you’re leaning on the mouse harder than ever, so each app should reward that hand with the action you reach for most in that app. Per-app gesture mappings are what turn a clever trick into something you can actually live in for six weeks.

The setup that kept me shipping

After a week of flailing, here’s the configuration that held for the rest of the recovery:

  1. Sticky Keys on, with sound off. The confirmation beep drove me insane in a day. Keep the feature, kill the sound.
  2. Thumb trackball as the primary pointer, parked exactly where my right hand naturally rests. No arm travel, ever.
  3. Twelve mouse gestures covering app switching, tab/window management, desktop navigation, and the destructive actions. The trade-off between gestures and keyboard shortcuts leans hard toward gestures when you only have one hand.
  4. Per-app overrides for the three apps I live in (editor, browser, design tool), so each gesture fires the action I actually want in that context.
  5. Voice Control reserved for the moments both hands were truly occupied (eating, holding something) — not for normal work.
  6. A one-handed hardware fallback for sustained text entry: dictation for drafts, a compact one-handed keyboard for edits. Gestures don’t write prose.

That stack got me to roughly 80% of my normal throughput by the end of week two. The remaining 20% was almost entirely text entry, which no pointer trick solves.

What a one-handed workflow doesn’t solve

I want to be precise about the limits, because overselling “accessibility” to someone on a deadline is cruel:

Text entry still needs a keyboard or dictation. You can gesture your way through navigation, but you cannot gesture your way through writing code or prose. Plan for dictation (rough drafts) and a real input method (edits). If writing is most of your job, a one-handed keyboard like the Matias Half Keyboard is a better investment than any software.

It is not a medical strategy. A distal radius fracture, tendinitis, or carpal tunnel needs rest, professional assessment, and rehab. Software does not replace a cast or a physiotherapist. If your injury came from repetitive strain rather than trauma, the longer-term playbook matters more than the one-handed shortcut — and that’s a different problem than a six-week sling.

There’s an adjustment curve. The first week feels slower than it should, because your decade of two-handed muscle memory keeps reaching for keys you can’t press. By week three the gestures are automatic and the cost disappears. If you give up in week one, you’ll never see the payoff.

If your mousing hand is the one injured, this whole setup flips. Everything above assumes your good hand is on the pointer. If the injury is in your dominant/mousing hand, you’re learning to mouse with your off hand — possible, but slower, and you’ll want a trackball (more forgiving than a mouse for an unfamiliar hand).

Frequently asked questions

Can you really code with one hand on a Mac?

Navigation, app switching, window management, and build/test cycles — yes, fully. Pure text entry — no. The realistic split is: use one-handed gestures and Sticky Keys for everything around the code, and dictation or a one-handed keyboard for the code itself. I shipped a release during my recovery; I did not enjoy writing the commit messages.

Is Voice Control enough on its own?

No. It’s impressive as a demo and painful as a daily driver for anyone doing fast, precise work. The ~1–1.5s latency per command compounds. Keep it for moments when your hand is genuinely occupied, not as your primary input.

What’s the single best mouse for one-handed Mac use?

For most people, a thumb trackball (Logitech MX Ergo or Kensington SlimBlade). The ball doesn’t move, so one parked hand does everything without arm travel — which is exactly what you want when you only have one hand to spare. A vertical mouse is the runner-up and the better pick if you also care about preventing strain.

Do I need to buy an app to use mouse gestures one-handed?

macOS gives you Sticky Keys and trackpad gestures for free, and those alone cover a surprising amount. But system-wide drawn gestures with per-app mappings — the features that actually let you replace two-handed shortcuts one-handed — are mostly paid tools. A head-to-head comparison of the options covers what each one offers; most have trials, so test with your own most-used shortcuts before committing.

How long until a one-handed workflow feels normal?

About a week to stop fighting it, two to three weeks to feel automatic. The gestures themselves are learned in days; what takes time is un-learning the reach for modifier keys you can no longer press.


A one-handed Mac workflow isn’t one setting — it’s a stack. Sticky Keys handles the modifiers you can’t hold, a trackball removes the arm travel your single hand can’t afford, and a dozen mouse gestures replace the two-handed shortcuts that became impossible. None of it is magic, and none of it replaces a keyboard for writing. But together they got me through six weeks of deadlines I’d otherwise have missed.

If your constraint is temporary — a fracture, a surgery, a newborn — build the stack in an afternoon, accept 80% speed for the duration, and tear it down when you heal. If your constraint is permanent, the same gesture foundation scales, and you’ll want to invest more in the per-app layer. Either way, the bottleneck is never the missing hand. It’s reaching for a modifier key that was never designed to be held for eight hours a day.

If you’re down to one hand and need to keep moving, Curflow handles the part macOS can’t — system-wide, per-app drawn gestures with a 14-day free trial. Map your dozen most-used shortcuts and let your single hand do the rest.

Read next:

Curflow

Write less. Gesture more.

Curflow turns your trackpad and mouse into a gesture engine. 14-day free trial, no card required.

Try Curflow Free
Luis

Luis

Building Curflow — native gesture automation for macOS.