A page can look perfectly organized to a sighted visitor and still be difficult to navigate with a screen reader. That is why all headings are not equal in ADA compliance: the visual appearance of a heading is only one part of the requirement. The HTML element, its level, its wording, and its position in the document structure all affect whether users can understand and move through the page efficiently.

For WordPress site owners, this is not a minor formatting concern. Heading errors can affect course pages, government notices, service information, blog posts, forms, product content, and PDFs embedded or linked from the site. They also create a recurring compliance risk when editors rely on visual styling rather than semantic structure.

All Headings Are Not Equal in ADA Compliance

The Americans with Disabilities Act does not provide a numbered rule stating that every webpage must use a specific sequence of heading tags. In practice, however, ADA accessibility obligations are commonly evaluated against the Web Content Accessibility Guidelines, including WCAG 2.1 and WCAG 2.2. Under WCAG, headings help satisfy requirements related to information, relationships, headings and labels, and content structure.

A heading has two jobs. It tells visual users what the next section is about, and it gives assistive technology users a navigational landmark. Screen reader users often open a list of headings and jump directly to the section they need. If the page uses bold paragraphs, oversized text, or styled links in place of real heading elements, that navigation method breaks down.

A large blue sentence is not automatically a heading. A real heading is defined in the page markup with an `

` through `

` element. Likewise, placing every section title in an `

` may be technically better than using plain text, but it still may not communicate the actual relationship among the sections.

What Makes One Heading Different From Another

Heading levels indicate hierarchy, not font size or visual emphasis. An `

` identifies the main topic of the page. An `

` introduces a major section within that topic. An `

` introduces a subsection under the relevant `

`, and the pattern continues only when the content truly needs a deeper level.

Consider a city department page titled “Residential Permit Applications.” That page title should generally be the `

`. Sections such as “Eligibility,” “Required Documents,” and “Application Fees” would usually be `

` headings. If “Required Documents” contains separate categories for homeowners and contractors, those labels may be `

` headings.

The distinction matters because screen reader users do not receive the visual cues created by whitespace, columns, borders, or color alone. They rely on the programmatic outline to understand whether “Application Fees” is a peer of “Eligibility” or a detail within it.

An H1 Is Not Just a Bigger H2

Most pages should have one clear, descriptive `

` that identifies the primary subject. Templates sometimes create exceptions, particularly on complex application interfaces or pages with embedded content. But for standard WordPress pages and posts, a single page-level H1 is the most dependable approach.

Multiple H1 headings are not automatically an ADA violation. Modern HTML can support more complex document structures. Still, multiple top-level headings can confuse content teams, weaken a consistent editorial workflow, and make automated findings harder to interpret. The operational question is simple: can a visitor using a screen reader immediately identify the page’s purpose and the structure beneath it? If the answer is uncertain, use one primary H1.

Skipped Levels Need Context

A heading order such as H1 followed directly by H3 is often flagged because it may suggest that a section level was skipped. In many cases, that finding points to a real structural problem. A user who hears an H3 after an H1 may reasonably expect a missing H2 section.

However, a skipped heading level is not always a standalone WCAG failure. The full context matters. Some templates use components that create complicated structures, and headings may appear in shared page regions such as navigation, sidebars, or footers. The objective is not to satisfy an outline checker at the expense of meaningful content. The objective is a logical, understandable hierarchy.

Treat skipped levels as a remediation priority that requires review. Confirm that the heading accurately represents a subsection, that no heading was used only to achieve a visual style, and that the content can be navigated in a sensible order.

Common WordPress Heading Failures

WordPress makes it easy to choose heading levels in the block editor, but that convenience does not prevent publishing mistakes. The most common issue is using a Heading block because it looks right rather than because the text introduces a section. A callout such as “Call Us Today” may look prominent, for example, but it is not necessarily a heading for the content that follows.

Another frequent problem occurs when authors begin a page with an H2 because the theme already displays a page title. If the visible title is properly marked up as an H1 by the theme, starting the content body with an H2 is usually appropriate. If the theme displays the title only as a styled `