A11Y 101: Evaluating my website

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
I was super happy to learn so much from Abbey 💖
In this series I'll explore the basics of accessibility and you can join me on this learning trip.
We evaluated the website by using all kinds of accessibility tools. It's good to go through the issues we found and see what they mean. We'll do this point by point by taking the main issues we discovered in the previous article. This article is more...
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

I started this whole journey to improve my website. As I had no idea where to start, I started by reading up on some articles.
This quickly drew me to Abbey's articles on Dev.to.
In this specific series, Abbey Perini is doing the same as I wanted. So I decided to ask her if she could help me out (after reading the complete series).
While chatting with Abbey, I asked her if she would be interested in guiding me through such an accessibility audit via a live session.
This makes an excellent resource for everyone else to use and get some insights into where to start.
Without further ado, my livestream with Abbey:
During the audit, we look at which tools we can use and start exploring what kind of things we can quickly find on my website.
Since I completely rebuilt it recently and tried to follow semantic HTML as much as possible, the start is already pretty good.
However, we identified a couple of things:
This might sound like a lot, but it's not too bad. Most of these issues were found by combining the tools we used in the video.
I've written this document on helpful accessibility tools you can use.
It's good to note that most of these issues were global and occurred on detail pages.
In the following article, I'll go through them and what needs to be done to fix them.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter