Web development Blog

Recently, someone posted on LinkedIn that skip links are often broken because their target elements are missing a tabindex attribute. I was really surprised to see that because I thought that was an issue of the past. That's why I decided to test it.

In the previous post, I explained how to hide presentational SVGs using aria-hidden="true".
That's a reliable technique, but sometimes I see developers use role="presentation" instead, which may or may not work as expected.

The title says it all: put aria-hidden="true" on decorative SVGs, or they'll be announced by some screen readers.

To kick off my new article series, #WebAccessibilityFails, I decided to focus on a bad practice I often see in main navigations during accessibility audits.

When you open the accessibility settings on your smartphone and increase the font size, you will immediately notice that the system font size increases. On Android, as a Firefox user, you will also notice that websites scale. As a Chrome user, you won't see any difference because Chrome doesn't respect the font size settings for web content. As an iOS user, it's the same.

There is a new HTML element called geolocation. I checked it out and here's what I learned.

You probably already knew that you can use :where() to lower the specificity of a single selector, but did you know that you can achieve a similar effect on multiple rules at once?

As someone who enjoys attending conferences, I thought it might be helpful to share a list of my favourite front-end and web development conferences.

I recently added a rule to my reset style sheet UA+ that I wanted to share with you.

Once again, I’ve teamed up with my friends at Smashing Magazine 😻 to share with you everything I know about web accessibility testing! In this smashing workshop we’ll talk about automatic and manual testing, screen reader basics, Single Page Applications, Dev Tools, and more.