<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
As someone coding websites in a university setting, I find the idea of <section> interesting but its corollary of restarting a heading hierarchy confusing. All existing UAs including AT expect a document to be hierarchical and <section> is not somehow a new
form of object or <iframe> where <i>every</i> hierarchy starts over from the top.
<div><br>
</div>
<div><section> and <article> exist to make portions of a webpage easier to be consumed as semantic blocks. The problem here is that the spec wants the blocks to be autonomous while remaining part of the greater whole. </div>
<div><br>
</div>
<div>Let's compromise. <section data-headerstart="3"> could inform a syndicator that outside the flow of the containing document, <h3> is functionally the top-level header, <h4> is <h2>, etc. This puts metadata where it belongs, and leaves authoring the rest
of the document without problems.</div>
</body>
</html>