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...
level aawcag2additionsuccesscriterion
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...
level awcag2additionsuccesscriterion
https://www.accessibilityoz.com/2025/12/all-wcag2-1-additions-blog-posts/
All WCAG2.1 Additions Blog Posts - AccessibilityOz
Dec 1, 2025 - Recently we ran a presentation on WCAG2.1 and WCAG2.2 additions to WCAG2. Since then we have been publishing these additions - one success criterion a day....
blog postswcag2additionsaccessibilityoz
https://lists.w3.org/Archives/Public/public-wcag2-techs/2017Mar/author.html
public-wcag2-techs@w3.org from March 2017: by author
by authorpublicwcag2techsw3
https://www.accessibilityoz.com/training/wcag2-content-authors-managers/
WCAG2.2 for Content Authors and Managers - AccessibilityOz
Aug 5, 2025 - All our courses are run online on Microsoft Teams or Zoom. This course is available as part of Accessibility Day or customised to your organisation. See our...
wcag2contentauthorsmanagersaccessibilityoz
https://www.accessibilityoz.com/2025/11/wcag2-1-addition-success-criterion-1-3-4-orientation-level-aa/
WCAG2.1 Addition - Success Criterion 1.3.4: Orientation (Level AA) - AccessibilityOz
Mobile content should be usable in any orientation. In some cases, the mobile device can be affixed, set to a specific orientation and cannot be rotated by the...
level aawcag2additionsuccesscriterion
https://lists.w3.org/Archives/Public/public-wcag2-techs/2012Jul/thread.html
public-wcag2-techs@w3.org from July 2012: by thread
by threadpublicwcag2techsw3
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...
level awcag2additionsuccesscriterion
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...
status messageslevel aawcag2additionsuccess
https://www.webaxe.org/category/wcag2/
wcag2 – Web Axe
web axewcag2
https://lists.w3.org/Archives/Public/public-wcag2-techs/2013Aug/author.html
public-wcag2-techs@w3.org from August 2013: by author
by authorpublicwcag2techsw3
https://lists.w3.org/Archives/Public/public-wcag2-techs/2015Jul/subject.html
public-wcag2-techs@w3.org from July 2015: by subject
by subjectpublicwcag2techsw3
https://lists.w3.org/Archives/Public/public-wcag2-techs/2014Jun/
public-wcag2-techs@w3.org from June 2014: by date
by datepublicwcag2techsw3