Aspects of modern HTML/CSS you may not be familiar with

Okay, but are those radio tabs accessible?

I think that if you want to follow WAI-ARIA practices, the aria-selected, tabindex and aria-controls need to be updated via JS when the active tab changes? I'd love to be wrong about that.

Accessibility is often an afterthought. And, sometimes there's an assumption that by working with HTML/CSS directly, accessibility comes built in. Just Something to keep in mind when choosing an approach.

Given how un-accesible this blog post is (the contrast is quite a crime against humanity, as someone who does web dev for a dsiability charity (well communcity interest company but similar)), I wouldn't go to this for a source on this.

could you give any examples of how the page's accessibility could be improved - apart from your dislike of the background color

you're calling the post un-accessible and telling people to not use it as a source - i'd like to know why you think that, and if there's any way to improve the accessibility

This is not my dislike of the background colour (blue is actually my favourite colour, well teal), nothing in that comment was an opinion. The WCAG (Web Content Accessibility Guidelines) have standards for colour contrast [1]. If you turn on developer tools in your browser and go to accesbility you will see how many elements do not conform to these standards. The site falls astray of this in the most common way, which is blue links on a blue background, making link text very hard to read.

You can also view these issues using googles hosted version of lighthouse (chromes checking tools for speed and accessibility) at https://pagespeed.web.dev/analysis/https-lyra-horse-blog-202...

[1]: https://developer.mozilla.org/en-US/docs/Web/Accessibility/G...

ps. I love the post in general, I'm a big fan of css over javascript!