<h2 class="h3"> is the why.
-
-
Replying to @davatron5000
how does this proposal solve that? You can still end up with <h class="h3"> that's an AT level 2 heading.
2 replies 0 retweets 1 like -
Replying to @jaffathecake
When my components can appear anywhere on the page, the style should stay the same but it's h-level would need to be diff.
2 replies 0 retweets 1 like -
Replying to @davatron5000 @jaffathecake
The current situation is I need non-DRY <product-with-h2> and <product-with-h3> versions
1 reply 0 retweets 1 like -
Replying to @davatron5000
that's not the current situation according to the HTML spec. https://webdesign.tutsplus.com/articles/the-truth-about-multiple-h1-tags-in-the-html5-era--webdesign-16824 …
2 replies 0 retweets 2 likes -
Replying to @jaffathecake
I'm just sharing a developer pain point that I need to pass a11y checks. An unimplemented spec doesn't do much for me.
1 reply 0 retweets 2 likes -
Replying to @davatron5000
then why are you pro-<h>? It won't pass your a11y checks, and it isn't even a spec to be not-implemented,
1 reply 0 retweets 0 likes -
Replying to @jaffathecake
IMO, under the section+Hn spec, the numbers become irrelevant. It's just a heading, thus an <h> element would be appropriate.
1 reply 1 retweet 3 likes -
Replying to @davatron5000
absolutely, that's the way it should have been. But I'm not sure what the benefit is of doing it now. XHTML2 failed.
2 replies 0 retweets 1 like -
Replying to @jaffathecake
The CDC is reporting XHTML2 has re-animated and is now a zombie calling itself JSX.
2 replies 3 retweets 13 likes
: ...wait...just in...we're getting reports that JSX is actually the re-animated corpse of E4X! Parsers tremble.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.