Perspective

I have to remember information from an earlier step

The interface makes a person retain or re-enter information that the system could keep available.

Memory should not be used as an unnecessary interface requirement.

Interface demands

• Memory
• Attention
• Accurate transcription

These describe what the interface requires from the person in this barrier. They are not disability categories and do not imply that everyone affected has the same experience.

What happens

A multi-step process asks someone to recall a reference number, value, choice or other information shown earlier, or asks them to enter the same information again.

Why it matters

Working-memory demands can create barriers for people with cognitive and learning disabilities and for anyone dealing with interruption, stress, fatigue or complex tasks.

How to test it

Complete multi-step flows and note every piece of information the person must carry between steps. Check whether previously entered information is auto-populated or available to select, and whether important reference information remains visible or easily retrievable.

Can automation detect it?

Rarely as a complete problem. Detecting unnecessary memory and redundant entry requires understanding relationships between steps and the task.

Relevant WCAG

Repeated entry can relate to 3.3.7 Redundant Entry. Other memory burdens may be usability/cognitive-accessibility concerns without a direct AA success criterion.

Standards & guidance

• WCAG 2.2: relevant criteria depend on the exact repeated-entry or authentication pattern; do not infer a failure from memory demand alone.
• W3C Cognitive Accessibility Supplemental Guidance: Ensure Processes Do Not Rely on Memory — informative guidance beyond WCAG conformance.

The W3C supplemental guidance is not a WCAG success criterion. It is included because it addresses user needs that can remain important even when no normative WCAG failure is established.

What a pass does not prove

Avoiding duplicate entry does not prove the overall process has reasonable cognitive load or that instructions remain available when needed.

Follow the evidence trail

• Standard where applicable: 3.3.7 Redundant Entry
• Broader guidance: W3C Cognitive Accessibility guidance
• Test it: A practical cognitive and usability review
• Try it: How much are you being asked to remember?
• Evidence limit: not every unnecessary memory demand is a WCAG failure; user research may be needed to understand impact.