Robust
3 articles
WCAG 4.1.2: Name, Role, Value
WCAG 4.1.2 requires that all user interface components have a programmatically determinable name and role, and that states, properties, and values can be both read and set by assistive technologies. This ensures screen readers and other tools can accurately identify, describe, and interact with every element on the page.
WCAG 4.1.3: Status Messages
WCAG 4.1.3 requires that status messages — such as form submission confirmations, error notifications, and cart updates — be programmatically determinable through role or property so assistive technologies can announce them without requiring the user to move focus. This ensures users who rely on screen readers receive important feedback even when focus does not shift to the message.
WCAG 4.1.1: Parsing (Deprecated in WCAG 2.2)
WCAG 4.1.1 Parsing requires that web content be free of major HTML/XML errors—such as duplicate IDs—that could cause assistive technologies to misinterpret or fail to process the page. Although deprecated in WCAG 2.2, the underlying axe-core rules remain active and violations still indicate real accessibility risk.