Headings

Use headings to describe and structure content on a page. This:

• helps users find the content before they even get to your page, such as in search engines
• makes it easier for users to skim read, or for screen reader users to jump between sections, and get to the content that’s relevant to them
• creates a logical flow to information, which makes content easier to understand

You must use headings, rather than making text bold. This is important for screen reader users.

Your headings must:

• have a hierarchical structure:
  • use a h1 for a page title
  • h2 for each main section
  • h3 for a sub-heading in a h2 section
  • h4 for a sub-heading in a h3 section
• be clear
• be a few words long and not contain any unnecessary words
• be written as front-loaded statements, not questions
• makes sense on their own
• accurately describe what's in the section
• use an active voice
• use words the user is using
• use sentence case
• only use acronyms that have been defined previously on the page or that are well known
• not end with a full stop

Avoid using gerunds (-ings) in headings. For example, use 'report a missed collection', not 'reporting a missed collection'.

If the heading is about doing something, but not actually doing that thing, reword the heading to avoid using a gerund. For example, 'how to submit a tax return' rather than 'submitting a tax return'.

Do not use the word 'Introduction' as a heading. It's more useful to the user to describe what's actually in the section. You can use 'Overview' in a guide page, if it's really necessary.