Martin,
Interesting ..
The references you give are in documents labeled "Working Draft", so I'd
be looking to see more definitive versions of those pages. In addition,
the issues are for accessibility and screen readers (i.e. WAI-ARIA),
which tend to have more strict requirements than plain HTML5.
-- Jon
On 1/25/19 1:41 AM, Martin Desruisseaux wrote:
Hello Jonathan. Thanks for all this work. I was wondering if the use
of <h1>, <h2>, etc. nested inside <section> has been considered for
simplifying the heading ranks? If I understood [1] and [2] correctly,
the following are semantically identical in HTML5:
<h1>XXX</h1>
<section>
<h2>YYY</h2>
<section>
<h3>ZZZ</h3>
and
<h1>XXX</h1>
<section>
<h1>YYY</h1>
<section>
<h1>ZZZ</h1>
Wouldn't the use of <section> allows to reset the <h#> counting to 1
for that section, which would free the developer to care about what
was the rank of last <h#> element? If each field and method is in its
own <section>, wouldn't it allow developers to use <h1>, <h2>, etc. in
their javadoc for each field/method?
Martin
[1]https://www.w3.org/TR/2011/WD-html5-author-20110809/headings-and-sections.html#headings-and-sections
[2]https://www.w3.org/TR/2011/WD-html5-author-20110809/the-h1-h2-h3-h4-h5-and-h6-elements.html#rank
