N3.07.2safety-critical FOV centredesignresearch

Critical information must not sit at the edge

Aliases: centre-priority HUD · missed-alarm placement · inner safe zone

What it is

Battery dying, a collaborator waiting on a confirm, a real piece of furniture about to be hit — information that must be understood on this beat cannot live at the view edge. The edge is the default miss location, not a polite shelf for “secondary”. Safety-critical FOV centre means: the few messages whose failure is irreversible occupy the patch the person is already looking at, not the patch they could “look back to”.

Why it happens

Attention and the fovea usually travel together. When the main task locks both onto the world or a tool, the edge has no promise of periodic scan. Aviation and automotive HUDs put warnings near centre not because that region is prettier, but because a miss is an accident. Spatial UI adds a further split: people may “see” an edge colour patch without reading the type — detection threshold passed, identification not. A tiny red dot in the corner for “disconnected” can be detected and still not understood. Critical information needs understanding, not detection.

Studying it

Signal detection: during a hard main task, inject alarms that must be answered at different eccentricities, and score misses and latency. The main task must be hard, or people will stare at the edge as if it were the view.

Independent variables: alarm eccentricity, encoding (colour / motion / type / sound), main-task load. Dependent variables: miss rate, time to correct response, duration of main-task interruption.

Endsley-style situation-awareness probes and UFOV-style peripheral detection both apply. Split “saw the colour” and “read the word” onto two response keys; do not collapse them into “noticed”.

Where it stops holding

Monitoring jobs treat edge scanning as the skill; radar rings and vital signs at the rim of a surgical view have trained scan paths, and centre-first is rewritten — the scan cycle must still be shorter than hazard growth. Deaf users cannot have the critical channel in sound only; this visual layout does not apply to people who are blind. When optical falloff has already made the true edge unreadable, “edge” sits further in than the display bezel, and the usable centre is smaller than it looks.

Applying it

  • List states whose failure is irreversible (safety, data loss, irrevocable commit). Allow them only in the centre the head need not move to read.
  • Give critical information at least two channels: central vision plus sound or haptics. Do not rely on an edge colour dot alone.
  • Transient alarms may occupy centre briefly and then leave; do not also park standing decoration there.
  • How to check: fire every critical alarm at random during the main task. Time from onset to correct understanding. Any item understood mainly by later review or a prompt is still living at the edge.

Related

  • Same group: N3.07.1 Edge content needs a head turn to be seen clearly · N3.07.3 The edge is fit for presence cues · N3.07.4 Pull edge elements inward to leave margin for optical falloff · N3.07.5 A ring layout fits the shape of the field of view better than a rectangle · N3.07.6 Content outside the binocular overlap is seen by only one eye · N3.07.7 Elements that enter and leave the view with head motion need hysteresis or they flicker
  • Nearby: N1.03 Field of View · N3.04 Text Readability in 3D Space
  • Search terms: safety-critical HUD · missed alarm · useful field of view

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/N3.07.2