
If not an audit, then what drives change?
Why accessibility audits alone do not sustain change, and how organizations build accessibility into everyday work.
Introduction
This article is not against accessibility audits. It asks what an audit can and cannot-change, and what helps accessibility improvements last.
Do we really not know what is wrong?
The problem is not diagnostic. It is organizational.
Analyses often make the argument that organizations lack the capacity to diagnose themselves and change.
That is a fair observation-but it can lead to the wrong conclusion:
If an organization lacks the capacity to act, an audit of that capacity will not create it.
An audit can:
- provide a report,
- organize what is known,
- strengthen the case for action.
But it cannot:
- make decisions,
- change processes,
- build accountability.
So the question is not whether an organization can diagnose itself.
The question is whether it can act on the diagnosis.
Why are audits so easy to sell?
If the impetus for change already exists and the knowledge is available, why do organizations choose an audit?
Because an audit is a convenient solution:
- quick to commission,
- external,
- formal,
- seemingly complete.
It promises a simple logic:
We’ll tell you what to do, and the problem will be solved.
It is an appealing promise. But it rests on a mistaken assumption that accessibility problems stem from a lack of knowledge, rather than from the way an organization operates.
This is not about choosing what is easier
Another argument is that the proposed approach requires systemic change-and that is difficult.
That is true.
But this is not a choice between easy and difficult.
It is a choice between what works and what does not.
The illustration compares two ways organizations approach digital accessibility. On the left is an impulse-driven model, such as an audit, where actions are periodic and reactive and fade when immediate pressure is gone. On the right is a systemic approach that makes accessibility part of everyday work through decisions, standards, testing, fixes, and ongoing monitoring. Impulses can start action, but only a system sustains it and produces lasting results.
An audit is easy to start:
- we commission it,
- we receive a report,
- we fix some things.
But if the organization’s way of working does not change:
- the same errors return,
- new ones appear,
- the process starts over.
Then:
We audit, fix things-and end up back where we started.
Is that really easier?
What actually drives change?
Change begins not with a report, but with a change in how the organization operates.
In practice, that means:
- Management decisions – not merely assigning someone responsibility, but defining the organization’s approach to accessibility:
- adopting standards,
- establishing processes and procedures,
- making accessibility part of how the organization works.
- Integration into processes – accessibility becomes part of everyday work, including:
- publishing content,
- designing services,
- deploying and developing systems.
- Making problems visible – the organization can see where accessibility is falling short through:
- functional testing,
- ongoing monitoring,
- actively gathering feedback from users.
- The ability to act – the organization can respond with:
- team skills,
- access to tools,
- practical capacity to make fixes, including time, resources, and accountability.
Accessibility does not begin with an audit. It begins when an organization starts doing things differently.
What role do experts play?
The idea that “you do not need an audit at the beginning” is sometimes interpreted as “you do not need experts.”
That is a misreading.
The problem is not that experts are unnecessary. It is that they are being used in the wrong way.
In an audit first
model, the expert’s role is narrowed to:
- identifying problems,
- producing reports,
- recommending what to fix.
This is important work-but it is limited.
In a systemic approach, experts have a much broader and more strategic role. They are not just auditors. They are:
- designers of standards,
- co-creators of processes,
- trainers and mentors for teams,
- advisers who support decision-making,
- partners in solving complex problems.
This means shifting:
- from
someone who comes in and evaluates
, - to
someone who helps the organization work better every day
.
A mature approach does not diminish experts’ role. It expands it.
What is more, a systemic approach needs more people who understand accessibility-not just a small group of auditors, but:
- editors,
- designers,
- testers,
- developers,
- accessibility coordinators.
Accessibility stops being the domain of experts among experts
.
It becomes a shared organizational capability, supported by experts.
Audits still have a place in this model. But experts are not needed only to conduct audits.
Above all, they are needed to ensure that an audit is no longer the only tool for taking action.
The myth of secret knowledge
In an audit first
model, another less often discussed problem can arise.
Accessibility starts to be treated as specialized knowledge available only to a small group of experts.
The expert becomes:
- the keeper of
secret knowledge
, - the only person able to understand the problem,
- the only source of a solution.
As a result:
- developers say,
accessibility is not my job
, - designers wait for instructions,
- the organization becomes dependent on external opinions.
This is a false picture of reality.
Most accessibility problems do not require secret knowledge. They require the careful application of sound software development principles.
HTML semantics, information structure, keyboard support, readable content, and predictable interactions are not extra
skills. They are basic skills for everyone who builds digital products.
Of course:
- some problems are complex,
- some situations require deeper expertise,
- specialist knowledge is sometimes necessary.
But these are not the source of most everyday barriers.
Accessibility is not an extra specialization
. It is part of the craft of building digital products.
In a systemic approach, the expert’s role changes:
- not to
own the knowledge
, but to spread it, - not to replace the team, but to strengthen its capabilities.
An expert is not a gatekeeper of knowledge. An expert multiplies it.
The key point
An audit can start action. But only a system can keep it going.
So the key question is not: Are we conducting an audit?
The key question is: Is our organization set up so that accessibility is built into our everyday work?
Translated from the Polish original with permission.
Need help with digital accessibility?
- Audit and debug pages with reports in a user-friendly format directly from the browser.
- Install when you can't use browser extension.
- Audit fully rendered pages, including themes and plugins.
- Effortlessly audit every page automatically. Integrate a code snippet and manage multiple sites from a central dashboard.