System anatomy · 07

Legible human interface

Make state, intent, limits, recording, help and stop functions understandable without specialist training.

Evidence statusService decision framework · site and user validation requiredLast reviewed: 14 August 2026
07

FUURAA thesis

An interface fails when people cannot predict or control the encounter.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

State

Use redundant cues for direction, waiting, yielding and faults.

02

Access

Design controls for diverse reach, vision, hearing and language.

03

Truth

Disclose remote help, recording and actual limitations.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    Can first-time users predict motion?

  2. 02

    Can varied users stop or get help?

  3. 03

    Is remote presence visible?

  4. 04

    What if speech interaction fails?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    Interface-state specification

  2. 02

    Evidence package 2

    Accessibility comprehension study

  3. 03

    Evidence package 3

    Misunderstanding and help log

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.