Good point! We've adjusted the plan so that it's 100% of beta (starting today). Thanks.

TFA has been fixed to make this clearer. Thanks!

They do if you include <meta name="color-scheme" content="light dark">

Also see https://github.com/whatwg/html/issues/5426

There is no warning in that case.

It is a shame the article did not explain that.

Nested lists have 0 block-margin and different list-style-type. But that seems to be about it...

The article says

> Do not rely on default browser styles for conveying a heading hierarchy. Explicitly define your document hierarchy using <h2> for second-level headings, <h3> for third-level, etc.

The argument I was making was what is why would

    <main>
    
    <h1>Main Heading</h1>

    section..h2... Etc

    </main>
    
    <aside>
    
    <h1>Aside heading</h1>

    section...h2...

    </aside>

Be incorrect? The original html standard clearly stated this was acceptable but now there should only be a single H1 which is the page heading and all other headings should be H2 and lower. What if the page content doesn't actually have a single main heading? This change fundamentally changes the semantics of something which has had unclear semantics for decades and which actually rendered what I typed above correctly in the past. Now it would not be rendered correctly anymore.

The spec allows multiple top-level headings: https://html.spec.whatwg.org/multipage/sections.html#heading...

It only worked visually. For screen reader users, all headings are level 1. If you switch to using h2 etc, it will be more accessible.

That's a problem with the screen reader implementation. At least, according to the previous semantics.

It was a problem with the screen reader implementation in 2009 when the semantics were introduced.

In 2025 if no screen reader works right it's a problem with the spec.

As of 2022 (when the outline algorithm was removed from the spec), it's a problem with your website implementation.

What is your bug?

Someone has to be first. :-)

There's a new proposal to address this: https://github.com/whatwg/html/issues/5033