[Bug 25003] modify required heading mappings to reflect reality

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003

--- Comment #28 from Marco Zehe <mzehe@mozilla.com> ---
(In reply to alexander surkov from comment #27)
> I find the suggestion reasonable, alternatively section element could have
> @heading attribute.

The problem with that is that section is acontainer, and heading can also
become one if it contains formattings like "strong" or such. We wouldn't want
to take that away from web developers. So I proposed a stand-alone new element
instead of an attribute.

> It doesn't address the relation between h1-h6 and section elements though.

That's why I wrote:

> > 1. Leave h1 to h6 alone as they always were. h1 through h6 are always that
> > regardless of what they are nested in.

So even if h1 through h6 are nested within section elements, they will always
be h1 through h6 for screen readers and not participate in any outline
algorithm calculation. Clean separation between the "old" way (h1 through h6
usage, manual outline by the author), and the "new" way (section + new heading
element, levels calculated by user agent).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 23 April 2014 07:24:07 UTC