Today is Global Accessibility Awareness Day and you see companies like Apple, Microsoft, and Google post about how they are making things more accessible for their users¹.

It’s good to see major companies doing this as it helps everyone. I just wanted to take this time to remind you that you can do your part by making your website a little more accessible.

A good place to go is WebAim and looking at the page on accessibility for designers. After reviewing the guidelines, you can checkout this page of accessible website examples.

What I really enjoy about this article is that it has VIDEOS showcasing how the different browsers work with alternative text.

I think that it’s a really good read as I’ve seen a couple apps and services advertise that they can generate the alt text for images. I never really worried about the upper limit for descriptions. I know that I’m a little terse when it comes to describing things - for example, my about page. After reading this, I feel a little more confident in this aspect.

The article goes into some details in some dangers of having a very long description.

Sometimes you can have too much alternative text, particularly for an %lt;img>. I don’t mean there is a limit to what is allowed, I mean there is a limit to what is usable by humans. This long cat photo demonstrates that.

This is a really good article and I’ve added the blog to my RSS reader. I spent a good 30 minutes researching <aside> and role=note and what that could mean for writing and reading on the web.

The more that I work with accessibility, the more I’m enjoying solving the smaller issues. Unfortunately, I also see a lot of areas where things could be improved.

Discovered via Auston.

I’m planning on going to Front End Study Hall on April 24, 2024 Noon PST.

The description of the meet up is as follows:

If you're a maven of markup or stylesheet superstar, or a newbie novice with nth-of-type, all are welcome to learn together at Front End Study Hall

The foundation of a flexible, good IndieWeb website is markup (the “M” in HTML!") that doesn’t drive you batty to debug and CSS that works with it to have it look, sound, and interact how you want, whatever device or format the website is displayed on.

Discovered via gRegor Morrill¹.

We've started a new project which requires heavy, creative theming, so I made a prototype to test some ideas out.

I really like this article as it breaks down the reasoning of why they are doing what they are doing. It has some examples that you can follow along with and leaves me thinking about how I can take this knowledge into my own development.

Discovered via Andy Bell