UI Text

UI text — often called microcopy — includes the short phrases users see during interactions. This includes buttons, labels, tooltips, placeholders, error messages, and more.

When done well, UI text guides users, clarifies intent, and improves usability. Tendoo’s UI text guidelines help teams write consistently, clearly, and with purpose.

Button Text

• Use action-oriented labels: "Save", "Continue", "Upload file"
• Avoid vague terms: 🚫 “Okay”, 🚫 “Submit”, 🚫 “Click here”
• Keep it short: 1–3 words is best
• Use title case for buttons: “Add User”, not “add user”

<button>Save Changes</button>
<button>Cancel</button>

Form Labels & Placeholders

• Labels should be clear, specific, and in sentence case
• Don’t rely on placeholders as labels (accessibility issue)
• Use placeholders only to show expected format or example

<label for="email">Email address</label>
<input type="email" placeholder="name@example.com" />

Tooltips & Help Text

• Be brief: explain, don’t document
• Use complete sentences if more than a few words
• Avoid repeating label information

<Tooltip content="Choose a strong password.">
  <InfoIcon />
</Tooltip>

Error & Success Messages

• Be specific and constructive ✅ “Password must be at least 8 characters.” 🚫 “Invalid input.”

• Avoid technical jargon or codes unless helpful

• Tone should be calm, never blaming

<span className="text-error">Email is required.</span>

Confirmation & Empty States

• Use clear, conversational language
• Tell users what’s happening or what they can do next

Examples:

• "Are you sure you want to delete this file?"
• "No items yet. Create your first one to get started."

General Guidelines

• Use sentence case for most UI text (labels, field names, headings)
• Avoid ellipses (…) unless something is loading or pending
• Avoid using punctuation in button text

Related

• Voice & Tone
• Accessibility Writing
• Grammar & Style

Small words make a big impact. Tendoo’s UI text should always feel helpful, human, and consistent — no matter where it appears.