I'm sure a lot of web folk are going to say "wow you're late to the party" but the fact that the <h1> tag's text size shrinks for every <article> or <section> it's inside of, but the other tags (like <h2>) do not.
That is a *BONKERS* decision and it's apparently intentional
@irina from the look of the standard it looks like it only calls out H1, I wonder if that was supposed to be an example and people took it literally?
https://html.spec.whatwg.org/multipage/rendering.html#sections-and-headings
it would definitely make *more* sense if they were to all shrink (or none shrink) though 😀
@JoshJers i can't find the name of it so i can't find it, but i think the plan was they'd all do that, so they implemented it for h1, but nobody cared so they never did any more? something about using the article and section tags instead of the different H levels
someone will know the name of the thing I'm thinking of, but googling keywords has led me to nothing
Yeah pretty much
standards folks thought there needed to be an outline algorithm to determine the tree structure of headings that are out of order, and browser developers, accessibility experts, and screen reader devs all said they don't plan on implementing it https://www.w3.org/Bugs/Public/show_bug.cgi?id=25003
But the spec also included sample CSS that does this resizing and that part did make it into browsers somehow https://github.com/whatwg/html/issues/7867
@JoshJers @Osmose @irina they did, in XHTML 2 https://www.w3.org/TR/xhtml2/mod-structural.html#sec_8.5.
But everyone hated that spec so they backtracked
@irina hahahaha amazing
great job W3, 10/10 no notes
I think the idea is that there's really only supposed to be one <h1> per page, and if you have them in an <article> you probably want it to be a sub-article of some sort with a smaller main title. I admit it does get a little out of hand once you nest multiple articles but that is a pretty odd use-case in which you're probably using custom CSS anyway overriding the defaults.
@JoshJers @amin @eniko I guess they didn't expect people to mix "put an H1 inside a bunch of sections" and "use decreasing H2-H6 tags" in the same page?
No idea why they wouldn't expect that, web developers will do any cursed thing you can imagine once your content's run through five people and two frameworks in four languages, but oh well
@oscherler @andrewt @JoshJers @eniko
Yeah, haha. I tried following typographic principles to make readable.css, my classless CSS framework, but it's definitely not easy. :)
@amin @oscherler @andrewt @eniko Just wanna say that I appreciate everyone who goes through the trouble to actually make a light and dark theme (at leastusing the theme preference selector)
I just did so on my blog ( http://drilian.com ) and it's not hard as long as you're careful about how you refer to colors
(also as an added bonus it usually ends up making you use a more limited palette and not just throw color tags around willy nilly, which is better for maintainability and consistency anyhow)
@JoshJers @oscherler @andrewt @eniko
Yep! And CSS custom properties (variables) are so useful when doing so.
HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [HTML] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.2 for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.
This is what I found:
https://html.spec.whatwg.org/multipage/rendering.html#sections-and-headings
@JoshJers
but heading levels are supposed to be hierarchical
I don't think you're supposed to have more than one h1 per page
and even then, how the hell does this fit into the hierarchical model???
@tthbaltazar apparently because it's so common to like nest code from generators and it was frequent that they all used H1 tags they just said "fuck it, nested H1s get smaller now in these elements" but didn't also specify the same behavior for the others
it's a *baffling* choice
wow, that's absolutely disgusting, and also something i've come across and just given up on figuring out because typography is something i enjoy and the webshit committees absolutely despise for some reason
I didn’t know that detail, but I never write anything that uses UA defaults, so I don’t see it as an issue.
The problem is more the persistence of legacy h1-h6 rather than a simple contextual header per section, but I doubt we’ll ever be rid of it.
(Although you can write it in your own markup interpreter if you feel like it. It’s fun. Particularly because you don’t have to keep count of h levels.)
Edward Jazzhands
Josh Jersild
irina [moved to critter.cafe]
Osmose
Not a Spring Onion
Charles ☭ is now tooting from queer.party
Talya (she/her) 🏳️⚧️✡️
NKT
Sören
Eniko (moved ➡ gamedev.place)
Amin, minor deity of the legume realm
Andrew
Ölbaum
Angelino Desmet
Seirdy
ArneBab
Graham Sutherland / Polynomial
Tóth Gábor Baltazár
trusty falxter 🧠
Tröglödÿt
AzureArmageddon
abbie
Electropict
tekhedd
Indiealexh