Lists

Lists make it easy for users to scan and understand a series of items. Structure and style lists with the user in mind. Set up grammatical structure for list items with a lead-in.

Structure items in a series as a list

Lists are series of items. All lists have a 'lead-in' (a phrase or sentence) or heading to introduce the list.

Use lists to:

  • help users skim information
  • group related information
  • help users understand how items relate to each other
  • show an order of steps
  • arrange information by importance.

Lists can be ordered or numbered (the order is important) or unordered (the order is not critical).

Plain language and word choice

Plain language can express complex ideas. Engage people with words they can understand quickly: use the list on this page. Clarify expressions people might be unfamiliar with.

Use everyday words

Choose words that people are familiar with. Unfamiliar words make content harder to read and understand.

Like this

Email your receipt by 5 pm today to claim the prize.

Age diversity

Refer to age only if it is necessary. Use respectful language and consistent style if age is relevant.

If age is relevant, follow style conventions

Question whether age is relevant. Avoid referring to a person’s age or an age group if it’s not relevant.

If you need to mention age, follow style conventions:

Paragraphs

One idea per paragraph helps users absorb information. Organise them under headings to help users scan the content. Write short paragraphs, each with a topic sentence.

Limit each paragraph to one idea

People find it easier to understand content when a paragraph contains only one idea or theme. Don’t introduce a new idea in the middle or at the end of a paragraph. Start a new paragraph instead.

Introduction or summary paragraphs recap ideas covered in the content. Group sentences in these paragraphs by theme – for example, to help users understand how the content is structured.

Put paragraphs in the order that makes sense to the user

Order paragraphs in a logical sequence, such as:

Headings

Headings help users scan content and find what they need. Organise content using clear heading levels. Begin each heading with keywords and keep it to the point.

Write headings that are clear and short

Headings organise information. Clear headings are specific to the topic they describe.

Keep them brief. They are signposts for people and for search engines.

Many people skim through headings to check whether a page is relevant before they read it in detail. Search engines use headings to analyse and rank content.

Accessibility requirements

User needs:

Emails and letters

Concise letters and emails tell a recipient what they need to know. Use the right level of formality for the recipient and purpose. Be mindful of people’s privacy.

Identify the user and purpose

The user (recipient) and the purpose determine whether you use an email or a letter.

The level of formality in the writing depends on the recipient and the purpose.

When you write emails or letters for work, use the right format and tone for the purpose.

Users vary. They include:

  • people outside government
  • colleagues in the department or agency
  • colleagues in other departments or agencies.

Consider the kind of relationship that you have with the recipient.

Alt text, captions and titles for images

Alternative text explains information in images for screen reader users. Captions describe images to help users relate them to surrounding text. Titles identify images and number them in long-form content.

Give all users access to the same information

When people use content with images, they get information from different elements.

Users combine information from:

  • image captions and titles
  • body text and the images themselves
  • alt text.

These elements have different purposes.

Reports

Create complete reports with a landing page, preliminary content, body and endmatter. Include other parts if the report needs to be tabled in parliament.

Order the parts of the report

There are conventions that apply to how the information in reports should appear.

The basic parts of a report are:

  • a landing page (a cover for printed reports)
  • preliminary content (separate pages in printed reports)
  • the main part of the report
  • supporting information (endmatter).

The type of report will determine what to include and where.

Images

Images can help users if they are clear and simple. Make sure everyone can access the information that images convey.

Add images only if they help the user

Use images if they help users complete their task with your service or product. Images can make it easier for some people to understand information.

Types of images include:

  • photographs and decorative images
  • charts, graphs and maps
  • diagrams
  • drawings
  • icons.

Copyright requirements

You must get permission (a licence) to use copyright material. This includes images and text.

Tables

Tables provide a structure for complex and detailed information. Design accessible tables and organise data so it’s easy for users to scan.

Use tables if they make content easier to read

Use a table only if there isn’t a simpler way to present your content, such as a list, paragraph of text or diagram.

Use tables for exact values and information that is too detailed for the text.

Don’t create a table for only one or 2 items. Report them in the body of the text instead.

Design tables to allow users to:

Help us improve the Style Manual

Did you find this page useful?
Do you have any other feedback?
Is your feedback about:
Select the answer that best describes your feedback:
Do you work for government?
Are you interested in taking part in Style Manual user research?
Please tell us a bit more about yourself.
Do you work for government?