Content structure · nuanced · v4.6.1

STR-01

Use headings to create scannable structure in help content, onboarding flows, and long-form UI copy. Short UI copy like error messages, tooltips, and confirmations don't need headings.

Pass example

What you'll need: a valid photo ID and a recent utility bill or bank statement.

Fail example

To complete verification you will need to provide a valid government-issued photo ID and you should also have a recent utility bill or bank statement that shows your current address on file with us.

Relevant content types

Version history

  1. v4.6.1 · 2026-04-23

    Per-standard version tracking introduced. Every standard starts at the library version current at introduction; bump per-standard when the rule text, examples, or content_type_notes change.

Related standards

Other standards in the Content structure category.

  • STR-02 — Keep paragraphs short. 2-3 sentences max for UI copy and help content.
  • STR-03 — Use parallel structure in lists and sequential steps. Each item should follow the same grammatical pattern. In multi-step flows, a final result-state item ('You're ready to go', 'Your account is set up') may shift to declarative when it describes an outcome rather than an action.
  • STR-04 — Front-load key information in tooltips and microcopy. Users may not read to the end.
  • STR-05 — Group related information together. Don't scatter details across disconnected sections.
  • STR-06 — Nest headings hierarchically. Never skip heading levels for visual styling. H1 for page title, H2 for sections, H3 for subsections.

← The content model