A design can feel effortless when it has anticipated your circumstances.
It can feel very different when you are the person expected to adapt—to a way of reading, moving, speaking, understanding, or participating that does not work for you.
Inclusive Design is the practice of investigating and reducing that exclusion. It considers the diversity of people's abilities, identities, languages, cultures, technologies, resources, and circumstances when shaping an experience.
At Abstraction, it means asking whose needs the design has understood, whose it has assumed, and who may have been left outside the conversation altogether.
We want people to feel that the experience has made room for them. That requires more than an image of inclusion. It requires choices they can actually use.
Notice what the design takes for granted
A product may assume someone has a recent phone, a reliable connection, a quiet room, fluent language skills, uninterrupted time, or a particular way of using an interface.
A service may assume the person making a booking is the person attending, that everyone can contact support during business hours, or that visitors already know how the place works.
Those assumptions deserve examination. Some reflect genuine requirements. Others are habits that have become invisible to the people creating the experience.
Microsoft's Inclusive Design approach offers a useful starting perspective: exclusion can emerge from a mismatch between a person and the experience, and learning from diverse perspectives can help expose it.
We carry that question across digital products, content, brands, services, and environments. What is the person being asked to supply or do—and why have we assumed that is the right condition for participation?
Inclusion and accessibility are connected, not interchangeable
Digital Accessibility addresses disability-related barriers in websites, applications, content, and interfaces. Inclusive Design considers a wider range of circumstances that can affect participation.
The distinction matters. A broad intention to design “for everyone” should not make the specific needs of people with disabilities disappear into a general discussion of usability. W3C's explanation of accessibility, usability, and inclusion emphasizes both their overlap and the importance of maintaining that disability focus.
An Accessibility Audit is a defined evaluation activity. It is not replaced by an inclusive philosophy, a varied collection of photographs, or positive feedback from a few users.
Similarly, a usable website does not establish that its connected physical environment is accessible. Architecture and physical access require their own appropriate design, expertise, and assessment.
These responsibilities can work together while keeping their differences visible.
Learn with people, not only about categories
We need to understand what people actually encounter rather than use a label as a substitute for their experience.
Two people with the same disability, age, language, or job can have different needs and strategies. One participant's account can reveal something important without representing everyone who shares an attribute.
We can bring relevant lived experience into discovery, exploration, and evaluation through Design Research, appropriate specialist support, and Co-Creation. That involvement should itself be designed thoughtfully: understandable material, suitable tools, appropriate access, clear expectations, and respect for the person's time and information.
Asking people to participate in a process they cannot comfortably access would reproduce the problem we are trying to understand.
Empathy and professional knowledge contribute to the work. They do not make direct experience unnecessary or turn a simulation of a difficulty into a complete understanding of living with it.
Making room for different ways of arriving
When shaping a showroom booking journey, we examine what each step asks of the person: choosing a time, completing a form, receiving a confirmation and arriving at the door.
A sequence that looks straightforward can contain assumptions about language, access, available time or the phone someone carries. We work with the business to make those assumptions visible.
We explore different circumstances rather than define one “typical” visitor and stop there.
| Moment | Question worth examining |
|---|---|
| Learning what the visit involves | Can someone understand the purpose, expected duration, location, and useful preparation without knowing the business already? |
| Choosing a time | Can the selection be operated and understood through the relevant access methods, rather than only a particular visual interaction? |
| Completing the form | Are the required fields genuinely necessary, and do the choices accommodate the people the service intends to welcome? |
| Receiving information | Can the person retain and revisit the details in a useful format? |
| Arriving | Does entry depend on a charged smartphone or one specific communication channel, and is there an appropriate alternative? |
| Asking about access | Is relevant information available clearly, with a real route to resolve questions the published information does not answer? |
| Meeting staff | Can the human handoff respect the person's needs without making them unnecessarily repeat sensitive information? |
The response might involve clearer content, changes to form requirements, accessible interaction, more useful arrival information, or coordination with the people managing the space.
We would need to verify what the venue and service can actually provide. A statement that an alternative is available is not helpful if the staff, tools, or environment cannot support it.
These questions help us identify what to investigate with the people affected and which alternatives the venue can genuinely support. We review those alternatives in context, rather than assume that one route will work for everyone.
Sometimes the inclusive choice is a choice
One interaction does not have to carry every need in exactly the same way.
An experience may support different ways to understand information, complete a task, or receive assistance. The aim is useful participation, not identical behavior from every person.
That requires care. An alternative should not be so hidden, burdensome, slow, or incomplete that it exists mainly to reassure the organization. We examine what it actually asks of someone and whether it serves the purpose.
We also avoid making a person disclose more about themselves than the interaction reasonably needs. It may be possible to offer a useful option without first asking them to explain or prove why they want it.
The right response depends on the context. Some needs should be supported in the main experience from the start; others may require an additional route or a specialist conversation. We make those decisions deliberately rather than treating everyone outside the default as an exception to be handled later.
Words and images help define who belongs
Language can make an experience feel familiar, confusing, welcoming, or exclusionary before anyone encounters a functional barrier.
We consider what the audience needs to understand, which terms require explanation, what a question assumes, and how imagery represents the people involved. We should not infer someone's needs or behavior from a demographic shorthand when we could investigate the actual circumstances.
Content Design and Form Design connect those decisions to the task. A required field, a preset category, or an unexplained phrase can reveal an assumption just as clearly as a physical obstacle.
Inclusive expression does not require abandoning a brand's character. It asks us to make that character communicate with care—and to examine whether the practical experience supports the welcome the imagery suggests.
Follow the experience beyond the screen
People do not divide their needs according to an agency's practice categories.
An accessible booking flow can lead to unclear arrival instructions. A considerate physical welcome can be undermined by a follow-up message the person cannot use. A helpful employee may be compensating for a service process that repeatedly excludes the same circumstances.
Customer Experience Design helps us examine continuity across those moments. Service Blueprinting connects the visible experience to the people and systems that need to support it.
For Abstraction, this is an important connection among Digital Design, Branding, Architecture, Development, and Marketing. The work can cross practices without pretending every access issue is the same discipline or that every specialist responsibility belongs to one team.
Give the unresolved needs somewhere to go
Inclusive Design is not a claim that one project can resolve every possible barrier at once.
We need to be clear about the people and contexts considered, the evidence available, the limitations identified, and the work still required. Time and budget affect the response; they should not make a known issue disappear from the record.
We can document the assumption, who may be affected, the consequence, possible responses, and what needs further investigation or specialist evaluation. That creates a basis for responsible prioritization and follow-through rather than a broad promise that cannot be examined.
Standards-based accessibility work and research with people contribute different evidence. W3C explains why user involvement does not replace accessibility requirements and why tools alone cannot establish accessibility. We need an appropriate combination, not one reassuring result treated as proof that every barrier has been addressed.
An inclusive intent becomes more credible when the team can show what it has considered, changed, tested, and left open.
Keep making room as the experience changes
Inclusive Design belongs throughout Design Thinking:
Discover → Define → Explore → Design / Develop / Market → Learn → Advance → Discover.
People, technologies, content, and service conditions change. New feedback may expose a barrier we did not see, or show that a well-intended option does not help in practice. Continuous Improvement gives us a way to carry that learning into the next response.
The goal is not to make people fit our idea of a user. It is to keep improving how the experience fits the people it is meant to serve.
If something you are making feels as though it only works for people under ideal conditions, we can help investigate who else needs a place in the design.