Functionality

Headings are

  • shown on the page
  • read by screen readers and required for orientation and navigation
  • in the web page markup they are the "h1" down to "h6" within the "body".

Page title

screenshot

Each page has a main heading.

Headings

screenshot

Each block of content is introduced by a heading. Ensure headings follow an appropriate hierarchical structure.

What to check for

  • Each page has a main heading.
  • All text that looks like a heading is marked up as a heading.
  • All text that is marked up as a heading is really a conceptual section heading.
  • Each block of content is introduced by a heading.
  • The heading hierarchy is meaningful. Ideally the page starts with an 'h1' – which is usually similar to the page title – and does not skip levels. The resulting tree structure reflects the meaning and dependencies of the page sections.

How to check

Editors can use in AEM the “page headline structure viewer”

Tip

Meaningful headings which contain the keywords a user would use when searching for your content have a big impact on page ranking in search engine results.

System provides good defaults
The system provides already good defaults and that editors can rely upon them.
Editor fine tune
A fine tuning is necessary and that the proposed checkpoints need manual verification.

Crosslinks

Reference for publisher

AEM Headlines

An expandable overlay is displayed as part of the side panel, which illustrates the structure of all visible page headlines created on a page.

Publishers can see the headline structure of the content they create in order to verify that the structure is good and correct in regards to accessibility.

screenshot

The title of the components link list, table, text with image and teaser can have different styles and still retain the "H2" code.

screenshot

Styling options in RTE for headline (H3)

What to avoid

  • Do not use bold formatting for a title!
  • Do not use empty titles!