WCAG version: 2.0
Collection of success criterion published in WCAG version 2.0 in 2008.
3.2.3 Consistent Navigation
Navigation elements (like menus, links, search) must appear in the same place and order across pages.
3.2.4 Consistent Identification
Elements with the same function must look, behave, and be labeled the same way across pages.
3.2.5 Change on Request
Major changes (like open dialog, navigate, submit) must only happen when explicitly requested.
3.3.1 Error Identification
Errors and validation must be clearly identified and described in text, not just visually (like color or highlighting).
3.3.2 Labels or Instructions
Form fields must have clear labels or instructions to avoid confusion and help complete the input correctly.
3.3.3 Error Suggestion
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”).
3.3.4 Error Prevention (Legal, Financial, Data)
Before submitting important actions (like payments or legal forms), the form must allow reviewing the input, correcting mistakes, or confirming.
3.3.5 Help
Provide additional help (like text instructions, help links, or tooltips) when label alone might be ambiguous or confusing.
3.3.6 Error Prevention (All)
Before submitting, all forms must allow reviewing the input, correcting mistakes, or confirming.
4.1.1 Parsing
This used to require HTML with proper structure and no critical markup errors (like missing tags or duplicate IDs). The requirement is removed but still helps with compatibility.