guideline: Compatible
Maximize compatibility with assistive tools and browsers.
WCAG 2.0, 2.1
Level A
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.
WCAG 2.0, 2.1, 2.2
Level A
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.
WCAG 2.0, 2.1, 2.2
Level AA
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.
