Should a Typing Test Stop You When You Make an Error?

Some typing tools refuse the wrong keystroke. Type the wrong letter and nothing happens — the caret sits there until you produce the right one. The reasoning is intuitive: if errors are what slow you down, do not let errors happen.

It is a defensible design. It is also, as far as the published literature goes, unsupported.

There is no typing study either way

This is the honest starting point. Search for evidence that error blocking improves typing speed or accuracy, and you will not find a controlled study that tested it. You will find strong opinions, product decisions, and forum arguments, but not a result.

Anyone telling you that blocking “helps learning” is extrapolating from adjacent research. So is anyone telling you it hurts. The correct answer to “which is better” is currently nobody has measured it in typing.

What we do have is a broader motor learning literature, and it is genuinely split.

Errorless versus error-based practice

Errorless learning — structuring practice so mistakes rarely occur — has real support, particularly for beginners and for learners with impaired memory. The argument is that an error, once made, leaves a trace that competes with the correct action. Prevent the error and there is nothing to compete.

Error-based learning has equally real support, particularly for skilled performers. Here the argument is that the correction is the learning: the nervous system tunes a movement by comparing what it intended with what it got, and removing errors removes the signal it tunes from.

These look contradictory until you notice they are describing different learners. The Challenge Point Framework reconciles them: the optimal difficulty of practice depends on the skill of the practitioner. Novices are overwhelmed by error and benefit from having it reduced. Experts are under-stimulated without it and benefit from exposure.

Applied to typing, that suggests blocking may genuinely help someone still hunting for keys, and may genuinely hold back someone already typing at 70 WPM. It does not suggest one setting is correct for everyone — which is what a hardcoded default implies.

The failure nobody predicted

There is one consequence of error blocking that is not theoretical at all, and it is a design failure rather than a learning one.

When a typing interface silently refuses input, users do not conclude that they made a mistake. They conclude that the software is broken. The most commonly reported version is a user insisting that their spacebar has stopped working — because they finished a word, pressed space, and nothing happened, since an earlier character was wrong and they had not noticed.

This is a discoverability problem, and it is severe. The interface is applying a rule the user does not know exists, using the only feedback channel it has — doing nothing — which is indistinguishable from a bug.

Any tool that blocks input has to solve this explicitly. A refused keystroke needs to look refused, immediately and unmistakably, or the feature reads as a malfunction.

What this means for how you practise

Three things follow, none of which require settling the research question.

Do not treat a blocked test as more rigorous. It measures something different, not something better. A blocked score and an unblocked score are not comparable, so pick one and stay with it if you are tracking progress.

Match the setting to where you are. If you are still learning key positions, blocking prevents you from drilling a wrong reach twenty times before noticing. If you are refining speed at a level you already control, blocking mostly interrupts the rhythm you are trying to build.

Watch what an error costs you, not just how many you make. The real expense of a mistake is not the wrong character — it is noticing, stopping, deleting and rebuilding your place in the sentence. That sequence runs two to three seconds, during which a 60 WPM typist would have produced three more words. Ten errors in a minute do not cost you ten characters; they cost most of the minute.

That last point is why accuracy dominates speed in practice, and it holds regardless of whether your tool blocks you or not.

The 97% rule still applies

Whichever mode you use, the practical target is unchanged: practise at whatever speed keeps you above 97% accuracy. When you can hold that comfortably, push your speed until accuracy dips to around 95%, work there until it climbs back, then push again.

It is almost too simple to call a technique, and it is the difference between practice that compounds and practice that just burns time.

Where to start

The typing test reports accuracy alongside speed, and the gap between your raw and net WPM shows exactly how much speed your errors are costing you — the number that matters more than either setting.

For structured work with accuracy targets built in, the typing lessons progress from the home row up. If you want a short, repeatable benchmark to track over weeks, the 1 minute typing test is the standard format most published averages are based on.