“We did it because the law requires it.”
If this is the first sentence that comes to mind when talking about digital accessibility, the problem is probably not the regulation, but the perspective. When accessibility enters a project only because it has to, it almost always ends up being treated as a compliance task: a technical check, a checklist to complete, a risk to avoid. Action is taken late, often when the project has already been defined, trying to fix only what is necessary to be compliant.
Every digital experience is created to be used by someone. A website, a service, or an app does not exist to comply with a standard, but to allow people to get information, navigate, buy, and participate. When accessibility is not part of the project from the beginning, some of those people are simply left out. Not by choice, but because the experience was not designed with them in mind. This is where the issue stops being only regulatory and becomes cultural and design related.
Designing a digital ecosystem means building languages, paths, and interactions that allow people to connect with a brand. But if that experience is not accessible, the problem is not only technical. It becomes a missed opportunity for connection, trust, and credibility.
Accessibility is not simply a box to tick on a bureaucratic checklist. It is a positioning choice that reveals the real level of your digital maturity.
At that point the question changes perspective: who can actually use what we have designed?
In recent years accessibility has become a central topic in the discussion around digital design. The introduction of regulations such as the European Accessibility Act has certainly helped bring attention to the issue. But the point goes deeper. The web is no longer only a communication space. It has become a service infrastructure. Getting information, booking services, making purchases, managing administrative tasks, accessing cultural or educational content. More and more everyday activities now take place online. When a digital experience is not accessible, for many people that service simply does not exist.
For this reason, in contemporary design accessibility is not an additional layer but a basic quality of the project. It means building interfaces that can be perceived, understood, and used in the widest possible range of contexts and conditions.
The World Wide Web Consortium, the organization that defines web standards, summarizes this idea through a few very simple principles: an experience must be perceivable. It must be operable. It must be understandable. And it must work reliably across the different technologies people use to access content.
These are not just technical criteria. They are methodological guidelines for anyone designing digital communication.
In everyday work this means making design decisions that take into account the real diversity of people and contexts of use. Sometimes these decisions concern details that may seem harmless: the way text stands out from the background, the presence of a description that allows an image to be interpreted even by someone who cannot see it, or the possibility of navigating an interface without necessarily using a mouse.
These elements may appear minimal, but they strongly affect how the experience is perceived by a large number of people.
If accessibility defines the minimum conditions that allow a digital experience to be used, inclusive design goes one step further. It shifts the focus from making something accessible to designing starting from the diversity of people.
Non è un’aggiunta a valle del progetto, né una correzione tecnica. È un approccio che entra nel processo creativo fin dall’inizio e che invita chi progetta a considerare un dato semplice ma spesso ignorato: le persone non usano la tecnologia tutte allo stesso modo, né nelle stesse condizioni.
Inclusive design starts exactly from this awareness. It means imagining experiences that can work in different contexts, for people with different abilities, habits, and needs. Not because every project must be perfect for everyone, but because the more a system is designed to adapt to human variability, the more useful it becomes for everyone.
For those working in communication and digital design this change in perspective has very concrete implications. It means designing interfaces that do not assume an ideal user who is young, fully able, and connected with the latest available device, but that instead take into account the much more complex reality in which digital experiences are actually used.
This is also where the strategic value of inclusive design becomes clear. Not because inclusion should be reduced to a sales argument, but because when a project is designed to work in different contexts it inevitably expands the audience that can truly use it.
Think for example of people with disabilities, who still encounter widespread digital barriers. Or the so called silver economy,made up of users with strong purchasing power who require clearer, more readable, and more understandable experiences. Or people who use older devices or navigate with unstable connections, a situation that is far more common than we might think.
These are not marginal niches but a significant part of the digital population. And the sooner we keep this clearly in mind, the better our projects will be.
Designing inclusively means recognizing a design responsibility and creating experiences with very concrete effects. In other words, when inclusive design is truly integrated into the creative process, it does not only improve the accessibility of a project. It improves the overall quality of the experience.
And when an experience works better for people, it almost always works better for the brand as well.
When talking about accessibility people still tend to imagine two separate categories: normality on one side and exceptions on the other. This way of thinking has influenced digital design for a long time, which has often been built around an ideal user who is perfectly able, fast, equipped with updated devices, and supported by stable connections.
The point is that this average user has never really existed. The reality of people is much more nuanced: different ages, different abilities, different levels of familiarity with technology, and contexts of use that constantly change. In other words, reality is a spectrum.
For years this complexity remained at the margins of digital projects. Not because it did not exist, but because design, like many of the systems we live in, has often been built around an implicit idea of an average user who is perfectly functioning.. Designing inclusively means exactly this: stopping the search for an ideal user and finally recognizing what has always been true. People are different, and design can and should take this into account. We all know this.
Perhaps it is worth returning to the question we started with: who can actually use what we have designed?
