- Accessibility and Inclusion — A Better Way to Build
- The Table of Christ Has Room for All (Luke 14:12–14)
There is a difference between building something that works, and building something that works for people.
In technical contexts, success is often measured by functionality. Does it run? Does it scale? Does it meet requirements? These questions matter. But they do not go far enough.
Because a system can function perfectly — and still exclude.
May’s theme, Accessibility and Inclusion — A Better Way to Build, invites us to look again at how we design, develop, and think about the people who use what we create.
It asks a simple but searching question:
Who is this for — and who is being left out?
Accessibility Is Not an Add-On
Accessibility is often treated as a feature.
Something to be added later. Something to consider if time allows. Something required only when regulations demand it.
But accessibility is not an addition. It is foundational.
If a system cannot be used by people with different abilities, contexts, or constraints, then it is incomplete.
Accessibility is not about exceptional cases. It is about recognising that users are diverse by default.
Inclusion Is Intentional
Inclusion does not happen automatically.
Left to default assumptions, systems are designed around those who are easiest to consider — often those most similar to the people building them.
This leads to blind spots:
- interfaces that assume perfect vision,
- interactions that require fine motor control,
- content that assumes shared language or context,
- workflows that exclude those with limited time or resources.
Inclusion requires intention.
It asks us to consider people who are not immediately visible in the design process.
Designing for Real People
Real users are not uniform.
They vary in:
- ability,
- experience,
- language,
- environment,
- and access to technology.
Some may rely on screen readers.Some may use older devices.Some may have limited bandwidth.Some may interact in ways we did not anticipate.
Designing for real people means expanding our assumptions.
It means recognising that convenience for some can create barriers for others.
The Ethics of Exclusion
Exclusion is not always deliberate.
Often, it is the result of oversight.
But unintentional exclusion still has real impact.
When someone cannot access a service, they are not merely inconvenienced. They are prevented from participating. Opportunities are limited. Needs go unmet.
Accessibility and inclusion are therefore not only technical concerns. They are ethical ones.
They ask whether we are willing to build systems that serve broadly — or only conveniently.
A Better Way to Build
A better way to build begins with posture.
It values people over assumptions.It prioritises usability over simplicity of implementation.It considers edge cases as central, not peripheral.
This posture changes decisions.
Accessibility is considered early, not retrofitted.Inclusion is designed into systems, not layered on top.
Learning From Constraints
Constraints often reveal what matters.
Designing for accessibility introduces constraints:
- clear structure,
- meaningful labelling,
- predictable navigation,
- thoughtful interaction design.
These constraints do not limit quality. They improve it.
Systems designed with accessibility in mind are often:
- clearer,
- more consistent,
- and easier to use for everyone.
Inclusion in Teams
Accessibility and inclusion are not only about users. They also apply to teams.
Diverse teams bring broader perspectives. They identify issues that homogeneous teams may miss. They contribute to more robust and inclusive design.
Inclusion in teams leads to inclusion in systems.
Beyond Compliance
As with many areas of stewardship, there is a temptation to do the minimum required.
Accessibility standards can be treated as checklists. Inclusion can become a statement rather than a practice.
But a better way to build goes further.
It seeks to understand users, not just satisfy requirements.It listens to feedback, not just metrics.It prioritises dignity, not just functionality.
A Reflection of Care
Accessibility and inclusion reflect care.
They communicate that people matter — not only those who are easiest to serve, but all who might be affected.
This aligns with the broader vision of faithful practice.
We are not building in isolation. We are building for others.
Walking Into May
Throughout May, we will explore accessibility and inclusion from both technical and spiritual perspectives.
On Mondays, we will look at practical design and development — accessibility standards, inclusive design, team practices, and user experience.
On Fridays, we will reflect on the theological foundation — welcome, dignity, community, and the example of Christ.
This is not simply about improving systems.
It is about building differently.
The Invitation
As this month begins, the invitation is clear:
Look beyond the default user.Consider those who are overlooked.Design with intention.
Because accessibility is not a constraint.Inclusion is not optional.
They are part of a better way to build —one that reflects care, responsibility, and the value of every person.