Welcome to the a11yblog. That’s a-eleven-y blog, or rather accessibility blog, as the following image explains.

This is going to be a blog on web accessibility, which has to do with how we ensure web pages are possible to use in a multitude of ways, catering to the typical user as well as users relying on assistive technologies such as screen readers, voice control, screen magnifyers et cetera.

I, Helena, am starting the blog today and I will write mostly from a web developer’s point of view and relating to European legislation. I will also invite others to write, hoping this blog will be a collaborative effort. If you are looking for a place to share your own thoughts on web accessibility, please contact us!

Why then, a blog on this subject? Web accessibility is a hot topic! For web developers it’s essential to learn how to develop with accessibility in mind, and that is for two main reasons:

1. Accessible websites are better for everybody! Having an accessible website is having a usable website, and of course you want your users to be able to fulfill their order, find the information they’re after, submit their application, or whatever applies to the website in question.
2. The law already requires public sector websites to be accessible, and with the European Accessibility Act of 2025 these requirements will apply to all websites providing products and/or services to consumers on the European market.

I spend a lot of my time working with accessibility issues these days: conducting accessibility reviews, solving accessibility issues in existing websites, writing accessibility statements and of course, prototyping and developing with accessibility in mind. And I have to admit: it’s not always easy. Sometimes it’s hard to know exactly what is needed to meet the legal requirements, and sometimes it’s hard to map a perceived flaw to a legal requirement. We can all benefit from sharing and discussing our findings, and I hope this blog will contribute to that.