mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-23 21:02:09 +00:00
New note: callout semantics
This commit is contained in:
parent
25684aa384
commit
3e61193a66
1 changed files with 17 additions and 0 deletions
17
content/notes/thoughts-on-callout-semantics.md
Normal file
17
content/notes/thoughts-on-callout-semantics.md
Normal file
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
title: "Thoughts on callout semantics"
|
||||
date: 2023-08-29T22:54:38-07:00
|
||||
replyURI: "https://toast.al/posts/softwarecraft/2023-08-29_semantic-markup-for-callouts"
|
||||
replyTitle: "Semantic Markup for Callouts: A Not-Quite-RFC for Admonitions in HTML"
|
||||
replyType: "BlogPosting"
|
||||
replyAuthor: "toastal"
|
||||
replyAuthorURI: "https://toast.al"
|
||||
---
|
||||
|
||||
Interesting proposal! Some thoughts:
|
||||
|
||||
- I'd suggest looking into the `doc-notice`, `doc-tip`, and `doc-example` [DPUB-ARIA](https://w3c.github.io/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.
|
Loading…
Reference in a new issue