# Consider using the “h1” element as a top-level heading only — or else use the “headingoffset” attribute (otherwise, all “h1” elements are treated as top-level headings by many screen readers and other tools). > Canonical HTML version: https://rocketvalidator.com/html-validation/consider-using-the-h1-element-as-a-top-level-heading-only-or-else-use-the-headingoffset-attribute-otherwise-all-h1-elements-are-treated-as-top-level-headings-by-many-screen-readers-and-other-tools > Attribution: Rocket Validator (https://rocketvalidator.com) > License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Multiple `h1` elements on a page can confuse screen readers and other assistive tools, which treat every `h1` as the top-level heading. HTML headings (`h1` through `h6`) form an outline of your document. The `h1` element represents the highest-level heading, and most accessibility guidelines recommend using only one `h1` per page. When screen readers encounter multiple `h1` elements, they may present them all as equally important top-level sections, making it harder for users to understand the page structure. Instead of using multiple `h1` elements, use a proper heading hierarchy. Start with a single `h1` for the main topic of the page, then use `h2` for major sections, `h3` for subsections, and so on. This creates a clear, navigable document outline. The W3C warning also mentions a `headingoffset` attribute, which is a proposed feature for `

` elements that would allow automatic heading level adjustment. However, this attribute is **not yet implemented in any browser**, so you should not rely on it. ## Example with the issue ```html

My Website

About Us

Some content here.

Contact

My Website

About Us

Some content here.