Understanding WCAG 2.2 Success Criteria: A Complete Guide
Creating an accessible website is no longer just a best practice — it is a responsibility. Millions of people rely on accessible digital experiences to browse websites, complete transactions, access services, and interact online.
The Web Content Accessibility Guidelines (WCAG) 2.2 provide organizations with a clear framework to make websites and applications more inclusive. These guidelines help developers, designers, content creators, and businesses remove barriers and create digital experiences that work for everyone.
But what exactly are WCAG 2.2 success criteria, and how do they impact your website?
This guide explains the key WCAG 2.2 requirements, the latest improvements, and practical steps organizations can take to improve accessibility.
What Are WCAG 2.2 Success Criteria?
WCAG success criteria are measurable requirements that help determine whether a website meets accessibility standards. Each success criterion explains a specific accessibility requirement and is assigned one of three conformance levels:
Level A — Essential Accessibility Requirements
Level A criteria address the most critical barriers. Websites that fail Level A requirements may prevent some users from accessing content completely. Examples include:
- Providing alternative text for images
- Ensuring keyboard navigation works
- Using proper page structure and headings
Meeting Level A is the minimum requirement for an accessible website.
Level AA — The Recommended Accessibility Standard
Level AA addresses the biggest accessibility challenges and is the target level recommended for most organizations. It includes requirements related to:
- Colour contrast
- Form accessibility
- Keyboard usability
- Navigation consistency
- Error identification
Many accessibility laws and regulations, including AODA requirements in Ontario, reference WCAG Level AA as the expected standard.
Level AAA — The Highest Accessibility Level
Level AAA provides advanced accessibility improvements. While organizations are not usually required to meet all Level AAA criteria, these enhancements create a more inclusive experience. Examples include:
- Sign language interpretation
- Simplified language options
- Enhanced content readability
What Changed in WCAG 2.2?
WCAG 2.2 builds on WCAG 2.1 by improving accessibility for people with cognitive disabilities, mobile users, and people who navigate websites using keyboards or assistive technologies. WCAG 2.2 introduced nine new success criteria:
| Success Criterion | Level | Purpose |
|---|---|---|
| Focus Appearance | AA | Makes keyboard focus indicators easier to see |
| Focus Not Obscured (Minimum) | AA | Prevents focused elements from being hidden |
| Focus Not Obscured (Enhanced) | AAA | Provides stronger focus visibility |
| Dragging Movements | AA | Provides alternatives to drag-only actions |
| Target Size (Minimum) | AA | Improves touch target usability |
| Consistent Help | A | Makes support options easier to find |
| Redundant Entry | A | Prevents users from repeatedly entering information |
| Accessible Authentication (Minimum) | AA | Removes unnecessary barriers during login |
| Accessible Authentication (Enhanced) | AAA | Provides stronger authentication accessibility |
These updates focus on real-world usability challenges that many users experience every day.
Key WCAG 2.2 Success Criteria Explained
1. Focus Appearance: Make Keyboard Navigation Visible
Many users navigate websites without a mouse. They depend on the keyboard, especially the Tab key, to move through links, buttons, and forms. WCAG 2.2 requires websites to provide a clear and visible focus indicator. A user should always know:
- Which element currently has focus
- Where they are on the page
- What action they can take next
Common Issue: A website removes the default browser outline without adding a replacement focus style.
Better Approach: Create a strong visual focus indicator that works for both keyboard and mouse users.
2. Focus Not Obscured: Keep Important Elements Visible
Modern websites often use:
- Sticky headers
- Floating banners
- Cookie notifications
- Chat widgets
These elements can accidentally cover the item currently selected by keyboard users. WCAG 2.2 requires focused elements to remain visible.
Example: A user tabs to a “Submit Form” button, but a sticky footer hides the button. The user cannot see what they selected.
Solution: Design layouts that keep interactive elements visible during keyboard navigation.
3. Target Size: Improve Mobile Accessibility
Small buttons and links create challenges for users with:
- Limited mobility
- Hand tremors
- Mobile users
- Older adults
WCAG 2.2 introduces minimum target size requirements to make interactive elements easier to select. Improve accessibility by:
- Increasing button size
- Adding enough spacing between links
- Avoiding crowded navigation menus
4. Dragging Movements: Provide Alternative Controls
Some websites require users to drag objects, sliders, or cards. However, dragging can be difficult for users with motor disabilities. WCAG 2.2 requires an alternative method when dragging is necessary.
Example: Instead of only allowing users to drag a slider:
- Provide plus and minus buttons
- Allow keyboard adjustments
- Support alternative input methods
5. Accessible Authentication: Remove Login Barriers
Authentication should not create unnecessary accessibility barriers. Common problems include:
- Requiring users to remember complex information
- Blocking password managers
- Using inaccessible CAPTCHA systems
WCAG 2.2 encourages authentication methods that support all users. Better options include:
- Password managers
- Copy and paste functionality
- Accessible multi-factor authentication
- Biometric authentication
Why WCAG 2.2 Compliance Matters for Businesses
Following WCAG 2.2 helps organizations create better experiences while reducing accessibility risks.
Improve Customer Experience
Accessible websites allow more people to interact with your products and services.
Expand Your Audience
Accessibility helps businesses reach:
- People with disabilities
- Older users
- Mobile users
- Users with temporary limitations
Reduce Compliance Risks
Many organizations must meet accessibility requirements under regulations such as:
- AODA (Accessibility for Ontarians with Disabilities Act)
- ADA (Americans with Disabilities Act)
- European Accessibility Act
Strengthen Your Brand Reputation
Organizations that prioritize accessibility demonstrate inclusion and social responsibility.
How to Start Preparing Your Website for WCAG 2.2
Improving accessibility does not happen overnight. A structured approach helps organizations achieve compliance efficiently.
1. Perform an Accessibility Audit
Identify current accessibility issues using :
- Automated testing tools
- Manual keyboard testing
- Screen reader testing
- Code reviews
Automation finds common issues, but manual testing discovers real user barriers.
2. Fix High-Impact Accessibility Issues First
Prioritize problems that prevent users from completing tasks. Start with:
- Missing alternative text
- Keyboard navigation problems
- Poor colour contrast
- Inaccessible forms
- Missing focus indicators
3. Test with Assistive Technologies
Validate your improvements using:
- NVDA
- JAWS
- VoiceOver
- TalkBack
Real accessibility testing ensures your website works beyond automated scans.
4. Train Your Team
Accessibility should become part of your development process. Educate:
- Designers
- Developers
- Content creators
- QA teams
Building accessibility into your workflow prevents future issues.
WCAG 2.2 Success Criteria Checklist
Before launching your website, verify:
- All images include meaningful alternative text
- Users can navigate using only a keyboard
- Focus indicators are visible
- Buttons and links are easy to select
- Forms provide clear instructions and errors
- Colour contrast meets WCAG requirements
- Authentication processes support accessibility
- Content works with screen readers
Final Thoughts
WCAG 2.2 provides organizations with practical guidance to create websites that are more usable, inclusive, and accessible. Accessibility is not only about meeting technical requirements — it is about removing barriers and ensuring everyone can participate equally in the digital world.
By understanding WCAG 2.2 success criteria and integrating accessibility into your design, development, and testing processes, your organization can create better experiences for all users.