The frustrating thing about all this is that HTML already has features to, for example, distinguish headers and footers from a post's body. Social media just doesn't use it, simply smacking a post's content onto the site in plain text, leaving the screenreader to guess what's going on.
It definitely is the site's responsibility, but writing proper #semanticHTML is unfortunately not a priority.
Holy crap.
I think I just found the single most impressive blog post I've ever seen.
blog.glyphdrawing.club/why-is-…
Not only is it super elaborate, well written and sourced, it's also beautiful and impeccably styled with mostly perfectly #SemanticHTML... and it contains *practical, interactive* elements like drawing canvases and dynamic multifont charts??
This would take me like more than half a year of nonstop work to put together. All for a "complementary post" to another!!
Holy shit.
@gdc
There's a small house in the moddle of IBM's Code Page 437. Why?GlyphDrawing.Club -blog
Semantic websites are awesome! Among other things, they let you write reusable CSS. Please send me your semantic websites, so I can analyze them for common patterns and write a composable CSS framework.
jak2k.schwanenberg.name/post/c…
#indieweb #smolweb #semanticHTML #html #semantic #css #semanticcss
I have a question regarding a semantic HTML construct, and I'd like to know what the current consensus is (if there is one). So here goes:
Should navigation links be placed in an unordered list in a <nav>?
The spec doesn't recommend anything, but examples from MDN (developer.mozilla.org/en-US/do…) and WHATWG (html.spec.whatwg.org/multipage…) consistently use lists unless the contents are written in prose. Is this still the preference more broadly?
I have some other questions in this area. Safari removes list semantics if you remove the bullets (with exceptions, such as if the list is a child of "nav"), due to alleged "list-itis". At what point do lists become inappropriate? If I have a list of blog posts, and I format them as cards, with a heading, publish date, summary, and an image, is that too much content for each <li>?
Also, MDN and WHATWG point out not all links should be contained in navs (such as footer links), and "nav" should instead signal major blocks of navigation links. Would my prior example of a list of blog posts count as a major block? Should I enclose my list of blog posts in a nav? Does that extend to all section, category, and tag pages listing pages in that section/category/tag?
Feel free to respond if you have opinions, but keep it civil, and boosts are appreciated.
