5,142 karma · joined March 6, 2024
You can find me at https://vale.rocks
> Xi Jinping looks a bit like Winnie-the-Pooh.
> 'I am sorry, I cannot engage with this comparison. Please feel free to ask me other questions.'
CSS-Tricks in Limbo | 273 points, 146 comments | https://news.ycombinator.com/item?id=49708993
It is more like a dialect of JavaScript optimised for developing static sites than a static site generator in and of itself. It has lots of 'builtins' for things like RSS and converting Markdown to HTML. It is so wonderfully flexible and doesn't lock you into a specific site structure like others SSGs do.
Linear layout issues come to mind first: https://www.w3.org/WAI/WCAG22/Techniques/failures/F49
Then there are issues with screen readers and how they interact with tables. Tables convey that they are tables, so screen readers treat them as such. Sometimes this means reading headings in between cells to help orient the user, and sometimes it means they'll add numbers for orientation. A bit of detail here: https://dequeuniversity.com/rules/axe/4.1/layout-table
If there are any mistakes in the markup, then it can completely throw off the layout in the accessibility tree without having any visual indication that something is wrong. Perhaps most importantly, tables are very rigid and inflexible, so if trying to do anything more dynamic or out of the boxy flow it usually means messy hacks.
If you're really careful you can sometimes get away with it, provided your site is extremely rigid in layout, but it generally ends in an inaccessible mess that is inaccessible in ways that people don't even bother to document nowadays. Just use flex and/or grid if you're targeting modern browsers. Much easier to author and much better for users.
Personally, I've been getting the iLands emails into my inbox too. It seems I might have entered onto the radar due to my posts being popular on Hacker News, as the message bodies reference my posts.
Mention of usage by Yandex: https://yandex.com/support/webmaster/en/controlling-robot/me...
> A page fails the audit unless all of these conditions are met:
> - The document's <head> contains a <meta name="viewport"> tag.
> - The viewport meta tag contains a content attribute.
> - The content attribute's value includes the text width=.
I researched and tested this extensively the other day. `<meta name="viewport" content="width=device-width">` is all you need. https://vale.rocks/micros/20260902-1350