Organise the story

Group information around recognisable questions: what you do, examples of work, useful resources and ways to contact you. W3C explains that headings communicate page organisation and can support navigation through assistive technologies. Use meaningful heading structure as well as visual styling. A line that looks large is not necessarily implemented as a heading, so include structure in the review of the published page.

Write labels that predict content

Prefer “Recent projects” to an abstract label that gives no clue about what follows. Keep headings short but informative. Avoid using a heading solely as a decorative slogan when it obscures the section’s purpose. Review the page by reading only the headings: the outline should make sense. If two sections repeat the same purpose, combine them or explain the distinction more clearly.

Imagine this

Hypothetical example

A hypothetical long profile replaces several vague chapter names with “Services,” “Selected work,” “Resources” and “Start a conversation.” Its visual personality remains, but visitors can now locate documents or contact details quickly. The team also checks that the page uses an appropriate heading hierarchy.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

W3C WAI: Headings ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.