# Heading

### Introduction

Upon visiting a web page for the first time, a sighted user will typically scan the headings of the page to create a visual model of its content. On subsequent visits to the page, the user recollects this visual model.

A non-sighted user will typically want to do exactly the same, using their screen reader to scan for headings to create a mental model.

### Working Examples

*The content for this section is not yet available, please check back again for updates.*

### Best Practices

Every page **must** have a single H1 heading.

The H1 heading **should** describe the content and purpose of the page.

The H1 heading does *not* need to be the first heading in the page.

Every page region requires a single H2 heading. This heading describes the content and purpose of the region. It is good practice to wrap every page region in a div or section tag.

Every page region can contain multiple H3 - H6 headings, but they *must* be placed in the markup in strict hierarchical order.

### Interaction Design

This section provides interaction design for keyboard, screen reader and pointing devices.

#### Keyboard

Headings are not interactive elements and therefore have no keyboard interaction.

**NOTE**: headings can *contain* links, which *are* interactive elements.

#### Screen Reader

Screen reader will identify heading by it's level, e.g. 1 to 6.

#### Pointer

Headings are not interactive elements and therefore have no pointer interaction.

A heading may give the illusion of being an interactive element if it contains a link, or is wrapped in a link, but the heading element itself is not clickable.

### Developer Guide

*The content for this section is not yet available, please check back again for updates.*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ebay.gitbook.io/mindpatterns/structure/heading.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.