Understanding resistance before answering it

When a team does not act on an accessibility finding, practitioners tend to hear one thing: resistance. In practice there are at least three different things, and the response that works for one makes the others worse.

A knowledge gap sounds like “we did not know,” “how do we do that,” or a confident wrong belief such as “the PDF is fine because it opens.” The answer is skill: a template, a checklist, a short training, a person to call. A structural constraint sounds like “we cannot,” and is often true: the notice comes from a system the unit does not control, there is no budget line for interpreters, the contract with the vendor has no accessibility clause, the staff who could do it have no time allocated. The answer is to change the structure, which usually means finding the decision-maker from the previous lesson. A values disagreement sounds like “this is not a priority,” “nobody has asked,” or “we cannot do everything for everyone.” The answer is the case for change, made in the language the person uses, and sometimes a requirement from above.

Diagnosis matters because the mismatches are expensive. Training people who face a structural constraint produces trained, frustrated people. Removing a constraint for people who do not think the work matters produces unused capacity. Making the values case to people who simply did not know how produces defensiveness where a checklist would have produced action. One question usually sorts it: “What would need to be true for this to work here?”