WCAG in Plain English

Abbreviations and acronyms should be avoided when possible, or explained the first time they appear.

If content requires reading skills above lower secondary education (around 9th grade), provide a simpler version, a summary, a visual aid, or a spoken version to help with understanding.

If a word can be pronounced in different ways with different meanings, the intended meaning must be clarified to avoid confusion or ambiguity.

Errors and validation must be clearly identified and described in text, not just visually (like color or highlighting).

Errors and validation messages must show text that explains the problem and gives suggestions for how to fix it (like “enter at least 8 characters”).

Before submitting important actions (like payments or legal forms), the form must allow reviewing the input, correcting mistakes, or confirming.

Provide additional help (like text instructions, help links, or tooltips) when label alone might be ambiguous or confusing.

Before submitting, all forms must allow reviewing the input, correcting mistakes, or confirming.