Loading

Accessibility: Understanding the Use of Multiple H1 Headings on the Salesforce Platform

Veröffentlichungsdatum: May 1, 2026
Beschreibung

Salesforce platform

On Salesforce platform pages, there are typically two <h1> headings:

  1. Banner Navigation Section: Displays the app name, such as "Service Console".
  2. Main Content Area: Displays the record name and object, such as "Contact Astro".

This layout ensures that each region of the page is clearly labeled, providing context and structure to all users, including those relying on assistive technologies.

Experience Cloud Sites

The same principle applies to Salesforce Experience Sites, including pages with record lists. While having a single <h1> per page is generally considered a best practice, multiple <h1> headings are acceptable when each heading clearly defines the purpose of its respective section. 
Lösung

Salesforce intentionally uses multiple <h1> elements on a page to clearly label each major region, such as the banner navigation and the main content area. This design choice supports efficient screen reader navigation by providing a distinct landmark heading for each section, without violating WCAG requirements. The HTML specification and WCAG both permit multiple <h1> elements provided each one meaningfully describes its section.

 

This behavior complies with WCAG 2.4.6:

  • Contextual Clarity: Each <h1> heading represents the main purpose of its respective section.
  • Enhanced Navigation: Screen reader users can quickly identify and navigate to specific sections.
  • Compliance: WCAG does not limit <h1> to a single instance per page but emphasizes logical structure and meaning.

By design, this structure improves accessibility and functionality.

Zusätzliche Ressourcen

The following resources provide additional context on WCAG heading requirements and accessible page structure:

Nummer des Knowledge-Artikels

004141331

 
Laden
Salesforce Help | Article