Touch Typing on a MacBook Keyboard: What Actually Needs Retraining

You are learning to touch type and the only keyboard you own is attached to your MacBook. Or you have typed properly for twenty years, you have just moved to a Mac, and this is the first keyboard that has made you look down at your hands to hit a 4.

Ask about this anywhere and every answer is about hardware: buy an external keyboard, the newer models are better than the butterfly ones, maybe the trackpad is pushing your hands out of position. What nobody suggests is practising the two things people name when they describe the problem — numbers and capitals.

Those two are the actual answer, and they are also two named stages of the Mochi Type course — Capitals and Numbers — which is where this page ends up.

The letters are not what changed

Here is the thing nobody in that thread said out loud: the letters did not move. The block a ten-finger course teaches sits in the same place on a MacBook as it does on a keyboard you plug in, and your hands already know where every key in it is.

That is because a Mac does not really care what is printed on a key. It knows which key you pressed by where that key sits on the board. Change the keyboard, or change the software layout to something else entirely, and the position is the part that stays put.

macOS does not identify a key by the letter printed on it. It identifies it by a virtual key code — a number bound to the key’s physical position, not to its glyph. Apple’s own header, Events.h, is explicit:

They identify physical keys on a keyboard. Those constants with "ANSI"
in the name are labeled according to the key position on an
ANSI-standard US keyboard.

So A is 0x00, the 1 on the number row is 0x12, ; is 0x29, and they are those numbers on a 2015 MacBook Air, a Magic Keyboard, and an M4 MacBook Pro alike. Change the software layout to Dvorak and the codes do not move; the glyphs do. Change the physical keyboard and the codes do not move either.

That block — the letters, the number row, the punctuation around them — is the entire subject of touch typing. It is smaller than the keyboard it sits on:

Block	Character keys	In a ten-finger course?
Number row	13	Yes
Top letter row (Q…)	13	Yes
Home row (A…)	11	Yes
Bottom letter row (Z…)	10	Yes
Extra key beside left Shift	1, ISO only	Yes
Function row / Touch Bar	0	No
Arrow cluster	0	No
Numeric keypad	0	No
Modifier row	0 — held, not typed	Reach only

Forty-seven character keys on an ANSI keyboard, forty-eight on ISO. (Those per-row counts are the ANSI arrangement; on ISO the backslash key moves out of the top row and down into the home row, and the extra section key joins the bottom, so the rows read 13 / 12 / 12 / 11 — forty-eight, one more than ANSI.) Space is not in the count — it is typed constantly, but it sits on 0x31 on every layout ever made, so a layout table has nothing to say about it. Mochi Type’s layout extractor walks exactly those 48 key codes when it reads a layout out of macOS — that list is the whole of what a ten-finger course has to teach.

Want to settle it on your own keyboard? It takes twenty seconds, and it is worth them, because the ANSI/ISO difference is the only difference in the block — and you can see it. On ANSI, Z sits directly beside a long left Shift and Return is a wide rectangle. On ISO, one extra key sits in that gap — macOS calls it kVK_ISO_Section, 0x0A — the left Shift is short, Return is tall, and the backslash key has moved down beside Return. Everything else in the block is identical.

One caveat before you generalise the sentence “every Apple keyboard”: Macs sold in Japan use a third shape, JIS, and it genuinely is a different block, not a variant of the other two. It carries its own character keys — kVK_JIS_Yen (0x5D) and kVK_JIS_Underscore (0x5E) among them — so the 47/48 count above does not describe it. Everything on this page about ANSI and ISO holds; Mochi Type renders those two shapes and not JIS.

What actually moves between Apple keyboards

Something does change when you come to a Mac, and it is not anything you type. It is the keys you hold down — the bottom-left corner your left little finger reaches for without thinking. On a Mac that corner is arranged differently from a PC, which is why a lifelong typist can suddenly feel clumsy while every letter is still exactly where it was.

The good news is that you do not have to retrain that finger at all. This corner is a setting, and you can rearrange it once and forget about it.

