implement headingoffset & headingreset attributes

[keithamus]

This specifies the headingoffset and headingstart attributes as proposed in #5033.

• At least two implementers are interested (and none opposed):
  • Chromium: Actively prototyping.
  • …
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chromium: …
  • Gecko: …
  • WebKit: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
• Corresponding HTML AAM & ARIA in HTML issues & PRs:
• MDN issue is filed: …
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/dom.html ( diff )
/index.html ( diff )
/sections.html ( diff )

[scottaohara]

thank you for working on this.

aside from the comments i left in my quick review, does it make sense to explicitly call out as a note that aria-level is not considered/taken into account with these attributes?

from re-reading the issue this stems from, i'm assuming people are likely thinking that if someone declares an aria-level on a heading, the value of that attribute is what the heading level will be exposed as, yes?

Or to be very clear, do people agree with the following:

<div headingoffset=1>
  <h1 aria-level=4> level 4 </h1>
  <h1> level 2 </h1>
  <h1 headingoffset=20 headingreset aria-level=3><!-- 3 --></h1>
</div>

if HTML doesn't have a note for this, then we can get it into html aam, aria in html, or both - and i'd assume MDN author guidance.

[domenic]

I haven't looked at the PR text itself yet, but I think such a note/example would be valuable.

[keithamus]

I've added a note mentioning aria-level as well as an example demonstrating their combinations.