Skip to main content

What’s it about? Sounds complicated, right?

Let’s start by explaining what parsing is. And no, it’s not *pressing* like ironing clothes 🤓

Parsing (according to the dictionary) is the process of analyzing a string of characters to figure out its structure.

Yes, we know. It still sounds like “tough stuff.” But let’s approach this in a way that’s both practical and coding-friendly. 😉

Criterion 4.1.1 ensures the quality of our HTML code. Why? Do they really care about how the code looks?

It’s not about looks. The people behind this criterion want us to write code correctly so that all the elements function properly.

It’s a bit like punctuation in a sentence. Imagine writing “Let’s eat, Grandma,” but forgetting the comma, and it turns into “Let’s eat Grandma.” Big difference, right? 😉

It’s the same with code. If a part of your code is missing something, like a closing tag `</span>`, or you assign the same ID to two elements, the code might not work. It won’t do its job. So, let’s make sure we get it right.

Now you might be thinking, “Do I really need to go through all my code and look for such tiny errors?”

Yes, please 😉 But seriously, most code editors today will highlight these syntax mistakes for you. But if you’re writing your code in a simple text editor (I KNOW SOMEONE WHO DOES – wink wink!), I’d recommend checking it with a validator. A popular and handy one is: [https://validator.nu/](https://validator.nu/)

Simple and easy, right?

We hope your Friday the 13th is just as smooth! Wishing you lots of luck! 🐈‍⬛

Until next time!

Małgorzata Szymczak

Małgorzata Szymczak

Accessibility Specialist & Junior Frontend Developer