Accessibility HELPS: Headings

Accessibility HELPS - Headings 

Headings support users in browsing for the information they are interested in. They break up content, allowing viewers to prioritize what they read. Headings are important for any structured document, making content easier to write, scan, and read, especially if the document is not expected to be read in a specific order.

Headings should be considered when developing content to support all readers.

Tip: Consider your headings first! Outlining a document ensures you cover all necessary content, and the outline can often serve as the basis for your headings. This also makes proofreading easier and faster by organizing your thoughts and verifying that information directly supports your headings.

Use Hierarchical Structure:

Organize headings in a logical, hierarchical order. Start with Heading Level 1 for the main title, followed by heading level 2 for major sections, heading level 3 for subsections, etc.

Do not skip heading levels. This ensures a clear and understandable structure.

Should Not Be Used for Emphasis:

Use headings to define sections of content, not for visual emphasis. 

Avoid pseudo-headings

Do not use large, italic, or bold text to mimic headings. This practice is not recognized by assistive technologies, can confuse readers, and increases cognitive load in determining important information.

Use Clear and Concise Language:

Ensure headings clearly describe the content that follows. This helps users quickly determine if the section contains the information they need. Long headings may not make sense and reduce the benefit of scanning through a document.

Use Parallel Structure:

Maintain a consistent grammatical structure in headings at the same level. For example, if one heading starts with a verb, other headings at the same level should also start with verbs. Parallel structure makes it easier for users to scan and understand the content.

Example Heading Structure:

This is the basic layout of this subunit, which could have been provided in a single, large example document:

  • Heading 1: Accessibility at the Beach
    • Heading 2: Accessibility Defined
    • Heading 2: Getting Help
      • Heading 3: Resources for Students
      • Heading 3: Resources for Employees
      • Heading 3: Resources for the Public
    • Heading 2: Best Practices
      • Heading 3: Accessibility HELPS
        • Heading 4: HELPS Advice - Headings
        • Heading 4: HELPS Advice – Explain (audio-visual content)
        • Heading 4: HELPS Advice - Language
        • Heading 4: HELPS Advice - Presentation
        • Heading 4: HELPS Advice – Structure
      • Heading 3: Advice for specific formats
        • Heading 4: Accessible Word
        • Heading 4: Accessible Web
        • Heading 4: Accessible Powerpoint
        • Heading 4: Accessible PDF
      • Heading 2: ATI information
        • Heading 3: Contacts
        • Heading 3: Newsletters
    • Heading 2: Policies
    • Heading 2: Contact

The primary title is Accessibility at the Beach. It is separated into the following Heading 2s:

  • Accessibility Defined
  • Getting Help
  • Best Practices
  • ATI Information
  • Policies
  • Contact

This is further broken down where necessary. Heading 2: Getting Help includes the following Heading 3s:

  • Resources for Students
  • Resources for Staff
  • Resources for the Public

These pages could be further separated into subsections; For instance, the heading 3: Resources for the Public page could include information on Heading 4s: 

  • In-person accessibility information
  • Accessibility feedback for the website
  • Accommodations for public events
  • Requests for access to content in alternate formats

This structure allows the website to grow naturally. When a section becomes too long, top-level headings can be easily split off into subpages.