Which words belong on an emergency or check-in button

Start with intent

“SOS” signals urgency, “Emergency” names a situation, “Ask for help” describes an action, and “I’m OK” communicates an agreed condition. They are not interchangeable.

Write down what people must understand and what contacts will receive. The label should express that intent, not an internal feature name.

Prefer concrete terms

A button should say what tapping does: send a signal, update family, or open a contact. Avoid “Send”, “Continue”, or “Confirm” without an object.

Visible text and accessible name should describe the same action. An icon can aid recognition but cannot replace the word.

Agree what “I’m OK” means

“I’m OK” should not simultaneously mean safe, read, and no help needed. Agree with recipients which condition it communicates and when to use it.

For a routine check-in, show frequency, recipients, and status. No response is not automatically an emergency or a diagnosis.

Separate emergency from asking for help

If you use “Emergency”, pair it with text explaining that it alerts contacts and does not automatically call public emergency services.

For immediate danger, clearly direct people to the local emergency number. In the EU, 112 is generally free and available; outside the EU, verify the local number.

Translate and check understanding

Translate intent, tone, and consequence, not isolated words. Test local terms for help, emergency, and OK with the people who will use the product.

Ask them to explain what leaves, who receives it, and what does not happen. If meaning depends on an icon, the label is too vague.

Test before release

Try large text, screen reader, contrast, and adjacent buttons. W3C gives 24×24 CSS pixels as an AA target minimum with exceptions, and 44×44 CSS pixels as an AAA criterion; these are not millimetres.

Also test an accidental tap, cancellation, recipients, and status. Document current behaviour and never promise unverified calls or intervention.

Frequently asked questions