Morse Code and Accessibility: Tania Finlayson, Gboard and One-Switch Communication
For most people morse code is history, a hobby, or a puzzle. For some it is the only practical way to speak. The same property that made the code robust enough for a century of shipwrecks — everything it says can ride on a single channel that knows only two states, on and off — makes it a natural language for bodies that cannot manage a keyboard: one reliable movement, anywhere on the body, is enough to spell anything in English.
That is not a theoretical elegance. It is the working reality of a modern accessibility community, and the story of how it went mainstream runs through one remarkable woman and one remarkable keyboard. This page covers the real history — Tania Finlayson and the Google keyboard she helped design — and then the practical present: what assistive morse looks like today, and how the major phone platforms compare.
Who is Tania Finlayson?
Tania Finlayson was born with cerebral palsy, and the condition shaped both her speech and her motor control from the beginning. Her childhood, by her own account in interviews and in Google's telling of her story, ran through institutions and therapies designed for children the world had limited tools for — and it was in that setting that someone introduced her to a then-old-fashioned idea: communicating by morse code, using a pointer mounted on a headband, tapped out one dot and dash at a time.
The mechanics matter, because they explain everything that followed. A head wand — a stick worn at the forehead or held in the mouth — requires gross motor control of the head and neck, which many people with cerebral palsy retain fine control of even when their hands and voice are unavailable. Tapping a wand against a surface in two rhythms is a single-repetition, large-movement task: no fine finger work, no multi-key reaching, no timed screen gestures. Morse met her body where it was. With the code and the wand, she could spell — first to therapists, then to family, then to the world.
How did morse change her life — and tech's direction?
As an adult, Tania Finlayson became an advocate and co-developer of assistive technology together with her husband, the engineer Ken Finlayson, building head-wand morse input systems that connected her one reliable gesture to the computers arriving in every home and workplace. Their work sat at the junction of two traditions: the century-old operator's code, and the young field of augmentative and alternative communication (AAC). She spoke — in morse, through her devices — at a time when the technology world was only beginning to understand that accessibility was not charity but engineering done properly.
The chapter that made her story widely known arrived in 2018, when Google brought a Morse code mode to Gboard, its keyboard for Android — a keyboard where the entire layout collapses into a dot zone, a dash zone, and a space, with word suggestions building as you key. Google worked with Tania directly, and told her story in its official developer communications: a woman who had spent decades communicating through head-wand morse now helping design the version that would ship to millions of phones. In a neat closing of the loop, Google also released a morse typing trainer built around her experience, designed so that new users — patients, mostly, and the people teaching them — could learn the code in game-like sessions rather than drill charts.
What is Gboard's Morse mode actually like?
Stripped to its essentials, it is the cleanest possible demonstration of the code's economics: two inputs instead of twenty-six. The on-screen keyboard presents areas for dot and dash; as you enter each letter's pattern, the keyboard offers completions and next-word suggestions, exactly as a conventional keyboard does, so a user who has internalized the letter patterns can type at conversational speed without ever sweeping a finger across a glass rectangle. For a switch user — someone driving the phone through assistive switches rather than touch — it is the difference between a scanning menu that cycles through every letter and a direct-selection system where the letter you want is always two gestures away.
That comparison — *scanning versus direct selection* — is the core engineering trade-off in motor accessibility, and morse sits on the good side of it. Scanning interfaces step through options on a timer, waiting for a single activation; they are universally compatible and agonizingly slow, and every miss costs a full cycle. Morse is direct: you choose each letter deliberately, at your own tempo, with error recovery that costs one backspace. The catch is the learning curve — the user must know the code. Which is why the trainer matters as much as the keyboard: the learning curve is the price of admission, and the tools to pay it are finally free.
Can you type morse on an iPhone?
The honest platform answer: Android got there first and most completely. iOS ships no native morse keyboard — Apple's built-in support runs through Switch Control, the system-level feature that lets external adaptive switches drive selection, cursor and typing; configured with a two-switch setup, a determined user can key morse-style input through third-party apps that accept switch events, and dedicated morse keyboard apps exist on the App Store with varying quality and upkeep. The result is a real but quieter ecosystem: possible for a motivated user with support, but not the first-class, out-of-the-box experience that Gboard's Morse mode represents on Android.
The platform gap matters less than it used to, because the serious deployments of assistive morse rarely live inside a phone at all. Clinical AAC setups pair hardware switches and wands with dedicated communication devices and mounting systems, fitted by occupational therapists; the phone is a valuable secondary channel. What the phone keyboards changed is *access to the learning curve* — anyone can now try the code's two-gesture economy for free on the device in their pocket, which recruits exactly the users, teachers and family members who need to discover that it fits.
Where else does morse appear in assistive tech?
The broader landscape is older and wider than the keyboard story. Switch access in general — one or two reliable movements mapped to selection — is morse's natural home, and the code remains a standard option in professional AAC practice for users whose best available movement is a single, repeatable one: a head turn, an eyebrow raise, a breath-activated sip-and-puff switch. Eye-blink communication, the most dramatic variant, earned its place in history through the POW who spelled T-O-R-T-U-R-E with his eyelids on television — a story told in full in our blink-signaling guide and the military stories collection — and the same technique, at gentler stakes, has let patients in intensive care spell out messages to nurses.
There is also a quieter, two-handed tradition: tactile morse for deafblind users, tapped directly onto a palm or knee, which needs no electronics at all — just two rhythms and an agreed alphabet, exactly as it was for the earliest telegraphers. What unites every one of these channels is the property this site keeps returning to: the code does not care what carries it. Wire, lamp, blink, switch, wand, palm. Wherever a body can produce two distinguishable events, the whole language fits.
Why is morse such a good fit for accessibility?
Reduce it to first principles and the fit is almost uncanny. Typography of language: English needs 26 letters plus digits and space — and morse encodes all of them in strings of just two elements. Input bandwidth: a disabled motor system's scarcest resource is *reliable, distinct gestures*, and morse spends exactly two. Cognitive load: the code is learnable — frequency-ordered letters mean common characters cost the least, a design choice going back to the beginning, as the invention story recounts. Error behavior: errors are per-letter, obvious, and cheap to fix. No other text-entry scheme offers this combination from two events; the alternatives either scan (slow) or demand many distinct movements (impossible).
The limitation is equally honest: learning takes hours of practice, and a user fatigued by therapy may not have them. That is the frontier the modern tools address — game-based trainers, word prediction to reduce keystrokes, communities of switch users sharing setups. The direction of travel is clear, though, and it runs toward the code, not away from it: as interfaces multiply and bodies vary, a two-symbol alphabet keeps looking *more* efficient, not less. The Victorians optimized it for copper wire; the 21st century is optimizing it for people.
How do you start learning assistive morse?
If this page describes you or someone you support, the on-ramp is genuinely short. Learn the letters with the structured guide or the practice games — both work with taps on a screen, which is the same motor plan a switch user trains. Reference the full chart until the common letters are automatic; frequency order means the first handful of letters already buys you most of English. Then try real sentences on the translator, which will play back anything you key and build the feedback loop. On Android, open Gboard's settings, add the Morse keyboard, and try a day of it.
And if you are an engineer or designer, take the real lesson from Tania Finlayson's story: the best accessibility features come from building *with* the experts — the people whose communication depends on the design. A keyboard mode that seems like a curiosity to an able-bodied reviewer is, for a user with one reliable gesture, the difference between a sentence taking eight seconds and eight minutes. Nine signals carry an SOS across an ocean; two rhythms carry a whole person back into the conversation.