4 ms·

The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? That seem

The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? That seemed to be the crux of this article, we don't need numbered headings like that anymore because we have semantic block-level elements like SECTION, HEADER, etc. These elements can be used by the browser to deduce a structured outline from the page, and it's also easier to use said elements when you can think of them as portable components (without resorting to setting CSS classes on everything). 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).

walterstucco 10y ago
> The H tag would replace the H1 tags in all your SECTIONs. You're not using H2-6 in there at all, so what do we need the "1" on the end of H1 tags for? 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.