Headings

Overview

Screen readers can jump between headings and view an outline of the document structure. Proper heading hierarchy makes this possible and ensures all users can navigate effectively.

Why this matters

Headings do more than organize your page visually—they create a navigable document structure that assistive technology users depend on. When you use proper heading markup:

• Screen readers can announce the heading structure, allowing users to understand page organization at a glance
• Users can jump between headings to navigate quickly rather than listening to or reading through entire pages linearly
• Users with cognitive disabilities can better understand the relationship between sections
• Search engines can better understand your content and prioritize key sections

Without proper headings, assistive technology users must navigate through all content sequentially, making pages frustrating and time-consuming to use. Visual styling alone—using bold text or larger fonts—provides no structure that assistive technologies can recognize.

Techniques

HTML Headings

Use heading tags in HTML to structure web content. There should be only one H1 (usually the main page heading). Use H2 for major sections, H3 for subsections, and so on. Do not skip heading levels. The website name or branding typically does not need a heading tag.

• H1: Main page heading (usually one per page)
• H2: Major section headings
• H3-H6: Subsection headings as needed
• Never skip levels: Do not jump from H1 directly to H3

UGA CMS Headings

The UGA content management system is built on WordPress. Use the format selector in the rich text editor to apply heading styles. The CMS reserves H1 for the page title, so begin with H2 for your content headings.

For questions about heading structure in the CMS, contact the Digital Accessibility Services (DASH) Team or EITS Web Services.

Word Headings

In Microsoft Word, use the built-in heading styles from the Ribbon. Select text and apply a style such as Heading 1, Heading 2, etc. You can also right-click a heading style to customize its appearance.

PDF Headings

If your PDF was created from a tool that supports heading markup (such as Word or InDesign) and exported as a tagged PDF, the heading structure should be preserved. You can check and edit heading structure in Adobe Acrobat Pro DC:

• Using the Tag Tree: Go to View > Show/Hide > Navigation Panes > Tags to review the document structure and heading levels
• Using the Reading Order Tool: From the Accessibility Panel, launch the Reading Order tool. Select text and apply heading tags. Save often and keep multiple versions as a backup

For help with PDF headings, contact [email protected].

Google Docs Headings

Google Docs has a Styles selector on the toolbar. Use it to apply heading formats. UGA has Google Workspace for Education, so you can use these features in your UGA Google account.

eLC Headings

In eLC course pages, use the formatting toolbar in the content editor to apply heading styles. eLC uses H1 for the page title, so start with H2 for your content sections. Use H3 and H4 for subsections as needed. Never skip heading levels.

Common mistakes

• Skipping heading levels: Jumping from H1 to H3 or H2 to H4 breaks the logical hierarchy that assistive technologies rely on. Always use sequential levels.
• Using headings for visual styling only: Applying a heading style to text just to make it larger or bold, without it being a true section heading, confuses assistive technology users.
• Using bold text instead of headings: Bold text is visual styling, not structural markup. Screen readers won’t recognize it as a section boundary.
• Multiple H1 elements on one page: Each page should have one primary H1. Using multiple H1s confuses the document structure.
• Empty headings: Headings with no text content provide no value and may confuse users navigating by headings.
• Overly long headings: Keep headings concise and descriptive. Long, complicated headings are harder to navigate and remember.

WCAG Criteria

• WCAG 2.1 Level A: 1.3.1 Info and Relationships – Content structure and relationships must be programmatically determinable, including heading hierarchy
• WCAG 2.1 Level AA: 2.4.6 Headings and Labels – Headings and labels must describe the topic or purpose of content

Getting help

If you have questions or need assistance, the Digital Accessibility Services Hub (DASH) is available to support colleges, schools, and administrative units as they build sustainable accessibility practices.

• Contact DASH at [email protected] for consultations, training, or technical assistance.

Accessibility is a shared responsibility, and every step you take makes UGA’s digital environment more inclusive.