Browsers are starting to roll out changes in default UA styles for nested section headings. This post describes the incoming changes, how to identify if it's an issue on your websites, and hints for conformant and better-structured pages.
I’ve always followed the “only one h1 per page” guidance. I had no idea this was a thing.
Seems like a good simplification.
The fact that it is being done and how breaking changes like that are handled is interesting - specifically in the context of messy mixed html parsing and contexts and usage. The least specificity selector :where(h1) is also interesting as guidance.
I like the idea of using h1’s as local top-level headings. But I also like that they reverted this thing they introduced some years ago. It forces us to locally style h1’s inside of articles and asides and such elements. This is the best of both worlds IMO.
I’ve always followed the “only one
h1per page” guidance. I had no idea this was a thing.Seems like a good simplification.
The fact that it is being done and how breaking changes like that are handled is interesting - specifically in the context of messy mixed html parsing and contexts and usage. The least specificity selector
:where(h1)is also interesting as guidance.I like the idea of using h1’s as local top-level headings. But I also like that they reverted this thing they introduced some years ago. It forces us to locally style h1’s inside of articles and asides and such elements. This is the best of both worlds IMO.