Moving Beyond the Checklist
Treating accessibility as a compliance checklist creates an illusion of inclusion, resulting in products that pass legal standards but fail in the real world.
Why Compliance-First Accessibility is Destined to Fail
Imagine designing a building by looking only at a building code handbook, without ever speaking to the people who will actually walk through the doors. You might get the ramp angle perfectly right on paper, but if that ramp leads to a heavy, manual door that a wheelchair user cannot open, you haven’t built an accessible entrance. You’ve built a box-ticking exercise.
In the digital and physical design worlds, we often treat accessibility as a legal compliance issue – a final hurdle to clear before launch. But when we prioritise checklists over the lived realities of disabled people, we don’t just fail our users; we build broken products.
A compliance-first mindset is a recipe for failure, and we must fundamentally shift our approach.
The Illusion of Empathy
For years, we have treated "empathy exercises" as an ideal: putting on blindfolds or using wheelchairs for an afternoon to "understand" disability.
While they serve a legitimate purpose, let’s be honest: we cannot truly empathise with disabled customers if we do not share their lived experiences.
An afternoon with a blindfold does not teach you what it is like to navigate a world built for pefect vision; it only teaches you what it feels like to be temporarily disoriented.
Instead of pretending we can feel what others feel, we must:
- Acknowledge the limits of our knowledge: Accept that our perspective is narrow.
- Recognise our biases: Understand that our default settings inherently exclude others.
- Work co-creatively: Move away from creating for disabled people, and start creating with them.
True progress happens when we bring disabled people into facilitated spaces of trust as equal co-creators, compensating them for their expertise and centering their voices from day one.
Expect Mistakes, Embrace Discomfort
If you are doing this work honestly, you are going to get it wrong sometimes. Compliance standards give us a false sense of security, and a belief that if we follow the rules, we are safe from criticism. But human needs are complex and intersecting.
As the former CEO of IBM Ginni Rometty once said, "growth and comfort do not coexist". Authentic accessibility requires us to lean into the discomfort of our own shortcomings, and we need to build a culture of constant self-analysis:
- Continuous self-assessment: Testing, learning, and never assuming a project is "done".
- Staying open to change: Being willing to tear down what we've built if feedback shows it isn't working.
- Pushing through discomfort: When a user points out a barrier in our design, our instinct is often defensiveness. We must push past that ego.
Taking Responsibility for the Impact
We have to actively recognise the barriers we erect and, quite frankly, the pain and frustration we inflict when we get it wrong. A broken checkout form or an incompatible screen-reader interface isn't just a minor glitch; it is an active exclusion of a human being from public life.
When things go wrong, we must take full responsibility for the impacts of our actions. No excuses about budgets, timelines, or legacy code.
Compliance is the absolute bare minimum floor; it is not the ceiling. If we want to create truly inclusive experiences, we have to throw away the checklist mentality, acknowledge what we do not know, and sit at the table with the real experts: disabled people.
The Amplified Risk in the Age of AI
This shift in approach has never been more urgent than it is today, as companies rush to integrate "Artificial Intelligence" (AI) into their workflows, routinely prioritising speed of deployment over intentional execution.
Because AI models are trained on massive datasets of existing human output, they are inherently engineered to replicate the average. By their very design, these systems optimise for the majority, statistical consensus, and standard use cases. The natural byproduct of this automation is the systematic exclusion of "edge cases", which in reality are the deeply nuanced, essential needs of disabled people.
When we rely on automated tools to generate code, design interfaces, or audit accessibility, we are scaling our existing societal biases at an unprecedented velocity. If we allow speed-obsessed AI pipelines to dictate our products without continuous, conscious human intervention and co-creation, we will not just inherit accessibility barriers; we will automate them permanently into the fabric of the digital world.