Skip to content

Commit c695b34

Browse files
authored
[Term Entry] UI/UX UX Psychology: Postel's Law
* [Term Entry] Add Pastels Law * Update: text edit * fix formatting * add examples of postel's law in practive * consistent bullets and Postel's spelling fixed * updated image for Postel's law * Minor changes ---------
1 parent 4af8cd2 commit c695b34

File tree

2 files changed

+71
-0
lines changed

2 files changed

+71
-0
lines changed
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
Title: 'Postel’s Law'
3+
Description: 'Postel’s Law, or the Robustness Principle, encourages flexible input handling while ensuring predictable output in UX design.'
4+
Subjects:
5+
- 'Web Design'
6+
- 'Web Development'
7+
Tags:
8+
- 'Accessibility'
9+
- 'Design'
10+
- 'UX'
11+
CatalogContent:
12+
- 'intro-to-ui-ux'
13+
- 'paths/front-end-engineer-career-path'
14+
---
15+
16+
**Postel's Law**, also called the Robustness Principle, originates from internet protocol design and is summarized as:
17+
18+
> "Be liberal in what you accept, and conservative in what you send." — Jon Postel
19+
20+
While originally intended for software protocols, this principle is widely applicable to _UX design_. It encourages flexibility and forgiveness in how systems handle user input, while still delivering predictable, high-quality output. It is especially important in forms, input validation, error handling, and accessibility.
21+
22+
## What It Means in UX
23+
24+
In UX, Postel's Law urges designers to:
25+
26+
- Accommodate varied user input formats and behaviors.
27+
- Handle edge cases gracefully rather than failing rigidly.
28+
- Provide consistent, accessible feedback without demanding perfection from the user.
29+
30+
This principle reduces user frustration by allowing users to complete tasks even when their input is not perfect — supporting a more forgiving, human-centered experience.
31+
32+
## Benefits of Postel's Law
33+
34+
- **Increased usability and task success rates:** Flexible input handling prevents user errors from turning into blockers.
35+
- **Greater inclusivity and accessibility:** Supporting different patterns of interaction helps users with diverse needs and tools.
36+
- **Stronger resilience in edge cases:** Systems are less likely to crash or behave unexpectedly under unusual input conditions.
37+
- **Higher trust in the interface:** When users feel understood and supported, they're more likely to engage fully with a product.
38+
39+
## When and Where to Apply Postel's Law
40+
41+
Postel's Law is especially useful when:
42+
43+
- **Designing forms or search bars:** Let users enter phone numbers with or without dashes, spaces, or country codes and still validate successfully.
44+
- **Handling user errors or mistyped data:** Allow minor spelling errors in search fields and suggest corrections instead of showing zero results.
45+
- **Designing multi-platform interactions:** Recognize inputs from different devices (e.g. touch, keyboard, voice) without rigid expectations.
46+
- **Building accessible interactions:** Ensure that screen readers, keyboard navigation, and alternate input methods receive appropriate, predictable responses.
47+
48+
## How to Apply It in UX Design
49+
50+
- **Support multiple input formats:** Whether it is date fields, email formats, or file names, accept a range of input styles and normalize them behind the scenes.
51+
- **Add real-time validation and correction:** Guide users gently with hints or auto-formatting instead of stopping them with hard errors.
52+
- **Make defaults and fallbacks work intelligently:** If input is missing or incorrect, offer smart defaults or safe assumptions to keep users moving forward.
53+
- **Use clear, non-blaming error messages:** Errors should inform, not shame. Make recovery easy and empathetic.
54+
- **Avoid punishing unexpected behavior:** Always consider how your system should respond to unusual but still valid input, and aim for graceful degradation.
55+
56+
![Diagram showing search engine input into multiple suggestive outputs](https://raw.githubusercontent.com/Codecademy/docs/main/media/postels-law-input-flexibility.png)
57+
58+
## Limitations of the Principle
59+
60+
- **Overly liberal input handling can hide issues or create security concerns:** For example, accepting any format without validation can increase the risk of incorrect or malicious input.
61+
- **Too much flexibility can reduce learnability:** Users may not know what to expect or how to interact consistently if there are no boundaries.
62+
- **It should never compromise clarity or control:** Flexibility should support users — not confuse them.
63+
64+
## Examples of Postel’s Law in Practice
65+
66+
- **Search bars that autocorrect typos or suggest queries:** Instead of showing “no results,” the system interprets the user’s intent and offers relevant alternatives.
67+
- **Date inputs that accept multiple formats:** Fields that let users type “August 27,” “27/08/2025,” or “08-27-25” without error.
68+
- **Phone number fields that strip spaces or symbols:** Systems that normalize input like “(123) 456-7890” into a clean format instead of blocking it.
69+
- **Form validation that corrects capitalization or spacing errors:** Automatically formatting names or addresses while still accepting varied input.
70+
- **E-commerce checkouts that accept minor address variations:** Matching “Street” with “St.” or recognizing mistyped zip codes to assist in delivery.
71+
- **Search filters that don’t break with wrong case or punctuation:** Recognizing that “UX Design” and “ux design” are the same for query purposes.
90.7 KB
Loading

0 commit comments

Comments
 (0)