Layered layouts raise per-key information density and the chance of hitting the wrong layer

What it is

A cap printed with the primary character, the Shift level, an AltGr third level, and sometimes a fourth raises information density: four outputs share one surface. Density saves physical keys. It also makes people read the wrong corner and press the wrong layer. Aiming is at a character; the hand executes “some layer + some key.” When the layer disagrees with intent, the symbol in the neighboring corner comes out. Wrong-layer errors are specific to multilevel layouts; they are not adjacent-key misses.

Why it happens

Visual search on the cap must pick a corner, then a layer. Four-corner printing encodes layer by color or position (for example AltGr in the lower right), and the encoding fails in low light, on small caps, and under dual-script overprints. After skill forms, people remember “€ is third-level E” and stop reading the cap. When memory disagrees with the current layout—a borrowed board, a remote-desktop input source—the error shifts from “wrong corner” to “muscle memory for the wrong layer.” Caps Lock locks the letter case, not AltGr, yet people may believe the lock grants the third level, producing another layer error. Dead-key errors are timing; layer errors are the modifier bitmap. Both emit a “wrong character” for different reasons.

Studying it

Place the same set of symbols on level two versus level three and measure wrong-layer rate, time looking at caps, and residual layer errors after a layout switch. Contrast color coding with position coding. Record error types on third-level tasks while Caps Lock is on. Include look-alike pairs (/ versus \, - versus _) so the test is not only odd currency signs.

Where it stops holding

Single-legend caps do not produce this error; they dump the third level entirely onto memory or an on-screen map. Large caps and high-contrast ink reduce wrong-corner reads, not “I thought I was on level three but was on level one.” Paged symbol sheets on touch have no four-corner print; wrong layer becomes wrong page. For people who never use level three, density is visual noise and error rate may not rise, but finding the primary character slows.

Applying it

• Keep primary and shifted legends readable first; put the third level in a smaller, spatially stable corner mark. Do not let four corners compete at equal size.
• On-screen key maps should highlight only third-level characters while AltGr is held, reducing a search in which all four are equally loud.
• When docs mention a special character, name the layer (“AltGr+E”) and show the glyph; do not paste a symbol and leave people guessing the corner.
• Verify by asking people, on a photo of the target cap, how to type € or @, then have them type it in low light. Book “got the shifted symbol” separately from “hit the neighbor”; only the former is a layer error.

Related

• Same group: C6.21.1 A dead key does not emit a character immediately; it combines with the next key to form a diacritic · C6.21.2 Without a cue for the pending dead-key state, people think the key is dead · C6.21.3 AltGr and other layered layouts put a third symbol on the same physical key, switched by a modifier
• Adjacent: C6.18 Regional keyboard layout differences · C6.04 Modifier keys
• Search: keycap density · wrong layer · AltGr errors