发表新帖
发表新帖

How to properly use h1 in HTML5

前端 未结
关注
3 1899
爱一瞬间的悲伤
爱一瞬间的悲伤 2020-11-28 23:25

Which of the following is the correct way to structure a page:

1) h1 only in header


    <
相关标签:
3条回答
  • 闹比i
    2020-11-28 23:58

    As I state in my comment and you quote in the W3C, h1 is a heading and not a title. Each sectioning element can have its own heading element(s). You cannot think of h1 as being the title of a page only but as the heading of that particular section of the page. Just like the front page of a newspaper, each article can have its own heading (or title).

    Here is a good article on this.

    0 讨论(0)
  • 臣服心动
    2020-11-29 00:16

    I would recommend using h1 throughout. Forget about h2 through h6.

    Back in HTML4, the 6 heading levels were used to implicitly define the sections. For example,

    <body>
<h1>This is a top-level heading</h1>
<p>some content here</p>
<h2>This is the heading of a subsection</h2>
<p>content in the subsection</p>
<h2>Another subsection begins here</h2>
<p>content</p>
<h1>another top-level heading</h1>

    Now with the section element, you can explicitly define the sections rather than having to rely on the implicit sections created by your browser reading the different heading levels. A browser equipped with HTML5 knows that everything inside a section element gets "demoted" by one level in the doc outline. So for example a section > h1 is semantically treated like an h2, a section > section > h1 is like an h3, etc.

    What's confusing is that browsers STILL create implicit sections based on the h2–h6 heading levels, yet the h2–h6 elements don't change their styles. That means that an h2, no matter how many sections it is nested in, will still appear like an h2 (at least in Webkit). This would be confusing if your h2 was supposed to be, say, a level-4 heading.

    Mixing h2–h6 with section leads to very unexpected results. Just stick with h1 only, and use section to create explicit sections.

    <body>
<!-- optional --><header>
    <h1>This is a top-level heading</h1>
    <p>you may optionally wrap this p and the h1 above it inside a header element.
     the header element doesn't affect the doc outline.
     the section element does, however.</p>
<!-- optional --></header>
<section>
    <h1>even though this is an h1, the browser "treats it" like an h2
        because it's inside an explicit section.
        (it got demoted).</h1>
    <p>content in the subsection</p>
</section>
<section>
    <h1>Another subsection begins here, also treated like an h2</h1>
    <p>content</p>
    <h2>This is misleading. it is semantically treated like an h3.</h2>
    <p>that is because after an h1, an h2 is demoted one level. the h1 above is
        already a "level 2" heading, so this h2 becomes a "level 3" heading.</p>
    <section>
        <h1>just do this instead.</h1>
        <p>it is treated like an h3 because it's in a section within a section.
            (It got demoted twice.)</p>
    </section>
</section>
<h1>another top-level heading</h1>

    Furthermore, you may use the <main> element. This element contains only information specific to the page, and should not include content that is repeated site-wide, such as navigation links, site headers/footers, etc. There may be only one <main> element present in the <body>. So your solution may be as simple as this:

    <header>
    <h1>Site title</h1>
    <nav>...</nav>
</header>
<main>
    <h1>Page title</h1>
    <p>page content</p>
</main>
    0 讨论(0)
  • 长情又很酷
    2020-11-29 00:17

    However, don't forget accessibility concerns. According to MDN, "there are currently no known implementations of the outline algorithm in graphical browsers or assistive technology user agents." That means that a screen reader might not be able to figure out the relative importance of sections with only <h1>. It might need more heading levels, such as <h2> and <h3>.

    0 讨论(0)
 看不清?
提交回复
热议问题