Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 4.1: Compatible
4.1.1 Parsing (Obsolete) Level A
This criterion is obsolete in WCAG 2.2 and always passes. It was originally about valid HTML markup but modern browsers and assistive technologies handle parsing errors gracefully. Crucible Scan tracks this criterion but marks it as automatically passing.
4.1.2 Name, Role, Value Level A
For all user interface components, the name and role must be programmatically determinable, and states, properties, and values must be programmatically settable. Crucible Scan checks for missing ARIA attributes, incorrect roles, and form controls without accessible names.
How to fix: Ensure custom interactive elements use appropriate ARIA roles and properties. Use native HTML elements where possible (a <button> is better than a <div role="button">). Provide accessible names via aria-label, aria-labelledby, or visible labels.
4.1.3 Status Messages Level AA
Status messages that provide information about success, errors, or progress must be programmatically determinable through role or properties so that assistive technologies can present them without receiving focus. Use role="status", role="alert", or ARIA live regions.