Skip to Main Content
Design & Content07 July 2026

Designing UX for Cognitive Load and Mental Health

Author

Redaksi Disabilitas.com

4 Min Read2 Views

Designing UX for Cognitive Load and Mental Health

When we talk about "Accessibility," the first image that comes to most designers' minds is a wheelchair or a blind person's white cane. However, according to data from the World Health Organization (WHO), the most common disabilities in the world are cognitive disabilities and mental health issues (including clinical anxiety, ADHD, and dyslexia).

Designing for cognitive disabilities often doesn't require complex ARIA code. It is about empathy, clarity, and respect for human cognitive limits. Utilizing psychological insights from the book Practical Web Accessibility by Ashley Firth, this article discusses how to design digital experiences that are calming, not stress-inducing.


1. Taming Anxiety in Design

Imagine a user with Clinical Anxiety trying to cancel their monthly software subscription. If the website hides the "Cancel" button and forces them to call a Customer Service agent, this can trigger a panic attack.

The Principle of Control

Good design never holds its users hostage. - Undo Actions: Provide the ability to reverse destructive actions. Instead of using an alert window asking "Are you sure you want to delete this?", use Gmail's approach: immediately delete the item, but display a toast notification with an "Undo" button for 10 seconds. - Visible Exits: Never hide the "Close Account" or "Unsubscribe" options. The practice of hiding exits is often referred to as a Roach Motel (one of the most despised types of Dark Patterns).

2. Session Timeout Management

Have you ever filled out a long registration form, and right when you hit Submit, the page refreshes with the message: "Your session has expired, please start over"? For a user with Attention Deficit Hyperactivity Disorder (ADHD), filling out that form might take 3 times longer than a typical user. Data loss is an incredibly cruel punishment.

WCAG 2.2 Criterion 2.2.1 (Timing Adjustable): If your application has a session time limit (for security reasons, like a banking app):

  1. Early Warning: Warn the user at least 20 seconds before the time expires.
  2. Extension Option: Provide a simple and clear button, for example, [Extend My Session by 5 Minutes]. The user must be allowed to extend the time up to at least ten times the initial limit.

3. Cognitive Load and Language

Reading text on a screen requires 25% more cognitive energy than reading on paper. For a person with Dyslexia or a user with low literacy skills, a "wall of text" without adequate spacing looks like an impenetrable concrete block.

Reducing Cognitive Load:

- Reading Level: Use simple language. WCAG suggests that general text should not exceed a lower secondary education reading level (grades 7-9). - Chunking: Break long paragraphs into bullet points. The human brain can only hold 5-7 items of information in its short-term memory at one time. - Avoid Jargon: Unless you are building a portal specifically for nuclear engineers, do not use technical jargon or uncommon acronyms.

4. The Danger of Deceptive Design (Dark Patterns)

Dark Patterns are interfaces specifically designed to trick users into doing something they didn't intend to do (like accidentally buying extra insurance when booking a flight).

For neurodivergent users (such as those with autism), Dark Patterns are incredibly dangerous because many of them read interfaces very literally. A classic example of a Dark Pattern (Confirmshaming):

  • Button 1: "Yes, I want the 50% discount subscription!"
  • Button 2: "No, I prefer paying the expensive full price."

This design, which shames the user, exploits guilt-tripping. True accessibility demands absolute transparency and deep respect.


5. Conclusion

Building a cognitively friendly web does not mean you have to create childish or overly simplistic designs. It means you remove unnecessary friction. When you design a clear "Cancel Order" button, provide an "Extend Time" button, and speak in human language, you are not only helping people with cognitive disabilities; you are providing a relieving and delightful experience for absolutely everyone.


References

The elaboration on UX architecture for mitigating anxiety disorders, time-out mitigation guidelines aligned with security and accessibility standards, and the hazard analysis of Dark Patterns (including literal exploitation of autistic users) are specifically extracted from the Cognitive Impairments section in the book Practical Web Accessibility by Ashley Firth (Chapter 3: Cognitive Impairments). The time limit rules refer directly to the Timing Adjustable criterion in WCAG 2.2.

What do you think?

Give your reaction to this article