Fair only if people can use it

A policy can use the word inclusive many times and still create an avoidable barrier. Fairness becomes more testable when a team writes conditions linked to actual tasks. ‘The courtyard is accessible’ is too broad if the review checks only whether people can enter. A stronger question asks whether different users can find the route, understand changes, operate services, participate and leave safely. Conditional clauses help turn that question into action. A trial may continue provided that a named barrier is removed. An area may remain open as long as an alternative is maintained. The policy is not ready unless each condition has an owner and review date. Grammar, however, cannot decide whether the conditions are reasonable. The affected users must be consulted, and the team must avoid making one person carry responsibility for representing a whole group. Role cards are useful for an initial classroom simulation, but they are simplified models. They can reveal missing questions; they cannot prove that every need has been covered. Results also need careful weighting. Eight easy completions do not cancel one serious barrier. Nor should every difference be treated as failure. A user may choose a different format when both formats provide the same essential information. The relevant criterion is independent, dignified use, not identical behaviour. Alternatives require maintenance. A printed schedule is not a real alternative if nobody updates it. An audio announcement is not enough if important changes never appear visually. The final policy should state a benefit, barrier, condition, responsible role, alternative and review route. If evidence changes, the team must revise the wording. This approach does not promise perfect fairness after one trial. It creates a visible process for finding unequal effects, correcting avoidable barriers and asking whose experience is still missing.