Accessibility is often described as something that benefits a specific group of users. People with particular needs, special conditions, or permanent limitations. Framed that way, accessibility easily becomes a parallel concern — important, but separate from “normal” usability. In practice, it is far more ordinary than that. Most of the challenges accessibility addresses have very little to do with edge cases. They are about how work is actually carried out in everyday situations.
Tobias Rydenhag
Head of Design

Many digital systems are designed as if users are always focused, well-rested, and working in calm environments. In reality, that is rarely the case.
Systems are commonly used:
These are not exceptions. They are normal working conditions — especially in professional and industrial contexts.
Accessibility accounts for exactly these situations. Not by creating special modes or alternative experiences, but by reducing friction when conditions are less than ideal.
Most people experience limitations regularly, even if they do not think of them that way. Loud environments make audio cues unreliable. Bright sunlight reduces screen contrast. Fatigue makes information harder to interpret. Stress increases the likelihood of mistakes.
Accessibility takes these conditions seriously.
Design choices that support accessibility — clear hierarchy, sufficient contrast, explicit feedback, predictable behavior — help users stay oriented when attention is limited.
This is not design for a small group. It is design for real situations.
One of the most underestimated aspects of usability is cognitive load. The mental effort required to understand a system, track states, interpret feedback, and recover from mistakes.
High cognitive load slows people down and increases error rates. It also makes systems feel fragile — as if they demand constant attention to avoid doing something wrong.
Accessibility addresses this directly. By making information clearer, interactions more consistent, and consequences easier to understand, it reduces the mental effort required to use a system correctly.
When cognitive load is reduced, everyone benefits.
Many accessibility principles align closely with error prevention. Clear labels, unambiguous states, and visible feedback help users avoid mistakes in the first place. When errors do occur, good guidance helps users recover quickly and confidently.
In professional systems, where mistakes can be costly or risky, this becomes especially important. In those contexts, accessibility is not about accommodation — it is about reliability.
A system that supports accessibility is often one that:
These qualities improve usability for everyone, regardless of experience or role.
One reason accessibility is sometimes resisted is the belief that it primarily serves a small subset of users. That belief fades when accessibility is viewed through the lens of everyday use.
When design accounts for distraction, fatigue, stress, and imperfect environments, systems become more resilient. They work better when users are not at their best — which is most of the time.
In that sense, accessibility is not about extreme cases. It is about reality.
Good accessibility rarely draws attention to itself. It does not rely on visible features or special modes. Instead, it is embedded in how a system communicates, responds, and supports its users.
When accessibility is present, systems feel calmer. Easier to trust. Less mentally demanding to work with. When it is missing, users notice immediately — often without being able to explain exactly why.
Accessibility improves usability for everyone because it aligns design with how people actually think, perceive, and act in real-world conditions.
Not as a special requirement.
But as a natural part of good design.