One decision per screen: progressive disclosure

Assess the real situation before the tool

With recognition, the option is present: someone sees “SOS”, “ALL OK” or “I need help” and compares it with their intent. Recall means remembering that a particular icon, long press, sequence or menu item produces an effect. The recognition-over-recall heuristic encourages visible objects, actions and choices. To compare this step with a related case, see Tremor and low dexterity: design an action people can tap.

This is design guidance, not a law that recognition is always easy. A word may be unfamiliar, a label too small, a translation unnatural or two choices too similar. Familiarity, vision, attention, literacy, language, assistive technology and context affect the result.

For a safety control, consequences matter too. Recognising its text does not reveal who receives it, whether location is included, whether a call starts or how to cancel. Put those facts where they are needed rather than relying on an explanation read weeks earlier.

What W3C guidance actually says

The W3C “Use Clear Visible Labels” pattern recommends common, understandable words, visible labels beside their controls and support for assistive technologies. It explains why missing or unclear labels can especially affect people with cognitive, memory or executive-function difficulties, and calls for user testing where the association is not immediate.

“Label in Name” connects visible text with the accessible name. If someone sees “Ask for help” but speech input knows the control by a different name, interaction may fail or surprise them. The visible words should therefore be included in the accessible name under the applicable criterion and techniques.

“Consistent Identification” and predictability guidance call for components with the same function to be identified consistently. Stability does not forbid improvement, but changing wording, colour, position and behaviour together makes prior learning harder to transfer.

A verification matrix for safety buttons

This matrix is neither a clinical score nor an accessibility certification. It turns the heuristic into observable questions before a routine depends on a control.

Visible labels and stable actions must remain honest

An effective label describes the action or outcome in words its audience uses. “Send SOS” is clearer than an unlabelled triangle, but may still omit who receives it. “Call emergency services” would be false on a control that only opens the dialler: visible promise and behaviour must match.

Stability means a recurring control keeps its name, relative position and consequence unless there is a reason to change. Colour and icon can reinforce the difference but should not be the only cue; colour vision, low vision, screens and cultural conventions make that fragile.

Confirmation may prevent accidental sends and show recipients, message and location. It also adds a step. There is no universally correct tap count: compare error risk, urgency, motor ability and cancellation, then measure with representative people.

Applying it to My Safe Circle, including its limits

My Safe Circle keeps SOS and ALL OK as separate free Home actions. SOS requires confirmation and a countdown. Message and location are optional, and location is added by explicit choice. The app may open the dialler but does not complete an emergency call.

“How are you?” requests show “I’m OK” and “I need help”. Replies are free; creating a manual request, which lasts 30 minutes, requires Premium. Creating or reactivating a recurring Reminder requires Premium and the recipient’s specific approval before it starts. The same operational plan is developed further in Delivered, read, understood, acknowledged: four different things.

These labels expose choices but cannot ensure that every person recognises or operates them. My Safe Circle does not detect incidents or medical conditions, call emergency services automatically, or guarantee delivery, reading, understanding or action. A call, SMS or accessible command that suits someone better should remain in the plan.

Checklist: test the control, rather than merely showing it

A desk review finds obvious issues but cannot replace real use. Include people representing the intended languages, ages, abilities, devices and assistive technologies.

A recognisable interface is not an emergency service. With concrete immediate danger, use the most suitable channel and call local services. In the EU, 112 is common and free.

A practical example to rehearse

Example: the first screen asks for the signal type; details and confirmation appear only after an understandable choice. Name the responder, backup and point for changing channel in advance, confirming that both people accept the role. Collect only data needed for the purpose and review consent, contacts and instructions when the routine changes.

One decision per screen may reduce clutter, yet extra screens can increase memory demand, waiting and abandonment. Rehearse on the real device at a calm time and record only observed obstacles without judging the person. The fallback should use a different channel and remain accessible when the app or smartphone fails.

Essential information such as recipients and sending consequences should not be hidden behind an unexpected path. Connectivity, battery, notifications and human availability change; no single tool guarantees delivery, reading or action. A missing reply triggers the agreed protocol, not automatic assumptions about health or intention.

A summary before a consequential action supports correction without assuming that every person prefers it. Collect only data needed for the purpose and review consent, contacts and instructions when the routine changes. Write an observable next step with a realistic margin and one person responsible for checking it.

When it is unnecessary and what backup remains

Progressive disclosure is unnecessary for a short, familiar task when it adds screens without clarifying a choice. The fallback should use a different channel and remain accessible when the app or smartphone fails. For concrete immediate danger, call the local emergency number directly and provide verifiable facts.

Experienced users may benefit from consistent shortcuts while labels and outcomes remain predictable. A missing reply triggers the agreed protocol, not automatic assumptions about health or intention. Name the responder, backup and point for changing channel in advance, confirming that both people accept the role.

Test the flow with the real language, text size, screen reader and orientation, rather than counting taps alone. Write an observable next step with a realistic margin and one person responsible for checking it. Rehearse on the real device at a calm time and record only observed obstacles without judging the person.

When the path is not understood, retain an agreed simple channel such as a call or SMS. For concrete immediate danger, call the local emergency number directly and provide verifiable facts. Connectivity, battery, notifications and human availability change; no single tool guarantees delivery, reading or action. Before testing, check the features described on the website.

• Observable purpose defined
• Responder and backup agreed
• Real-device rehearsal
• Only necessary data
• Independent second channel
• Local emergency route distinct

Frequently asked questions