This is a DRAFT resource that supports Working Drafts of WCAG 3. Content in this resource is not mature and should not be considered authoritative. It may be changed, replaced or removed at any time.


🔙 WCAG 3.0 (Silver) Guidelines (Structured content)

Method: Headings in HTML


  • Documents such as PDF, word processing documents, ePub, and slideware.
  • Web-based languages such as HTML, and ARIA.
  • Platforms such as iOS, and Android.




Assistive Technologies like screen readers rely on semantics in the code to properly help their users understand and navigate the material. For example, screen reader users can bring up a list of headings on the page to browse and navigate to the material they want without having to listen to everything.

How it solves user need

Properly coded headings allow assistive technology users to understand the hierarchy of content and navigate to the section most likely to have the material of interest.


Updated: 11 May 2020 to illustrate new architecture proposal.

Change Log

  • 11 May 2020 (changes for new architecture proposal)
  • 19 March 2020 (first draft)
Back to Top