disability: Visual
Promotes web accessibility for people with blindness, low vision, or color blindness.
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.
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.
4.1.2 Name, Role, Value
Interactive elements must have a clear name (what it is), the correct role (what it does), and any current value or state, so that assistive technologies can interpret and interact with them correctly.
4.1.3 Status Messages
Status updates (like “form sent” or “5 items in cart”) must be coded using proper roles (like role="status" or role="alert"), be detectable by assistive technologies, and not require moving focus.
