Headings

Overview

- Headings are the signposts of a page or slide. They provide structure, help all readers scan quickly, and let assistive technologies (like screen readers) jump between sections. Using true heading styles—not just bold or bigger text—creates a clear, logical outline for your materials.

- Strong heading structure helps students focus and find information fast. Screen‑reader users depend on headings to navigate. Headings also power tables of contents, document outlines, and search, reducing confusion for students and families and saving teacher time.

Use real headings, not formatting: Apply the platform’s built‑in heading styles (H1–H3+) instead of just changing font size or color.
Follow a hierarchy: One H1 for the page title, then nest sections under H2, H3, and so on. Don’t skip levels (H2 → H4).
Keep heading text short and descriptive: State the topic or action (e.g., “Materials,” “How you’ll be graded”).
Be consistent: Pick title case or sentence case and stick with it. Use the same labels throughout (e.g., always “Overview”).
Avoid all caps: Screen readers may spell out words when the text is in all caps; it also hurts readability.
One main idea per section: If a section gets long, add a subheading.

Canvas (LMS): In the Rich Content Editor, use Paragraph → Heading 2/3/4. Canvas reserves the page title as H1, so start in‑page with H2. Use the Accessibility Checker to catch missing headings and lists.
Google Docs: Apply Heading 1/2/3 from the Styles menu. Use View → Show document outline to verify structure. Update the Table of contents so it reflects your headings. Export to PDF to retain tagged headings.
Google Slides: Every slide needs a real slide title (use the Title placeholder or Slide → Apply layout). For content blocks, use consistent visual styles; Slides doesn’t create semantic H2/H3, so rely on clear slide titles and reading order.

W3C Web Accessibility Initiative (WAI) - Headings
- This tutorial explains why headings matter for accessibility and how to use them to organize content effectively. It includes examples that show how clear heading structures improve navigation for all users.
- Read “Headings” on W3C WAI »
WebAIM on Headings
- This guide details best practices for using headings, including how to create logical hierarchies, avoid skipped levels, and test for accessibility compliance.
- Read “Headings” on WebAIM »
W3C Web Accessibility Initiative (WAI) - Page Structure
- This tutorial expands on how headings fit within overall page structure, offering examples of proper hierarchy and navigation to help ensure accessible, user-friendly design.
- Explore the “Page Structure” Tutorial »

Page updated

Report abuse