WCAG 2.1 vs WCAG 2.2: What Changed and Does It Affect Universities?
WCAG 2.2 adds nine criteria with distinct A, AA and AAA levels. Compare them accurately and plan around your institution’s actual technical and legal requirements.
WCAG 2.2 was published as a W3C Recommendation on 5 October 2023. It adds nine success criteria to WCAG 2.1 and removes the obsolete 4.1.1 Parsing criterion. The other 2.0 and 2.1 criteria are essentially retained.
The new criteria and their levels
At Level A:
- 3.2.6 Consistent Help
- 3.3.7 Redundant Entry
At Level AA:
- 2.4.11 Focus Not Obscured (Minimum)
- 2.5.7 Dragging Movements
- 2.5.8 Target Size (Minimum)
- 3.3.8 Accessible Authentication (Minimum)
At Level AAA:
- 2.4.12 Focus Not Obscured (Enhanced)
- 2.4.13 Focus Appearance
- 3.3.9 Accessible Authentication (Enhanced)
Read W3C's explanation and links to the full criteria for their scope and exceptions. For example, Target Size (Minimum) includes a 24 by 24 CSS pixel requirement with spacing and other exceptions; it is not a universal rule that every visible link must be that size.
Review complete institutional journeys
Evaluate course publishing, student authentication, forms, help mechanisms and interactive assessments. A modern CSS framework or an SSO login does not prove that those journeys meet every applicable criterion.
Include keyboard operation, pointer alternatives, focus visibility and the actual authentication path. Record the scope of automated checks and retain the manual findings they cannot establish.
Separate the standard from the legal obligation
The US DOJ Title II web and mobile rule specifies WCAG 2.1 Level AA for covered content. Current compliance dates are April 26, 2027 for public entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. Student enrolment does not set the cohort. Consult DOJ guidance for applicability and exceptions.
Australian education obligations arise under the DDA 1992 and DSE 2005. Meeting a WCAG target alone is not a blanket determination of DDA compliance, and there is no matching federal US-style deadline. Review the institution's duties and procurement requirements with its accessibility and legal teams.
Build a practical improvement plan
Set the required standard and content scope first. Inventory barriers, assign owners and prioritize student impact while retaining a route to address individual access needs. Where the institution adopts 2.2 AA, include the new A and AA criteria in acceptance checks; do not mistake the new AAA criteria for AA requirements.
Aelira Core is beta and supports automated checks and eligible partial fixes. It does not establish complete WCAG coverage or replace manual evaluation. Inspect the current evidence and limitations when choosing an institutional workflow.
Aelira Team
•Accessibility EngineersThe Aelira team is building beta accessibility tools for higher education. Institutions can evaluate selected checks and partial fixes on their own files, with human review required before publication.
Related Articles
What Procurement Should Demand in an Accessibility AI Contract: A Due-Diligence Checklist
Eleven proposed due-diligence terms for AI-assisted accessibility procurement. Adapt acceptance, evidence, data-flow and exit commitments to institutional needs.
FERPA, Cloud Inference, and the Data-Sovereignty Question Procurement Should Be Asking
Map document and inference data flows, review FERPA conditions and contract terms, and verify what a self-hosted deployment actually sends outside the institution.
What Accessibility Scores Establish — and Why Review Records Matter
Use scanner scores within their measured scope, and retain review records tied to exact files. Neither a score nor an audit trail guarantees conformance or an investigation outcome.