Skip to main content
Hennepin County Design System

Digital text standards

Find guidance for digital text including headings, text formatting, numbers, alert banners, and user interface copy.

Accessibility

Find information for Writing for accessibility.

Addresses

  • There are 2 different purposes for addresses that affect the layout. One is meant for mailing and the other as a link for users to map or physically go to.
  • This is not for addresses in the Contact module for Sitecore websites.
  • Always spell out directions and type (street, road, boulevard, etc.) in the street address.

Mailing purposes

  • Name of building (followed by a soft return or SHIFT and enter key)
  • Street address, suite or room # (followed by a soft return or SHIFT and enter key)
  • City, state and zip (followed by a hard return or enter key)

Mapping for physical address

House number, street name, direction, city, state and zip should be on the same line with no return. The word “map” should be included after the building name. Not at the beginning.

  • Name of building (followed by a soft return or SHIFT and enter key)
  • Street address, suite or room #, city, state and zip (followed by a soft return or SHIFT and enter key)
  • Name of building map <hyper link to map URL> (followed by a hard return or enter key)

Examples:

Correct

701 Building
701 South 4th Avenue, Minneapolis, MN 55415
701 Building map

Incorrect

701 Building
Map
701 – 4th Avenue South
Minneapolis, MN 55415

Alert banners

  • Keep the alert banner message relevant to the user’s actions or goals.
  • Be clear and concise.
  • Where possible, include actions that inform users or help them resolve an issue.
  • Depending on the context of the message, include a link to further inform the user.

Error and warning messages

Error messages

Error messages notify a user of an issue that prevents them from completing an action. Error messages identify errors and what action to take. 

Error messages can: 

  • Alert a user to a mistake they made while giving input on a screen 
  • Notify a user of a problem on the server side  
  • Alert a user to a problem with their internet connection or local machine 

Error messages must: 

  • Explain how to correct the error if possible  
  • Use clear and concise language  
  • Avoid technical terms users don’t understand, like 404 error or 503 forbidden 
  • Use words that don’t blame the user but instead tell them what to do, for example: 
    Yes: Birth year required 
    No: Failure to enter birth year

Some error messages should link to more content. For example, someone may not qualify for a program they're applying for. Instead of a standard error message, link them to a page that explains eligibility and what they can do next. 

Error messages are also called validation.

Warning messages

Warning messages help users avoid an error or avoid an outcome the user may not want. They save users from confusion and frustration. The text should make sure the user understands the potential negative outcome of an action. 

Warning messages are like error messages. But warning messages alert a user ahead of time rather than afterward. For example, a warning message can tell a user of a missing attachment to a form they want to submit.  

Warning messages can also caution the user of actions they won’t be able to reverse. For example, a warning message may alert a user that if they proceed, they will permanently delete an account profile.  

The user must perceive the message and understand its intent. Use prominent, contrasting colors, like orange, for warning messages. Don’t use red for warning messages. Only use red for error messages.

Heading levels

Heading levels outline the hierarchy of the content. For full detail about heading levels, visit Heading levels.

Number formatting

In digital products, use numerals, unless at the beginning of a sentence:

  • 5,000 (not five thousand)
  • 3 or 4 (not three or four)

Readability tools

Readability tools like Hemingway or Flesch-Kincaid can help catch readability issues that writers and editors miss. The tools flag content that’s hard to read or that has other readability issues.  

Use readability tools with care since they don’t replace careful review by humans.  

Search engine optimization

Good search practices make it easy for people to find our online content. Useful metadata and keywords support good search.

We should use keywords in the page title, URL, and headings. But avoid this where it would break the rules of grammar.

Required metadata

For the page title:

  • Stay within a character limit of 50.
  • Leave off the words "Hennepin County" unless it is critical.

For the meta description:

  • Stay within a character limit of 156.
  • Use a concise description of the page content.

Optional keyword metadata

Keywords affect internal site search only. They don't affect external search such as in Google, Bing, or Yahoo.

Guidance for keywords: 

  • Use words or phrases not found on the page itself (like common misspellings, abbreviations, and slang).
  • Use up to six keywords separated by commas.
  • If no helpful keywords exist, you can ignore the keyword field in Sitecore.

You can ignore these Sitecore fields:

  • Audience
  • Service area
  • Content type
  • Department
  • Page owner email

Text formatting

Consistent formatting helps people read and understand text. Special formatting can increase clarity.

Use special formatting with care, to call out critical words:

  • Use bold to clarify key information, for example: "Walk-ins are no longer available. You must make an appointment." For more information, visit Bold and italics.
  • Use italics to call out a name, title, or label, such as: "When you arrive, push the Call button outside the main door."

Don't use these text formats:

  • Underline
  • Highlight
  • Color other than the standard black text color
  • All caps other than acronyms

Transcripts and subtitles for video and audio

For standards and guidance on transcripts and subtitles, visit Writing for accessibility.

User interface copy

User interface copy (UI copy) is the small bit of text that describes an action a user can take.

Examples of UI copy:

  • In buttons to execute an action: Submit, Finish, Pause, etc.
  • For confirmation before a final decision: Do you want to delete (item)?
  • In radio buttons to choose one option in a list: Monday, Wednesday, Friday

Keep UI copy short, clear, and meaningful:

  • Use 2-4 words. But use more words if you need, to clarify the task.
  • Lead with action words like submit, complete, or accept.
  • Avoid vague words like OK. State in a clear way what users will do by choosing the button.
  • Don’t use verbs for common labels. For example, use back, not go back.
  • Don’t use the words a, an, or the.
  • Use common words. Limit the use of terms unique to the county.
  • Use action words in a consistent way throughout the website or application.

Adapted from Nielsen Norman Group’s guidance on UI copy.