All page titles, headings and subheadings should be written in sentence case (not Title Case).

Use a heading that is specific enough to tell the user exactly what the page or form field does. For example, "Reset your password" not “I don’t know my password”.

People reading just the header, subheader, label or page title should know what to expect.

If the page is part of a collection of pages, we should also make that clear from the title.

Where there is only one action a user can take in a section, use the format "[Verb] the [noun]" or "[Verb] your [noun]".

Where a user can take multiple actions on a page, or for section headers and landing page headers, use a noun that covers all of the actions where possible. For example, "Contributions".

For platform content, we do not use questions as subheadings. Where it is completely unavoidable we use the first person for questions.

Text content should be organised with headings, wherever possible, to make it easier to navigate. For example in long form content, information articles and content that can be organised, like a ‘Setting’ menus. 

Some bits of content, like long letters, may not be suitable. 

We should also use headings in the right way if we have control over them. For example, if there are sub-topics, we should use H3s under the relevant H2 and so on.

This is an accessibility requirement, meeting Success Criterions 2.4.2 Page Titled, level A, 2.4.6 Headings and Labels, level AA, and 2.4.10 Section Headings, level AAA.