The modifier row, then, and the clusters around it. On a MacBook the bottom-left corner is the fn / 🌐 key with Control to its right, and that corner is where the muscle memory of a PC typist breaks: the key your left little finger has hit for Control for a decade now toggles function keys.

Want to know what your own machine does? I have not audited every Apple keyboard model, and I am not going to publish a table I did not verify. Look at your own bottom-left corner; that is the whole check.

The useful part is that this corner is software. macOS has a Modifier Keys panel — System Settings ▸ Keyboard ▸ Keyboard Shortcuts… ▸ Modifier Keys — whose instruction line reads, verbatim:

For each modifier key listed below, choose the action you want it to
perform from the pop-up menu.

It lists six keys: Caps Lock (⇪), Control (⌃), Option (⌥), Command (⌘), Function (fn) — labelled Globe (🌐︎) on newer keyboards — and Escape (⎋). Any of them can be assigned any of the others’ actions. If Control in the corner is what you want, put it there, once, and stop retraining a finger to work around a default.

One related trap, because it produces a symptom people misread as a broken keyboard: Keyboard settings also carries the option “Use the Caps Lock key to switch to and from last used Latin input source.” With that on, Caps Lock stops capitalising and starts switching input sources. If you type in two scripts and your Caps Lock has gone strange, that is the setting. (Practising a second layout without touching your input sources at all is a separate problem with a separate answer.)

Numbers and capitals are the actual bill

Two things pull your hands out of the position they have learned: reaching up for a digit, and holding Shift down while the other hand fires a letter. Both take a hand off home row in a way letter drills never do, and both are what the poster in the thread named.

Capitals are a chord: Shift held with the opposite hand while a letter fires. Numbers are a reach — the row your fingers leave the home position for, hit blind, and return from. Standard ten-finger assignment for that row, which is also the assignment Mochi’s on-screen hints use:

