Headings

Headings are critical for digital accessibility because they provide structural organization that allows assistive technologies to navigate a page efficiently. Without proper headings, screen reader users must read an entire page sequentially from top to bottom to find specific information, rather than jumping directly to the content they need.

Why Headings Matter

• Screen Reader Navigation: Blind users use keyboard shortcuts to jump from heading to heading. This lets them scan a page rapidly, much like a sighted user skimming a text visually.
• Logical Page Architecture: Headings establish a clear visual hierarchy. They break complex walls of text into smaller, digestible sections, which reduces cognitive load for users with learning disabilities.
• Contextual Signposting: Descriptive headings tell readers exactly what information follows. This helps users with short-term memory loss or focus challenges stay oriented on the page.

Best Practices for Accessible Headings

• One h1 Per Page
  • The h1 tag is best used for the main title of the page or document to clearly establish the primary topic. 
• Never Skip Levels
  • Always nest headings sequentially (e.g., h1 followed by h2, then h3)
  • Skipping from h1 directly to h4 confuses screen reader users.
• Use actual tags or built-in document styles.
  • Simply making text bold and increasing the font size does not tell assistive technology that it is a heading.

Example:

• H1: Department Name
  • H2: Courses
    • H3: Undergraduate Courses
    • H3: Graduate Courses
  • H2: Faculty
  • H2: Students
    • H3: Undergraduate Students
    • H3: Graduate Students

Consult the following tutorials for different content platforms:

• Headings in Microsoft Word (video)
• Headings in Google Docs
• Headings in HTML