fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-24 05:02:10 +00:00
Code Issues Projects Releases Wiki Activity
seirdy.one/content/notes/thoughts-on-callout-semantics.md
Rohan Kumar 942186f8d6
syndicate
2023-08-29 23:01:11 -07:00

1.2 KiB
Raw Blame History

title date replyURI replyTitle replyType replyAuthor replyAuthorURI syndicatedCopies
Thoughts on callout semantics 2023-08-29T22:54:38-07:00 https://toast.al/posts/softwarecraft/2023-08-29_semantic-markup-for-callouts Semantic Markup for Callouts: A Not-Quite-RFC for Admonitions in HTML BlogPosting toastal https://toast.al
title url
Lobsters https://lobste.rs/s/ehzhcw/semantic_markup_for_callouts#c_ddiqt8
title url
The Fediverse https://pleroma.envs.net/notice/AZFO77yIoQhSicea1I

Interesting proposal! Some thoughts:

  • I'd suggest looking into the doc-notice, doc-tip, and doc-example DPUB-ARIA roles. I'm a big fan of DPUB-ARIA and I do not think it is used enough. I believe Google's Talkback has the most robust support for it put of any AT I'm familiar with.

  • I'm not convinced that a cot element is necessary. I think a heading with aria-labelledby would work better as a way to name a callout, and an attribute (or DPUB-ARIA role) could better specify the type of callout.

Funnily enough, I'm thinking about my own proposal for a spoiler element which also has similar structure to—but different semantics from—the details element.