Headings remain one of the primary means of navigation for users of assistive technologies.
section should have a numbered heading (e.g.,
h1) that reflects its level
in the document hierarchy, as numbered headings allow assistive technologies, regardless of their support
for HTML5, to navigate the document structure.
Each heading element must represent a single heading. Do not break a heading up into separate tags for
visual formatting. If you need to include subheadings, incorporate them into the main heading or include
them in a subsequent paragraph, using a
header tag to encapsulate the full heading (Example 2 shows both usage examples).
If a section of text does not have a heading, include a heading in an
aria-label attribute on
the enclosing element. Assistive technologies will announce this label and alert users that a new section
Do not use heading elements within
blockquote and other HTML5
sectioning root elements. Although these features may have titles, using heading elements will force
users to navigate through them to find the next section.
Reading systems and assistive technologies do not support the outline algorithm defined in HTML5.
If you use an
h1 heading for every section, they will all appear as top-level
headings to a user, impeding their ability to navigate.