W3C home > Mailing lists > Public > public-html@w3.org > May 2014

Re: should HTML have a <heading> element?

From: Reinier Kaper <rp.kaper@gmail.com>
Date: Fri, 9 May 2014 09:29:03 -0400
Message-ID: <CAAz96Ot04BeKvPoS2DHYrvgRGuz5OWi_kbEXN0QM=u0=3iEx6Q@mail.gmail.com>
To: "public-html@w3.org" <public-html@w3.org>
I feel this:

conversely:
<body>
<section />
<section />
<section />
<section />
<section />
<section />
<h1>

Is a terrible way of handling headings by the algorithm.
If anything, that last heading should be an <h1>, or an <h2> (with a
missing <h1> at the top).
Sections are just that, sections, but the <h1> is a direct descendant of
the body. Headings inside the sections are not and are therefore
sub-headings in the document outline (or should be).

I'm very much in favour of a <heading> (and <subheading>) element and let
the algorithm decide the best structure.

Right now I have to resort to all <h1>'s in every sectioning element, as I
work in a CMS and one of the downsides is that blocks in a CMS can be
re-used in different place / contexts. Example: an <aside> in the main
content has a different meaning than an <aside> in a sidebar, but they can
still be the same element. Falling back to an <h1> inside the <aside>
prevents broken outlines in different contexts for me.

TL;DR: current headings (<h1> - <h6>) are a legacy from when web was not
much more then digital print. Let's move forward and be more generic and
dynamic about it.


On 9 May 2014 06:08, Detlev Fischer <fischer@dias.de> wrote:

> If the aim is to keep things as simple as possible, wouldn't it be better
> toleave it to authors to do one of the following:
>
> * (A) use the outline algorithm with section and h1-h6 (e.g. for cases
> where content segments are aggregated in a number of different places and
> the definitive correct heading level cannot be hard-coded in the segment
> itself)
> * (B) use div instead of section and keep using h1-h6 as before
>
> Having both heading and h1-h6 in the same document seems a bit confusing -
> if <heading> would indeed be dynamically populated with a level via the
> outline algorithm, authors would have no way to ensure consistency with
> other hard-coded h1-h6 headings used in the same document.
>
> But maybe I misunderstood..
>
> --
> ---------------------------------------------------------------
> Detlev Fischer PhD
> DIAS GmbH - Daten, Informationssysteme und Analysen im Sozialen
> Geschäftsführung: Thomas Lilienthal, Michael Zapp
>
> Telefon: +49-40-43 18 75-25
> Mobile: +49-157 7-170 73 84
> Fax: +49-40-43 18 75-19
> E-Mail: fischer@dias.de
>
> Anschrift: Schulterblatt 36, D-20357 Hamburg
> Amtsgericht Hamburg HRB 58 167
> Geschäftsführer: Thomas Lilienthal, Michael Zapp
> ---------------------------------------------------------------
>
>
>
Received on Friday, 9 May 2014 13:29:36 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:39 UTC