The 9th of April is CSS Naked Day. If you're reading this in a web browser with CSS enabled on the 9th April, you can probably tell that something looks different thanks to the banner across the top of every page and... well, the lack of CSS everywhere (almost - I intentionally use inline-css in a couple of posts, such as the 'Don't trust copy and paste' post which would break without it!) Thanks to timezones, this site switches off the CSS styles a bit before the 9th, and they stay off until a bit after.

I've spent a little bit of time (though nowhere near enough) over the last year making this sites' HTML more betterer but I have loads of accessibility changes to make - keyboard navigation, testing text-to-speech (or simply recording a reading of each post), and more - whilst ensuring I adhere to standards as rigidly as possible. I will also be making the HTML more accessible to people who wish to learn, inspired by jamesg.blog. I will be adding comments to the HTML and the CSS, as well as eventually publishing some information on the backend and my process of getting content live on a /colophon slashpage, but I have some work to do, getting this site to a place I'm happy with, before doing that. That work starts at the beginning though - allowing as many people to consume content with as little friction as possible. CSS Naked Day serves as a reminder to me to work towards that.

I encourage you to accommodate as many accessibility methods as possible whether you work on websites or apps or indeed physical objects. If you need a reason beyond it's the right thing to do, then... it can only increase your audience, your readership, your customers.