Perspective

A practical cognitive and usability review

Look for memory, ambiguity, interruption and recovery costs that a technical accessibility scan cannot evaluate.

Cognitive accessibility should not be reduced to a readability score.

Follow a real task

Work through the task while noting what the interface requires the person to understand, remember, infer and recover from.

Look for avoidable memory

Does the person need to retain information from another page or step? Is previously entered information requested again? Are instructions still available when needed?

Look for ambiguity

Are labels, instructions and next steps predictable? Does terminology assume organisational or specialist knowledge?

Look for interruption and timing

What happens when someone pauses, gets interrupted or takes longer? Is progress retained?

Look at recovery

Can mistakes be understood and corrected without starting over or remembering hidden information?

Record evidence, not diagnoses

Describe the observed demand: “the reference number shown on step 1 is required on step 4 and is no longer visible.” Do not infer a person’s diagnosis from difficulty with an interface.

What a pass establishes

You reviewed specific cognitive/usability demands in the tested task.

What it does not establish

An internal review does not substitute for research or testing with people with cognitive and learning disabilities.

Follow the evidence trail

Start with the memory barrier → try the memory Lab → use W3C cognitive accessibility resources for broader guidance beyond conformance.