It's already been solved by HTML spec.
Having an H tag it's the same of having the header tag. It doesn't solve any of the problems.
It's already been solved by HTML spec.
Having an H tag it's the same of having the header tag. It doesn't solve any of the problems.
The truth is, H1-H6 were useful to screen readers when the web was a lot less complicated. With the component-driven philosophy of today's web development, it's harder to maintain that structure and stay within the confines of 6 possible headings, especially for single-page designs (the ones that scroll, not "single-page apps" made entirely with JS).
the N after the H can be seen as the priority where 1 is the highest and 6 the lowest
> we don't need numbered headings like that anymore because we have semantic block-level elements like SECTION, HEADER
how do you express
HEADING > SUBHEADING > SUB SUBHEADING?
using classes? nesting tags?
> The truth is, H1-H6 were useful to screen readers when the web was a lot less complicated.
So in your opinion since the web is more complex now, we should drop perfectly reasonable tags?
> it's harder to maintain that structure and stay within the confines of 6 possible headings
I can't remember the last time this has been a problem.
a) All headers are H1, and styled the same, unless you then start classing up the section and h1 tags accordingly = more complex css than need be.
b) not-so-clever page crawlers won't be able to extract the real H1 header that should title the page content.