StableMobiletouch-ergonomics

Touch Ergonomics — The Hand and the Device

Operationalizes what changes when the input device is a human finger instead of a mouse. The governing idea: a touchscreen is not a small desktop screen — it is a different input channel with different physics. The pointer is fat, imprecise, and attached to a hand that covers the screen; it has no hover, no resting position, and no separate "aim then commit"

touchmobileergonomicstarget-sizethumb-zoneshit-area

Principios

· (any-pointer: coarse) — *can* this device be touched at all? Governs sizing. Hybrid laptops answer yes.
· (hover: hover) — does the *primary* pointer hover reliably? Governs whether hover may add anything.

Patrones

· Size the target, not the icon. A 16px glyph in a 44px box is correct. A 44px glyph is a design decision you probably didn't want.
· Padding beats overlays. Growing the element's own box is visible in devtools, participates in layout, and can't silently overlap a sibling. Reach for a pseudo-element only when the layout truly can't absorb the size.
· If you're adding an overlay, do the arithmetic first. gap ≥ F − (wA + wB)/2. Two seconds of arithmetic prevents the class of bug where the delete button quietly annexes its neighbour.
· Dense tables are the usual crime scene. Row actions inherit desktop density from the first implementation and nobody re-measures. Audit every row-action cluster explicitly.
· The close button is a real button. It gets the floor too — often it's the only escape from the surface.

Riesgos

· Ver anti-patrones específicos del dominio en el pack.

Checklist

[ ] ★ No interactive element is under 24×24 CSS px without a named, genuinely applicable SC 2.5.8 exception. (TEE1)
[ ] ★ No two hit areas overlap; every icon-button cluster satisfies gap ≥ F − (wA + wB)/2. (TEE9, TEE10)
[ ] ★ No hit area of any control overlaps a destructive control's hit area. (TEE11)
[ ] ★ No meaning, control, or warning exists only in a hover state or title attribute. (TEE15, TEE16)
[ ] ★ Every gesture-triggered action has a visible single-tap equivalent, unless the gesture is essential to the function. (TEE46, SC 2.5.1)
[ ] ★ Actions fire on the up-event and are cancellable by moving off before release. (TEE53, SC 2.5.2)

Fuentes

En la bibliografía AKOS

Este pack cita las siguientes fuentes registradas en el índice bibliográfico:

Explorar todas las fuentes →