ICYMI, @matuzo was kind enough to include my piece about the <details> element in this year’s HTMHell Advent Calendar!
Interactive and accessible SEO goodness abounds!
ICYMI, @matuzo was kind enough to include my piece about the <details> element in this year’s HTMHell Advent Calendar!
Interactive and accessible SEO goodness abounds!
Awesome. I did not know about the exclusivity via `name` thing.
Potentially relevant: I recall a Twitter discussion a few years ago, with @SaraSoueidan and Scott O’Hara among others, about the perils of heading semantics inside the <summary> element. I’m not sure where that has ended up several years of browser development later, and can’t find a reference to it
@urlyman Last test I did a few weeks ago for one of my course chapters was that heading inside summary was still not exposed by JAWS paired with Firefox on Windows. Plus users on previous versions of JAWS (prior to 2024 IIRC) won't get those exposed as well. My current approach is progressively-enhanced custom widget with <hx><button></hx>.
@SaraSoueidan thanks Sara. Yes, whenever a heading is justifiably involved as the synopsis of content that is expandable/collapsible I too continue to use that pattern :)
@urlyman The best thing about that is that it's easier to make print-friendly too =)
@developerjustin aha, I’ve found that @yatil opened https://github.com/whatwg/html/issues/8864 nearly 3 years ago, and that Scott and @aardrian added thoughts. I need to read more closely.
This Chromium-related document from David Baron looks to be a good summary https://docs.google.com/document/d/1IO5m67Ngw_J1OmNBdzGhB7Rd7B-9vcuQWtrGaeovsJE/edit?tab=t.0#heading=h.hbp1zf7jgf7w