Ability is not access describes the distinction between possessing an underlying capacity and being able to reliably use that capacity under the conditions in which action is required.
A person may be able to reason, write, communicate, organize, solve problems, or perform skilled work while still having unreliable access to those abilities because of fatigue, cognitive load, executive dysfunction, interruption, physiological state, environmental conditions, or other changing barriers.
Being capable of doing something does not mean that capability is always functionally available.
What Ability Without Reliable Access Can Look Like
- Knowing exactly what needs to be done but being unable to reliably begin
- Performing a task successfully one day and being unable to reproduce that performance the next
- Demonstrating high competence during an appointment, evaluation, or meeting while struggling substantially elsewhere
- Finally reaching a productive state only to lose it after an interruption
- Having supports that work temporarily but stop matching the barrier as conditions change
- Being able to clearly explain your impairment and having that clarity used as evidence that you are not impaired
The Recognition Paradox
One consequence of confusing ability with access is the Recognition Paradox:
The more successfully someone demonstrates preserved ability, the easier it may become for others to assume that support is unnecessary.
Visible competence proves that the ability exists.
It does not prove that access to that ability is reliable, stable, or available on demand.
Access Architecture Framing
The Ability/Access distinction changes the accessibility question.
Instead of asking:
Can this person do it?
ask:
Under what conditions can this person reliably access the ability to do it?
And when access changes:
How stable is that access, what disrupts it, and what helps restore it?
This is the foundation of Access Architecture: designing conditions that allow preserved ability to become usable action.
Related Reading
- [Read at PhilPapers] Niad, M. I. (2026). Ability Is Not Access: Foundations of Access Architecture for Preserved Capacity and Unreliable Functional Availability. DOI: 10.5281/zenodo.21259008
- Ability.Is.Not.Access Homepage
- Access.Architecture Homepage
