Fitts’s Law Calculator

Fitts’s Law Calculator

animation
accessibility
ux-design
Try Open the calculator and make the button 48 CSS px wide, then press Calculate.
Observe After pressing Calculate, read the targeting time and the 44 CSS px size check.
Explain Explain why a larger target, such as 48 CSS px instead of 32, lowers targeting time after you press Calculate.

Technical boundaries. Targeting time uses fixed intercept and slope values of 50 ms and 150 ms. The target-size example is subject to exceptions.

WCAG contrast ratio calculation: For text to be WCAG AA compliant, contrast ratio C=L1+0.05L2+0.05C = \frac{L_1 + 0.05}{L_2 + 0.05} must be ≥4.5\geq 4.5 (normal text) or ≥3.0\geq 3.0 (large text ≥18pt). Light gray #AAAAAA on white #FFFFFF has relative luminance Lgray=0.402L_{gray} = 0.402, Lwhite=1.0L_{white} = 1.0, giving C=1.0+0.050.402+0.05≈2.32C = \frac{1.0 + 0.05}{0.402 + 0.05} \approx 2.32 — fails WCAG AA (needs 4.5). Dark gray #595959 has L=0.0999L = 0.0999, giving C=1.0+0.050.0999+0.05≈7.0C = \frac{1.0 + 0.05}{0.0999 + 0.05} \approx 7.0 — passes WCAG AA.

Touch target accessibility: WCAG 2.5.5 (Level AAA) specifies at least 44 × 44 CSS pixels for pointer targets, subject to exceptions. A 32 CSS px square has area 322=1,024 px232^2 = 1{,}024\,\text{px}^2; a 44 CSS px square has area 442=1,936 px244^2 = 1{,}936\,\text{px}^2, 89% larger. In an illustrative independent two-axis model with independent horizontal and vertical normal touch errors of σ=10 CSS px\sigma=10\,\text{CSS px}, the hit probability for a square target of half-width rr is Phit=erf⁡(r/(2σ))2P_{hit}=\operatorname{erf}(r/(\sqrt{2}\sigma))^2: 32 px gives 79.3% and 44 px gives 94.5%, a 19.2% relative improvement.

Fitts’s Law for motor accessibility: Time to reach a target is T=a+blog⁡2(DW+1)T = a + b \log_2\left(\frac{D}{W} + 1\right) where DD = distance, WW = target width, a≈50msa \approx 50\text{ms}, b≈150msb \approx 150\text{ms}. For a button 200 CSS px away, 32 CSS px wide: T=50+150log⁡2(20032+1)≈50+150×2.86≈479 msT = 50 + 150 \log_2\left(\frac{200}{32} + 1\right) \approx 50 + 150 \times 2.86 \approx 479 \text{ ms}. For 48 CSS px wide: T≈50+150×2.37≈405 msT \approx 50 + 150 \times 2.37 \approx 405 \text{ ms} — 15% faster targeting, critical for users with motor impairments.

Multi-device state sync latency: For a smart home with N=5N = 5 devices (phone, tablet, watch, hub, voice assistant), achieving consistent state across all devices with τsync<500ms\tau_{sync} < 500\text{ms} (perception threshold) requires real-time pub-sub architecture. Star topology (all devices → hub → cloud → broadcast) has 2-hop latency τ=2×(Ldevice−cloud+Lcloud−device)≈2×(150ms)=300ms\tau = 2 \times (L_{device-cloud} + L_{cloud-device}) \approx 2 \times (150\text{ms}) = 300\text{ms}. Peer-to-peer mesh has N−1=4N-1 = 4 simultaneous broadcasts at τ≈20-50ms\tau \approx 20\text{-}50\text{ms} (local network) — 6× faster than cloud round-trip.

Screen reader semantic markup efficiency: In this illustrative navigation model, two 1.5-second jumps through properly named landmarks take 3 seconds versus an assumed 15-second linear scan, an 80% modeled reduction. Use labelled <nav> landmarks for navigation and native <button> elements for actionable controls; do not rely on role="button" alone.

Back to the chapter