addition success criterion

https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-4-1-3-status-messages-level-aa/ WCAG2.1 Addition - Success Criterion 4.1.3: Status Messages (Level AA) - AccessibilityOz Status messages should be programmatically determinable through appropriate roles or properties, allowing assistive technologies to present the information to... addition success criterion level aa status messages accessibilityoz https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-1-4-13-content-on-hover-and-focus-level-aa/ WCAG2.1 Addition - Success Criterion 1.4.13: Content on Hover and Focus (Level AA) - AccessibilityOz When additional content becomes visible upon receiving pointer hover or keyboard focus (and subsequently becomes hidden when these triggers are removed) it... addition success criterion level aa content hover focus https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-1-4-11-non-text-contrast-level-aa/ WCAG2.1 Addition - Success Criterion 1.4.11: Non-Text Contrast (Level AA) - AccessibilityOz This requirement applies to user interface components and their states, except for inactive components or when the appearance is determined by the user agent... addition success criterion non text level aa contrast accessibilityoz https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-2-5-3-label-in-name-level-a/ WCAG2.1 Addition - Success Criterion 2.5.3: Label in Name (Level A) - AccessibilityOz Ensure that the control's text label and accessible name are the same where possible. This practice supports both visual users and those interacting through... addition success criterion label name level accessibilityoz https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-1-3-5-identify-input-purpose-level-aa/ WCAG2.1 Addition - Success Criterion 1.3.5: Identify Input Purpose (Level AA) - AccessibilityOz The purpose of each input field is to clearly define its intended function. Collecting user information can be automated when the input field’s label correctly... addition success criterion level aa identify input purpose https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-1-4-10-reflow-level-aa/ WCAG2.1 Addition - Success Criterion 1.4.10: Reflow (Level AA) - AccessibilityOz The purpose of this standard is to ensure that content remains readable and accessible on mobile devices. In simpler terms, it is about making sure your... addition success criterion level aa reflow accessibilityoz https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-2-5-4-motion-actuation-level-a/ WCAG2.1 Addition - Success Criterion 2.5.4: Motion Actuation (Level A) - AccessibilityOz The goal here is to remove the need for users to manually move their mobile devices. Features such as shake-to-undo are problematic because they can be... addition success criterion motion actuation level accessibilityoz

Robuta