fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-09-19 20:02:10 +00:00
Code Issues Projects Releases Wiki Activity

New note: notice box semantics

Browse source
This commit is contained in:
Rohan Kumar 2022-09-22 09:10:44 -07:00
parent 2e2a37583c
commit 2218a44a36
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
content/notes/notice-box-semantics.md Normal file
View file

@ -0,0 +1,17 @@
---
title: "Notice box semantics"
date: 2022-09-22T09:10:41-07:00
replyURI: "https://tdarb.org/blog/notice-box.html"
replyTitle: "RE: Creating a Simple HTML/CSS Notice Box"
replyType: "BlogPosting "
replyAuthor: "Bradley Taunt"
replyAuthorURI: "https://tdarb.org/about.html"
---
I'd rather make a notice a `<section>` with a heading, or an `<aside>` if it's not related to the surrounding content.
You could even add a more specific ARIA (or DPUB-ARIA) role like `role="note"`, `role="doc-pullquote"`, `role="doc-tip"`, etc. But don't use them unless you have multiple kinds of `aside` elements and need to help people skim.
Most of these roles actually map to the `section` superclass rather than the `complementary` role of `aside`, which isn't always a problem: the `aside` element tells reader-mode implementations to remove the element, but the `role` tells assistive technologies more useful information. I use a similar hack for my in-page section permalinks.
If the notice is important to the surrounding content and reader-mode shouldn't remove it, use a `section`.