@alfonsoml yeah, it'll depend on how the tool gets its information. If it's reading the DOM itself, then it'll get the wrong answer, but these tools tend to read the a11y tree, and we expose the correct level there when you use headingoffset.

@noleli @mdekstrand and it starts with saying it's only currently in Firefox Nightly, behind a flag.

@alfonsoml accessibility should be for people

@codingjoe pretty much! Here's the algorithm https://html.spec.whatwg.org/multipage/sections.html#get-an-element's-computed-heading-level

@tommi it should just work in those cases, no?

@chriskirknielsen here's the algorithm in the spec https://html.spec.whatwg.org/multipage/sections.html#get-an-element's-computed-heading-level

@timsev headingoffset can be used on any HTML element (it won't work on SVG or MathML elements)

@simoncox for me, this solves a problem I've had since the days of Apache SSIs and PHP includes.

@mausmalone personally, I've had this problem from Apache SSIs to Markdown includes to components like the example. But maybe I've been hit by this issue more than most folks though.

@aardrian I didn't take it as pedantry at all. It's an important detail.