Clear, consistent language makes interfaces easier to use. These standards apply to every label, message, and action in the system.
Words in use
Name the outcome.
A specific action label tells people what will happen before they choose it.
Too vagueSubmit
Clear actionSave changes
Use the action that matches the task. A booking flow may need “Confirm booking” instead.
Labels
- Use sentence case for all labels and button text.
- Keep button labels to 1–4 words. Write them as verbs that describe the action.
- Avoid punctuation in button labels — no periods or exclamation points.
Save changes
Do
Use a verb that describes the outcome.
Submit
Don't
Avoid generic labels that don't describe the specific action.
Error messages
- Identify the field, the problem, and the recovery action.
- Use plain language — avoid codes or jargon.
- Place error text next to the field it describes.
Placeholder text
- Use placeholder text to show format examples, not as a replacement for labels.
- Placeholders disappear on input and are not reliably read by screen readers.
Tone
- Be direct and helpful. Avoid humor, emoji, or exclamation points in functional UI.
- Use positive framing when possible: "Enter your email" rather than "Email cannot be empty."