WCAG 2.2 adds success criteria while retaining its conformance model; a valid claim still requires traceable scope and complete testing.
The additional accessibility questions in WCAG 2.2
WCAG 2.2 extends WCAG 2.1 while retaining the four principles and conformance levels. The added criteria address visible and unobscured focus, dragging alternatives, target size, consistent help, redundant entry and accessible authentication. Upgrade review therefore needs to test interaction paths, not only static page markup.[S1]
WCAG 2.2 retains the four principles and conformance structure used in earlier WCAG versions while adding nine success criteria. The additions address visible focus, obscured focus, dragging alternatives, target size, consistent help, redundant entry and accessible authentication. In education services, these issues often arise in sign-in, navigation, forms, assessments and support rather than on a single public page.[S1]
New success criteria and the retained conformance model
A traceable record identifies the exact success criterion, level, page or process, testing method, result, environment and remediation. Authentication and assessment journeys deserve end-to-end testing because a barrier in one required step prevents completion even when surrounding content passes.[S1]
A conformance record identifies the WCAG version, claimed level, page or process scope and testing method. It then maps findings to the relevant success criteria. Manual keyboard, focus-order, zoom, pointer and authentication testing complements automated checks. Evidence from disabled users can reveal practical barriers, but a usability report must still be connected to the specific conformance criterion when a formal claim is made.[S1]
The added criteria can be examined in the real states of a service, including validation errors, time-limited tasks, sticky headers, authentication and repeated data entry. Screenshots alone rarely establish keyboard order or announced meaning. A reproducible finding includes the interaction, input method, expected result and observed barrier, followed by evidence that the repaired state was tested again.[S1]
Testing complete learner journeys
Conformance applies to full pages and complete processes within the declared web-content scope. Mobile applications, hardware and non-web documents can be governed by related standards or law. Third-party content needs an explicit treatment under the conformance model.[S1]
Complete processes matter because a learner may pass through multiple pages, embedded components and third-party services to perform one task. Registration, payment, course access, content, assessment and help can each affect the result. A claim limited to selected templates or a public marketing site needs to state that boundary plainly and cannot be read as covering the entire learning service.[S1]
Version, sampling and usability limits
A high automated score cannot cover all criteria or user needs. WCAG conformance does not resolve the accuracy of learning content, the accessibility of customer support or the legality of an accessibility statement. Claims need current version and scope information.[S1]
WCAG 2.2 supersedes 2.1 as a W3C Recommendation but does not invalidate every earlier test result. The version claimed must match the evidence. Sampling leaves residual uncertainty, and a technically conforming interaction can still be difficult to understand. WCAG evidence also does not decide legal coverage, educational quality or the accessibility of non-web elements outside the tested scope.[S1]
WCAG 2.2 evidence for ICEQC review
ICEQC treats WCAG 2.2 as external technical evidence, not as an ICEQC-owned standard. W3C does not endorse the resulting analysis or a certification subject. The article predates ICEQC’s published edition and carries no retrospective clause link.
ICEQC may rely on WCAG 2.2 as an external technical reference when digital accessibility is within scope. W3C conformance and ICEQC certification remain distinct statements. The historical article contains no later ICEQC criterion and does not imply W3C review or endorsement.