Heading Structure Available
Group: layout • Guideline: structure
Summary in Plain English
Meaningful blocks of content are organised under a logical hierarchy of headings, where the technology supports heading levels.
Why It Matters
Headings are the primary way screen reader users navigate a long page; a flat or scrambled hierarchy removes that route entirely.
Scope: When This Applies
The draft's own conditions, quoted from guidelines/groups/layout/structure/heading-structure-available.md.
Except when
- The technology does not support heading levels.
Test Procedure from the W3C Draft
Quoted from the provision's informative document, informative/guidelines/layout/structure/heading-structure-available.md. It is the group's own procedure, not an editorial testing guide.
Headings set at right level
Procedure
For the hierarchy of headings:
- Check that headings for sibling content blocks have the same heading level.
- Check that headings for immediate child content blocks are at most one level higher than parent content blocks.
Expected results
- #1 and #2 are true.
HTML heading levels not skipped
Procedure
For each page/view:
- Review the hierarchy of headings.
- Check that each heading level is at most one numerical level higher than the preceding heading.
Expected results
- #2 is true.
W3C Working Group Status
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
4 GitHub threads carrying 9 comments, fetched from w3c/wcag3 by the tracker. Titles, numbers and states are the threads' own.
What the Argument Is About
Whether the provision should police how headings look as well as how they are marked up, and what the heading hierarchy has to be for content that does not naturally have one.
Positions taken in the thread
Questions whether there is a requirement for headings to be visually distinct at all, since headings that are not distinct for anyone are not obviously an accessibility question. Accepts differentiating font from typeface as long as the result is programmatically different. Pushes back on the suggestion that sufficient semantics on headings matters more than visual presentation, reading "sufficient semantics" as "sufficient meaning" and suggesting, with the hedge "(I donโt think)", that WCAG cannot require authors who write meaningless headings to rewrite them, while asking whether WilcoFiers meant something different.
Holds that content structure for a good visual hierarchy matters for COGA among others, and that it is simultaneously a contrast question: padding around a heading, leading and letter spacing all change perceived contrast, as does font weight. Argues weight is the most critical spatial quality because it sets the spatial frequency that drives contrast sensitivity, illustrated with same-color samples at different weights placed on the contrast sensitivity curve. Also warns that the CSS font-size metric is close to futile as an absolute, since size and weight vary massively between families.
Wants existing sufficiently distinct methods catalogued so a requirement does not accidentally remove one, and stresses that combinations of distinctions matter. Proposes four groups rather than Myndex's three: spatial, visual text attributes, content, and external indicators, with capitalization, writing system, sentence type and person placed under content. Argues writing system in particular belongs with content, since writing in sitelen pona carries semantics and nuance that Latin script or speech does not.
Filed #81 on behalf of a commenter who wrote to public-agwg-comments; the submitted comment asks for an outcome stating that section heading levels be semantically nested so they form a hierarchical outline of the content, and that there be only one h1 per page, reserved for introducing the main content or topic and matching or closely resembling the page title. No one has replied since May 2024.
Opened #478 asking that "higher" and "lower" be replaced when referring to heading levels, since which direction each word points is ambiguous. Also wants "meaningful block of content" clearly defined and exceptions specified, recognising that paragraphs, letters and emails may not require headings, while insisting any exception be explicit enough that it cannot be used as a loophole. Notes both items may resolve from a single consistent definition.
Agreed
- Font and typeface have to be kept distinct in the spec's language. WilcoFiers's example, that Helvetica 12pt bold and Helvetica italic 14px are different fonts sharing one typeface, drew no objection.
- A heading being larger than the body text is a valid distinction even though an absolute font size is not. u9000-Nine proposed the split and Myndex agreed size is and should remain a distinguishing feature.
- Color should not be the sole distinguisher. u9000-Nine is willing not to count it; Myndex agrees it must be an accompaniment rather than the solo distinction, given how far color perception varies with context even for standard vision.
Still open
- How to decide whether headings are sufficiently distinct from each other and from surrounding content, whether color contrast can carry that judgement, and whether reading distance should be a factor. WilcoFiers asked all three in #19 in 2023 and none has been answered.
- Whether sufficient semantics on headings matters more than visual distinctness, and whether the visual requirement should simply be that presentation changes away from the default. WilcoFiers raised it, GreggVan contested what it would even mean, and it stalled there.
- Whether heading levels must be semantically nested and limited to one h1 per page (a public-agwg-comments submission filed by rachaelbradley as #81), which has had no discussion at all.
- How "meaningful block of content" is defined and which content types are exempt from needing headings (giacomo-petri, #478) - a definition shared with the Blocks of content available (minimum) provision.
- Where text decoration belongs. u9000-Nine asked why it sits in both the layout and non-text groups; Myndex left it unresolved, leaning non-text when it signals function and layout when it is merely divisional.
Note
Only one of the four threads has any discussion. All nine comments come from #19, which is labelled for this provision and for Blocks of content available (minimum), and is mostly a two-person taxonomy exchange between Myndex and u9000-Nine. #81, #271 and #478 are issue bodies with no replies: #271 is alastc's requirement-tracking issue listing Visually organize content, Regions (Minimum and Enhanced), Section Label, Headings Structure and Programmatic Relationship under one guideline, rather than an argued position.
- #19 Create Structured Content guideline open 9 comments · updated 2026-04-20
- #81 Section heading levels should be semantically nested open 0 comments · updated 2026-04-16
- #271 Requirements: Section labels open 0 comments · updated 2026-04-02
- #478 Heading structure - Clarifying terminology and exceptions open 0 comments · updated 2026-03-29
WCAG 2.2 Criteria That Map Here
From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is an interpretation, not a W3C mapping: W3C has not published one yet.
W3C Raw Source Text
Verbatim from guidelines/groups/layout/structure/heading-structure-available.md · informative document: informative/guidelines/layout/structure/heading-structure-available.md
Meaningful blocks of content are organized with a logical hierarchy of headings. :::except-when * The technology does not support heading levels. :::