About h1

[fiatjaf]

See Headings And Accessibility on The Importance Of HTML5 Sectioning Elements.

Ignoring the discussion about our need to use only h1 (yes, we should be using only h1), there's something on this pure semantic thing and the importance of sectioning elements that Marx is overlooking: browsers are already styling headers differently according to the section they belong to.

Marx, however, forces all headers, independent of their section, to be of the same size.

[samwilson]

(Do you mean "use only one h1"?)

Headings currently do decrease in size as they go down in importance. Not by a huge amount, but it's quite noticible in many situations.

[fiatjaf]

no, I meant use only h1, not h2 or h3 or any h.

[samwilson]

ah right, that makes sense: because the hierarchy is provided by nesting <section> elements, is that it? It would be possible to style it so that one could do both (either nest sections, or use h1, h2, h3, ...).

[fiatjaf]

Well, probably with something like section h1, header h1, section header h1, article h1. I don't know. We should see how Chrome styles it in its default stylesheet.

[ricklancee]

yes, we should be using only h1

No, we shouldn't. See the spec:

There are currently no known implementations of the outline algorithm in graphical browsers or assistive technology user agents, although the algorithm is implemented in other software such as conformance checkers. Therefore the outline algorithm cannot be relied upon to convey document structure to users. Authors are advised to use heading rank (h1-h6) to convey document structure.
http://www.w3.org/TR/html5/sections.html#outlines

It is currently discouraged to use only h1. Stick to one h1, then use h2-h6s.
Note: it's currently discouraged, this might change in the future.