이해 가능성: 읽기 쉽고 예측 가능한가요?

Understandable is the third WCAG principle: people must be able to read your content and predict how the interface behaves.

Plain, clear wording helps people with cognitive differences, non-native speakers, and tired readers. Simple beats clever for readability. 📖

Set the page language so screen readers use the right voice and pronunciation. One small attribute makes speech sound correct.

Jargon and abbreviations confuse readers. Spell out terms or define them so meaning stays clear and understandable to all.

Things should act the way users expect. Focusing a field should not suddenly submit a form. Surprise breaks predictability.

Keep menus and links in the same place across pages. Consistency lets people learn your site once and reuse that knowledge.

Call the same thing by the same name everywhere. If it is a Cart on one page, do not name it Basket on another. Labels should match.

Good labels and hints stop mistakes before they happen. Telling users a date format up front prevents a frustrating error later.

When something goes wrong, say what and where in plain text. A clear error message names the field and how to fix it.

Do not just flag a problem; offer a way out. Suggesting a valid format or value turns a dead end into a quick correction.

Ask of every screen: can people read this and guess what happens next? If they are surprised or confused, it is not understandable.

Let us test the Understandable principle.

You learned that Understandable means content reads clearly and behaves predictably: plain language, set the lang, consistency, and helpful errors. 💡