Before reading a long page, people often scan its headings. They are looking for the shape of the argument and a place to begin. Assistive tools can use the same structure to help readers move between sections.

A heading should name the section that follows it. Its level describes the relationship between sections, while its appearance can be designed separately. Making a sentence large does not automatically give it a useful structural role.

Read the headings of a page without its paragraphs. If they tell a coherent story, the structure is doing helpful work. If every heading says something vague, revise the labels before adding another visual flourish.

Imagine a practical setting.

Imagine scanning a guide before reading it closely. Headings that name the actual questions let you choose the section that matters to your task.

Before the next experiment.

An ordinary visit includes arriving, reading, acting, and leaving. Review the connections between those moments, rather than judging only the most polished screen.
A few starting points
  1. Read the headings as an outline.
  2. Name the content of each section.
  3. Keep structure separate from appearance.

Follow a related question

Connect the permission to an app feature.

Permissions should have a purpose

Distinguish active work from saved references.

A calmer browser

Keep learning

Related background to continue exploring this subject.

MDN: learn web development MDN: how the web works
Explore a possibility