Heading

Utility component for rendering consistent typographic hierarchy and semantic headings

Accessibility

Semantics

  • Use semantic heading elements (<h1><h6>) to define the structure of the page.
  • Screen readers use heading order to build a document outline, allowing users to jump between sections.
  • If a heading must look different from its semantic level, use elementType="h2" and a visual variant (e.g., emphasis="bold"/size="large") to preserve semantics while adjusting style.

Hierarchy

  • Do not skip heading levels arbitrarily – this can disorient screen reader users.
  • Keep the order meaningful, reflecting the visual and logical page hierarchy.

Landmarks

  • When headings label a section, ensure they are inside proper landmark regions (<section>, <article>, <nav>, etc.) for better structure.

Contrast and Readability

  • Heading text must meet WCAG AA contrast against the background.
  • Ensure sufficient line height and spacing for readability.