Skip to main content

Punctuation

Ask AIView as Markdown
Copy a prompt to ask an AI assistant about this page.

We recommend a minimal approach to punctuation as it can add cognitive load and presents consistency challenges across products, portfolios and teams.

Ampersand &​

Use only when part of an official or registered product or company name. Although space-saving, many screen readers are unable to interpret ampersands correctly.

  • Legal and logistics
  • Documents and downloads
  • Legal & logistics
  • Documents & downloads

The common phrase "About & legal" always uses the ampersand. This is the only exception in our guidelines for ampersand use.

  • About & legal
  • About and legal

Apostrophe ’​

Apostrophes look like a single quotation mark, show ownership and create contractions (I'm, you're, they're).

  • customer's role (single customer)
  • customers' roles (multiple customers)
  • The folder's contents are displayed in the dashboard.
  • Today's date is displayed in the banner.

With our minimal punctuation approach, we limit apostrophes by using nouns as adjectives.

  • Select file location.
  • Edit user profile information.
  • View employee details.
  • Set time format.
  • Select the file's location.
  • Edit user's profile information.
  • View employee's details.
  • Set the time's format.

Asterisk *​

Use a single asterisk to indicate required fields. Place them immediately after the text without a space. A legend explaining what the asterisk means, typically at the top of forms, is recommended.

Note: Consider adding asterisks automatically via attributes within your component to remove the manual load and prevent duplication. See Forms field (component).

  • Device name*
  • Device name *

Bullet points •​

Use bullet points to break down complex information into scannable, digestible chunks. They help users quickly identify key points and reduce cognitive load. Use consistent bullet styles within a single list or section.

For unordered lists, use the HTML <ul> element. In iX applications, unordered lists should be displayed using the standard bullet point style.

For ordered lists, use the HTML <ol> element. Use numbered lists only when the sequence or priority of items matters.

Maintain a parallel structure within a list; if one item is a complete sentence, make all items complete sentences.

  • Key features:
      • Real-time monitoring
      • Automated alerts
      • Custom dashboards
  • Setup steps:
    1 Connect device
    2. Configure settings
    3. Start monitoring
  • Benefits include:
      • Increased efficiency across all operations.
      • Reduced downtime through predictive maintenance.
      • Enhanced visibility into system performance.

Colon :​

Use to introduce lists, options, descriptions, settings and preferences to visually separate labels and input fields. Colons help to enhance readability when both the labels and input area are not visually distinguishable. When it's clear within the interface what needs to be completed, remove the colon.

  • Username Felix (color to distinguish fields)
  • Username: Felix (colon to visually separate label and field)

Comma ,​

Use commas to separate data in lists for clarity.

  • Jane Roe, Admin, 3 plant zones
  • Jane Roe Admin 3 plant zones

The Oxford comma is placed before the final "and" or "or" in a list of three or more items. It is acceptable to use and can help avoid ambiguity, but omit it when space is limited in the UI. Remove the Oxford comma especially if it causes text to wrap or overflow in constrained UI elements such as labels, tooltips or buttons.

  • Save, print or share this document.
  • Settings include notifications, privacy, and security.
  • Status: Connected to WLAN, Bluetooth, and USB.
  • Before proceeding, save your work, close all applications, and disconnect external devices.
  • Mix components A and B, catalyst C, and hardener D in separate containers.

Ellipsis …​

Use ellipsis with transitional text to inform users that something is happening and ongoing. There are never spaces between the text and the ellipsis.

  • Searching…
  • Retrieving notifications…
  • Searching . . .
  • Retrieving notifications.

They are also sometimes used to show that a new dialog box will open within the UI, e.g. "Print…" or "Save as…", but as this comes with consistency challenges it is slowly being removed from UX writing guidelines.

  • Save as
  • Save as…

Hyphen ‐​

Hyphens join words together (drop-down menu) and connect prefixes to words (non-technical). Use hyphens to avoid confusion and enhance readability. Never use spaces before or after the hyphen.

  • read-only memory
  • user-friendly
  • pre-provisioned
  • preprovisioned

Remove hyphens for widely understood terms that have evolved beyond needing them.

  • email
  • database
  • ecommerce
  • e-mail
  • data-base
  • e-commerce

Minus sign −​

Use the proper minus sign (−) rather than a hyphen (-) when expressing negative values or subtraction. In UI contexts such as labels, values or data displays, the minus sign should be used to ensure mathematical clarity. The minus sign should be placed directly before the number with no intervening space except for mathematical operations for readability. See Formatting of Numbers and percentages.

  • The temperature dropped to −12°C
  • Balance: −$50.00
  • 10 − 3 = 7
  • The temperature dropped to -12°C (hyphen as minus sign)
  • Balance: -$50.00 (hyphen as minus sign)
  • 10-3=7

En and em dashes – —​

They look similar, but there are two dashes and we use them differently from hyphens and the minus sign.

Use the smaller en dash to connect times, numbers and date ranges. Use the longer em dash to replace commas, brackets or colons.

Don't use spaces when using en dashes for number ranges. In all other cases, add spaces before and after en dashes and em dashes for digital readability.

Em dashes are often used in longer texts to make part of the text stand out, such as telling users about special or new application features. To avoid em dash overuse, we typically use commas instead within UI text to connect phrases.

  • Maintenance planned Monday – Thursday (en dash)
  • Threshold range: 15–20 (en dash)
  • Our new obsolescence feature, available now, gives you more sustainability opportunities
  • Maintenance planned Monday - Thursday (hyphen)
  • Threshold range: 15-20 (hyphen)
  • Our new obsolescence feature — available now — gives you more sustainability opportunities (em dashes)

Exclamation mark !​

Use only for high-level alarms. We don't use them for messages, notifications or for any other communication with our users. And, as the exclamation mark is often within warning icons, it doesn't need to be added to text to signify the strength of our messaging.

  • Critical system error detected. Immediate attention required!
  • Welcome to your dashboard!

Forward slash /​

Use forward slashes sparingly in UI text. They work well for established patterns and technical contexts, but can reduce clarity and accessibility. Forward slashes are appropriate for established UI patterns like on/off and country/region, mathematical fractions, file paths, and compact form labels where space is limited. Use lowercase in body text (on/off) and sentence case following standard capitalization rules (see Capitalization guide). Use lowercase after the slash unless it’s a proper noun.

Avoid spaces before or after the slash unless spaces enhance clarity in larger text blocks or when there is complex formatting where spaces can enhance readability.

  • country/region
  • 3/4 cup
  • Toggle on/off
  • C:/Program Files/Industry
  • Enable notifications and/or alerts
  • country / region
  • 3 / 4 cup
  • Click Save/Export
  • C: / Program Files / Industry
  • Enable notifications and / or alerts

Parentheses and brackets​

There are several types of parentheses (also known as brackets). For all variations, there are no spaces between the parentheses and the text within them. However, there are spaces before and after all variations except when followed by another punctuation mark.

Round ( )​

Use sparingly to give users additional information or clarify messaging. Consider alternative punctuation first, e.g. commas or dashes. Use when the information is supplementary but helpful.

  • Available in multiple formats (PDF, DOCX, TXT)
  • Review the settings (see Figure 1).
  • Our new software version is here. Get ready for enhanced features, improved performance (and a seamless user experience).

Curly { }​

Use for variables, placeholders and programming.

  • Service alert: {deviceId} - {errorCode}
  • Template: {customerName}

Square [ ]​

Rarely used within UI text. Sometimes used for units but more common within academic authoring, quotes and translations to indicate errors, omissions or text in other languages.

  • Save assets, e.g. valves [Ventil] within your plant zones.
  • "A real game-changer for the [food and beverage] industry."
  • Room temperature [°C]

Angular < >​

Use to show file paths and navigation more clearly in applications. Add spaces before and after for enhanced readability except when followed by another punctuation mark.

  • Open > Open file > Upload file > Save
  • Open>Open file>Upload file>Save

Periods / full stops .​

Use consistently. We use full stops at the end of all full sentences and file extensions (.csv .txt .zip).

  • Heading: No zones created
  • Description: Create zones from your dashboard.
  • Heading: No notifications.
  • Description: We'll notify you when there are updates or activities related to your account.

When creating lists or using bullet points, use full stops for full sentences. If even one item in your list requires a full stop, add full stops to all items to keep punctuation consistent.

  • List items:
      • Quick setup
      • Easy integration
      • 24/7 support
  • List items:
      • Quick setup is available.
      • Easy integration with existing systems.
      • 24/7 support for all users.

We do not use full stops for toast messages (brief pop-ups), headings, titles or icon/button text labels. No space before a full stop. Only one space after a full stop between sentences.

  • Assets deleted (toast message)
  • Home (icon label)
  • Assets deleted. (toast message)
  • Home. (icon label).

Question mark ?​

Question marks are appropriate for genuine informational questions, in help text and search prompts. However, avoid them in headings, even when phrased as questions, to maintain a confident and declarative tone.

  • Need help? Contact support.
  • What are you looking for?
  • What's new with Version 3.4?
  • What's new with Version 3.4?

State consequences clearly and use direct language that empowers users rather than questioning their choices. Avoid "Are you sure...?" phrasing specifically, as this can seem patronizing and undermines user confidence.

  • Deleted users lose their access immediately.
  • Are you sure you want to delete users?

Never use multiple question marks for emphasis. Use one space after a question mark when it appears mid-sentence, and no space before.

  • Really???
  • Need help ?

Quotation marks " "​

Use consistent quotation marks throughout the UI. We typically use straight double quotation marks, not single or curly, for direct quotes and to highlight UI text when it improves readability. Use quotation marks to differentiate UI elements only when the same word appears multiple times in close proximity or when clarity requires it. Avoid overusing quotation marks around UI elements as most of the time, the context is clear without them.

  • Select Save to apply a time zone
  • Select "Save" to apply a time zone.

Never use quotation marks for emphasis or to add informal tone. No space between quotation marks and the enclosed text. One space after the closing quotation mark when mid-sentence.

  • Customers said, and I quote, it was "a real gamechanger for the industry."
  • This feature is "amazing" for productivity.

Semi-colon ;​

Use semi-colons to separate key application features to enhance and contrast them, and to present steps or sequential information. We prefer using commas or short sentences instead as semi-colons are easily misused and misunderstood. No space before a semicolon. One space after a semicolon when mid-sentence.

  • The system is offline; check your connection.
  • Our app offers real-time plant updates; personalized dashboards; and interactive maps.
  • Our app offers real-time plant updates, personalized dashboards and interactive maps.
  • 1. Calibrate sensors;
    2. Set operating parameters;
    3. Start the process.
  • The system is offline ;check your connection.
  • The system is offline;check your connection.

Tilde ~​

Use the tilde primarily in technical contexts to indicate approximation and home directories in file paths. In UI text, we prefer "approximately" or "about" for better clarity and accessibility when there is space within the UI. Add spaces before and after the tilde when using it to mean "approximately" in text. Remove spaces when used in file paths or technical notation.

  • File path: ~/Documents/Projects
  • Processing time: ~ 5 minutes
  • Processing time: about 5 minutes
  • Temperature range: approximately 20–25°C
  • File path: ~ / Documents / Projects
  • Processing time: ~5minutes

Trademark symbols ™ ®​

Use the correct symbol for the correct context. ™ is used for unregistered trademarks, ® is used for registered trademarks. Always follow Siemens brand guidelines when applying trademark symbols to product and service names.

Only use the trademark symbol on the first mention of the name on a page or screen. Don't repeat it every time the name appears.

Never place a space between the name and the symbol. Don't alter the size or position of the symbol, it should always appear as a superscript.

  • BrandName™
  • BrandName®
  • BrandName ™
  • BrandName ™®

Note: If you are unsure whether a product name is a registered or unregistered trademark, check with your legal or brand team before publishing. Using the wrong symbol can have legal implications.

Punctuation and spacing​

Spaces before punctuation: As a general rule, there are no spaces between text and its following punctuation.

  • The system, now fully updated, is ready to use.
  • The system , now fully updated , is ready to use.

Spaces after punctuation: Use only one space after periods (full stops), commas, semicolons, colons, exclamation marks, question marks and quotation marks.

  • Welcome to your new app experience. Log in to see more.
  • Welcome to your new app experience.    Log in to see more.

Spaces before and after punctuation: No spaces inside parentheses or quotation marks.

  • Our new software version is here. Get ready for enhanced features (and a seamless user experience).
  • Our new software version is here. Get ready for enhanced features ( and a seamless user experience ).