Show essentials and let people expand details
A safety interface should make clear what can be done and what will happen. Keep recipients, location, action, and status visible; place secondary context behind an understandable, reversible expansion.
Decide what stays visible
The main screen should keep the recipient or group, any shared location, the primary action, and the operation status. These facts change the decision or explain the result.
Do not make understanding depend on an icon, colour, or memory. A short text label beside the control remains available with zoom, a screen reader, or low light.
Expand secondary context
Permissions, explanations, history, and advanced settings can sit under “Details”. The control needs a clear name, keyboard access, and a state that announces whether the content is open or closed.
Expansion must not hide charges, recipients, duration, or consequences. If information could change someone’s decision before sending, put it in the visible review.
Keep the action recognisable
Use one distinct primary action whose wording says what goes out and to whom. Secondary actions such as edit or cancel need separate labels and should not compete visually.
After tapping, preserve context: recipient and action remain readable while the system shows preparing, sending, or response. Do not replace the button with an ambiguous state.
Design status and focus
Keyboard focus, selected borders, and the open state need sufficient contrast and must not rely on colour alone. The active point should remain visible after expansion.
Separate ready, in progress, successful, failed, and human response. “Sent” describes the system; it does not prove that a family member read or acted.
Keep details accessible
Expandable content should work with touch, keyboard, and assistive technology; the control name should match its visible text. Move focus into newly opened content only when helpful, never unexpectedly.
Offer a simple way to close and do not make the primary control disappear. Test zoom, large text, orientation, language, and spoken output on the real device.
Check understanding and fallback
Ask different people to identify recipients, location, action, and status without opening details. Then ask what consequence they expect in the expanded panel and whether they can return.
Also test no network, a locked phone, low battery, and an unavailable recipient. Agree a call, SMS, or paper instruction: the interface is not an emergency number.
Frequently asked questions
What should always be visible?
Recipients, shared location when applicable, the primary action, and an observable status. Other information is secondary only when it cannot change the decision.
Can a detail always stay behind an expansion?
Not when it concerns cost, recipients, duration, or consequences before sending. Those facts belong in the main path.
Does “sent” confirm that family replied?
No. It describes a system step; reading, understanding, and a human reply are separate events.
Sources consulted
Technical and safety information was checked against the following official sources.
- W3C — clear labels
- W3C — label in name
- W3C — consistent identification
- W3C — accessibility principles
- W3C — cognitive accessibility
- Nielsen Norman Group — heuristics
- European Commission — 112
- My Safe Circle — app features
Editorial note: this guide applies W3C principles and Nielsen Norman Group heuristics to a family-coordination interface. Sources were checked on 8 September 2026; product features and limits can change.
LOOK AT THE FIRST LAYER
Recipients, action, and status must stay readable
Expand context only after making the consequences needed for a decision visible.
Explore My Safe CircleThis guide covers accessibility and coordination; it does not replace emergency services. For immediate danger, call the relevant local number; 112 is the European number where applicable.