My journey

I started my career as a frontend developer, and like many, I was mostly focused on the visual aspects of the web. In my last job interview, though, I was asked some questions about accessibility and ARIA, which made me realise how little I had actually put into practice in this area. I knew what ARIA was in theory, but I hadn’t really spent much time thinking about accessibility or checking how usable the products I built were.

Up until that point, I just followed the basics: using semantic HTML, adding labels to inputs, and making sure images had alt attributes. It was a good starting point, but I quickly realised it wasn’t enough when I joined the new company. I was assigned to a team building core components, and I saw that accessibility was a priority. Everything was built with ARIA in mind, which made me want to dive deeper into the topic.

With every new component I worked on, I made sure the design was accessible from the start. I collaborated closely with the design team to make sure we were building components that were inclusive for everyone. As I got more comfortable with the concepts, I started using automated tools to check for any accessibility issues in the user experience. After that, I would also test everything with a screen reader to double-check that it all worked smoothly.

Over time, I became the go-to person on my team for accessibility-related questions, not only internally but also for clients. They often come to me for advice on ensuring their designs and products meet accessibility standards. I now think about accessibility as something that should be part of the process from the very beginning, not just something to fix later

What I Do

On this blog, I simplify complex accessibility concepts and turn them into practical steps that anyone can follow. I write about how to build accessible components, share tips on testing for accessibility, and explain why accessibility should be a core part of frontend development. Whether you’re just starting out or you’ve been coding for years, I want to help you make the web a more inclusive place.

Here’s what you can expect from me:

• Code Snippets & Tutorials: I’ll walk you through building common UI components like forms, buttons, and modals—with accessibility already built in.
• Practical Advice: You’ll learn how to add accessibility into your development workflow without sacrificing design or performance.
• Real-World Examples: I’ll share case studies and real-life examples of how accessible components not only improve the user experience but can even boost your SEO.

My Mission

For me, accessibility isn’t just an option—it’s a responsibility. My mission is to help developers understand that making a website accessible isn’t as complicated as it might seem, and it benefits everyone in the end. By focusing on inclusive design and building components that work for all users, we can make the web a better place together.