Keys	Finger
` 1	Left little
2	Left ring
3	Left middle
4 5	Left index
6 7	Right index
8	Right middle
9	Right ring
0 - =	Right little

If you already touch type, this is a week of deliberate practice, not a course. Type numbers on purpose. Refuse to look. Accept being slow at it for a few days. That is the honest answer, and it does not require software.

The missing numeric keypad

You are not missing anything a typing course would have given you.

The worry behind the question is that a full-size keyboard would have taught you something your MacBook cannot. It would not have. The pad is a separate set of keys for a separate job, learned separately by the people who need it, and the digits a typing course does teach are the ones along the top of the keyboard — which yours has.

The keypad is not a second copy of the number row; macOS treats it as a different set of keys entirely. Keypad 1 is kVK_ANSI_Keypad1, 0x53. The number row’s 1 is kVK_ANSI_1, 0x12. Different codes, different keys, different skill.

A ten-finger course teaches the number row, because the number row is the part every keyboard has. Mochi Type does not touch the pad at all: its 48 key codes contain no keypad code, and neither of its two keyboard renderings draws one. Where the pad is taught, it is taught as its own thing — a separate ten-key drill on separate keys, with its own home position on 4 5 6 — and none of that skill is what a touch-typing course means by touch typing.

If your work is accounting or data entry, a keypad is a real tool and worth buying on its own merits. Just do not buy it as a fix for the problem this page is about; it is not the same problem.

The Touch Bar

Same answer. The strip took the place of the row along the very top of the keyboard — the row with no letters, no digits and no punctuation on it. The numbers, one row lower, stayed as real keys you can feel.

The Touch Bar replaced the function row, and the function row carries no characters — zero of the 48 codes. The number row on Touch Bar MacBook Pros stayed physical, so nothing a typing course covers was ever on that strip.

The legitimate complaint is Escape, which was a virtual target on the earliest Touch Bar models. That is a real ergonomic loss for anyone who lives in vim or dismisses dialogs a hundred times a day, and it is also not a typing problem — Escape is a key for operating a computer, not for writing. It is the one thing on this page with a software fix: the Modifier Keys panel above will map Caps Lock to Escape, which is where a lot of people ended up leaving it permanently.

macOS 26.6 still ships the Touch Bar controls in Keyboard settings — the strings Touch Bar Settings…, Touch Bar shows and Customize Control Strip… are all still in the pane’s English string table — which suggests the configuration surface is still shipped for the machines that need it. I have no Touch Bar Mac to confirm what it draws, and shipped strings can outlive their interface.

Key travel

I have no measured travel figures for you and I am not going to invent any.

What I can say is what the skill consists of. Touch typing is targeting and sequencing, not force. Shallow travel changes the feedback — how confidently you feel a key register — and the standard adaptation is to stop bottoming out hard, which most people arrive at within a couple of weeks without being told. The symptom you feel is uncertainty; the symptom you can measure is accuracy, and accuracy is the number to watch over a fixed short session rather than speed, which will lie to you while you are adapting.

The boundary matters: if keys are physically failing to register or double-firing, that is a fault, not a habit, and no amount of practice touches it. Take it to Apple. Nothing on this page applies.

So which keyboard should you learn on

The one you will use most. If that is the MacBook, learn on the MacBook — and if you already own both, the block is either identical or one key apart, so what you learn on one arrives on the other nearly intact. Budget a few sessions for the bottom-left corner and the number row and you have paid the whole transfer cost.

And you do not need an app for this — a week of typing numbers without looking will do it. What a week of vague practice never gives you is a number to compare against yesterday’s, which is the next section.

What Mochi Type does about the number row and capitals

What software buys you here is measurement and a reason to stay on the boring part.

Mochi Type gives you a Learn session that lasts one minute. Short enough that you will actually sit down and do it, long enough to leave you with a number you can compare against yesterday’s — which is the thing a week of vague practice never gives you.

Two of its stages are built entirely around the part you are bad at. In one, a real number takes the place of every third or fourth word, so you are reaching up for that row over and over instead of once a paragraph. In the other, every second word starts with a capital, so the Shift chord comes round constantly. In both, the digits and the capitals are scored separately from the letters, so a clean run of letters cannot hide three fumbled numbers.

It also does not punish you for going slowly on purpose, which is exactly what retraining a number row looks like: stay accurate and you move on, even if you are crawling. And when the minute is over you get a keyboard coloured by how well you hit each key, with the number of times you hit it, so you can tell a real weak spot from bad luck on three attempts.

That is the whole of it. If you want to go and practise your numbers now, you have everything you need.

If you do want the mechanical version: Learn runs as a fixed 60-second session — not user-adjustable, which is the point: it is short enough that you will do it, and long enough to produce a number. A stage unlocks when one session lands at 95% accuracy and 25 WPM at your current frontier. If you are accurate but deliberately slow, five consecutive sessions at 95% or better unlock the stage anyway, so slowing down on purpose is not punished.

Numbers are stage 16 of 17, the last one before the Final Test, and Capitals is stage 12. In the Numbers stage a real number — a year, a two-digit count, a three- or four-digit figure — takes the place of every third or fourth word. In Capitals every second word is capitalised (German is the exception: it capitalises every noun instead, because that is what German does). For those stages the unlock score is a 50/50 blend of your overall accuracy and your accuracy on the target characters alone, so twenty clean letters cannot carry three fumbled digits.

Afterwards the per-key accuracy heatmap is where you check the work. Hover a key and the tooltip gives you its accuracy together with the number of times you actually hit it, which is the difference between “65% on three attempts” and a real weakness.

The on-screen hint is speed-aware, which matters for an experienced typist who does not want to be taught to read: it starts fading above 25 WPM and is fully dim by 45, then brightens again after a second of hesitation. And setup’s first question screen asks for three things — your typing language, your keyboard layout, and whether your Return key is wide or tall, which is ANSI or ISO. That last one is the shape question the app cannot answer for you.

It is a native Mac app with no account of its own and no sign-in screen anywhere in it, which is a topic of its own. It is also a typing tutor and nothing more — it changes no setting on your Mac, and it cannot do a thing about a key that is physically failing to register. For the problem on this page the app is a convenience. The diagnosis is the useful part: your letters are fine, your number row is not, and a new keyboard was never going to change either one.