Passing accessibility checks feels like a finish line.
The audit is clean.
The tooling reports no errors.
The acceptance criteria are satisfied.
And yet, something still feels unresolved.
That unease is what now guides my testing.
Compliance answers whether something is technically accessible. It does not describe what it is like to move through a system over time.
Two systems can meet the same standards and demand very different amounts of effort from the person using them.
One feels calm.
The other feels like work.
After the checks pass, a different set of signals becomes visible.
- how much remembering an interaction demands
- how often a user must re-orient themselves
- how many micro-decisions are required just to make progress
None of these show up as failures.
Tasks are completed.
Outcomes are achieved.
But effort accumulates.
When teams stop at compliance, that effort does not disappear. It simply moves.
It moves to the user.
A person who eventually completes a task is often treated as a success case. Accessibility testing exposed the limits of that framing.
Effort is a cost, even when outcomes are achieved. Confusion is a cost. Fatigue is a cost.
When systems rely on those costs, they remain accessible only as long as people are willing — or able — to keep paying them.
This is what I now test for after the checks pass.
Not because standards are wrong.
But because people experience systems — not conformance.