{"id":358,"date":"2021-03-21T15:01:53","date_gmt":"2021-03-21T15:01:53","guid":{"rendered":"https:\/\/html5accessibility.com\/stuff\/?p=358"},"modified":"2021-03-21T15:01:53","modified_gmt":"2021-03-21T15:01:53","slug":"a-decade-a-year-of-heading-backwards","status":"publish","type":"post","link":"https:\/\/html5accessibility.com\/stuff\/2021\/03\/21\/a-decade-a-year-of-heading-backwards\/","title":{"rendered":"A decade + a year of heading backwards"},"content":{"rendered":"

\"Patrick<\/p>\n

Originally published February 2020<\/a>, updated today.<\/p>\n

It’s actually been longer (I remember being introduced to the outline algorithm in 2007<\/a>), but 11 years<\/strong> is a number worth signifying.<\/p>\n

In 2020<\/del> 2021<\/strong> as it was in 2010 the HTML specification<\/a> defines an outline algorithm and specifies how it affects heading rank regardless of the hard coded heading level h1...h6<\/code> and how <hgroup><\/code> automagically<\/em> transforms multiple headings into a single heading.<\/p>\n

Problem is that its never been implemented, as a consequence developers taking the specification as the truth, have been and continue to be misled. The reality of this fantasy has been burned into many books on HTML<\/a> and articles over the last decade. The disconnection between implementation reality and HTML specification has been raised many a time<\/a>. This was in the past partially mitigated by the the HTML5 specification (2014), which initially warned of the disconnect<\/a> and later modified the definitions<\/a> of the various elements effected by the non existent outline algorithm and obsoleted the hgroup<\/code> element (as it does nothing apart from provide a hook for developers to hang CSS styles off), so that they aligned with a (less) desirable but actual implementation of the semantics of headings and sectioning elements. This included updating the code examples to reflect that <h1><\/code> elements are semantically heading level 1<\/strong> elements regardless of what they are nested in.<\/p>\n

There has been ongoing discussions with the current keepers of the HTML specification, but as such discussions do, have dragged on for years. This is not uncommon or sometimes undesirable, but what is uncommon and undesirable is that important information used by developers and expected to have a passing relationship to reality, does not and has not aligned with implementations for 10 years or so.<\/p>\n

10 years + 1, no change<\/h2>\n

Good news was that there appeared to be movement at the station<\/a> and the HTML specification may sometime<\/em> soonish reflect reality. The question is still 10 years + 1:<\/p>\n

Why is it OK to have a substantial set of authoritative semantic HTML definitions misdirect developers for so long?<\/strong><\/p>\n

And then there is the question What do we do with <hgroup><\/code>?<\/a><\/p>\n

New PR – Obsolete <hgroup> <\/a>#6462 by SideShowBarker<\/a><\/p>\n

Further Reading<\/h2>\n