The Web Content Accessibility Guidelines (WCAG) are the global standards to make web content accessible to everyone, including people with disabilities, to build an inclusive society. WCAG is standing on four core pillars known as POUR (Perceivable, Operable, Understandable, Robust). WCAG continues to update itself according to the global technological advancements by complying with the World Wide Web Consortium’s (W3C) Web Accessibility Initiative (WAI). These guidelines provide a framework for web developers to create accessible websites, and conformance levels (A, AA, AAA) are used to indicate the degree of accessibility. At the moment, the latest version of WCAG is Web Content Accessibility Guidelines (WCAG) 2.2, also known as WCAG 2.2.
Guidelines are advisory frameworks or recommended practices intended to help individuals or organizations meet a desired objective or quality level. They carry no legal force on their own, meaning no one is obligated to follow them, so we usually refer to conforming to guidelines. Laws, however, are enforceable rules created by governments or legal authorities, and individuals or organizations must comply with them.
Although the WCAG is not legally enforceable on its own, it is widely recognized as the global standard for digital accessibility. Many accessibility laws and regulations cite WCAG as the minimum benchmark, which is why people often use the term “WCAG compliance” interchangeably with “WCAG conformance.”
What’s New in WCAG 2.2?
WCAG 2.2 introduces nine new success criteria. These focus on accessibility for web users with low vision, cognitive and learning disabilities, and motor disabilities, including access on touch-screen devices.
How to Meet WCAG 2.2?
WCAG provides detailed technical requirements and success benchmarks for website owners, designers, and developers. These standards guide teams in creating websites that support users with diverse needs, including those who rely on assistive technologies such as screen readers or keyboard-only navigation.
Under WCAG 2.2, websites are expected to include elements such as:
- High color contrast between the text and its background
- Meaningful alt text for images and graphics
- Captions and transcripts for video content
- Clear and accessible labels for form fields
- Descriptive titles or tags for navigation links and buttons
Nearly all digital accessibility laws around the world are built on WCAG principles.
WCAG 2.2 AA Accessibility Standards
Organizations and their design teams should understand the WCAG 2.2 standards and routinely review their digital content to ensure it aligns with accessibility expectations.
There are three primary motivations for pursuing WCAG alignment:
- Expanding access for all users.
- Improving website usability and overall performance.
- Meeting national and international legal requirements.
Inclusion
Accessible design removes obstacles that prevent people from effectively using a website. It broadens reach to individuals with visual, motor, and cognitive disabilities, as well as people browsing on different devices such as smartphones, tablets, or assistive technologies.
Disability is a universal experience. More than one billion people globally live with a disability, and many more encounter temporary or situational limitations due to aging, injury, illness, or environmental conditions.
Website Optimization Through Accessibility
WCAG-compliant web content leads to a well-optimized website with improved structure and readability. This enhances user experience, boosts website traffic, improves conversion performance, increases revenue, and reduces bounce and abandonment rates.
For example, WCAG requires meaningful alt text for images and transcripts for multimedia assets. On e-commerce sites, this supports inclusive shopping experiences for visually impaired users and strengthens SEO through well-crafted metadata.
Compliance Requirements
WCAG serves as the foundation for most digital accessibility regulations worldwide. Failure to comply can result in significant legal exposure, including fines and civil lawsuits.
In the United States, Section 508 mandates WCAG 2.0 compliance for federal agencies and contractors. Court rulings and Department of Justice enforcement actions indicate that private businesses must also meet WCAG requirements under Title III of the Americans with Disabilities Act (ADA). Numerous settlements confirm that WCAG is the accepted standard.
Internationally:
- The European Union’s EN 301 549 requires WCAG 2.1 Level AA.
- Ontario’s AODA mandates WCAG 2.0 Level AA.
- Australia’s National Transition Strategy requires government agencies to comply with WCAG, with private sector compliance recommended under the DDA.
- Israel’s IS 5568 requires most businesses to adopt WCAG standards.
With so many regulations referencing WCAG, meeting the guidelines ensures compliance with related laws.
WCAG 2.2 Level AA Requirements
Understanding WCAG Versions
To understand terms like “WCAG 2.2 AA” or “WCAG 2.2 AAA,” it’s helpful to look at how the guidelines are structured.
The Web Content Accessibility Guidelines (WCAG) have been developed by the World Wide Web Consortium (W3C) for nearly three decades and have gone through multiple updates since the now-retired WCAG 1.0. Each version is shaped by contributions from global organizations, accessibility experts, academics, W3C staff, and the wider public. UserWay team members also participate in the standards-development process.
WCAG Version Timeline:
- WCAG 1.0 – May 5, 1999 (retired)
- WCAG 2.0 – December 2008
- WCAG 2.1 – June 5, 2018
- WCAG 2.2 – October 2023
Most accessibility laws reference WCAG 2.0 or 2.1, with WCAG 2.1 adding 17 new success criteria. WCAG 2.2 builds on 2.1 with additional guidance for mobile accessibility, users with cognitive or learning disabilities, and individuals with low vision. As of August 2023, WCAG 2.2 is the most current version.
This update continues the long-standing WCAG principles designed to support people with visual, auditory, motor, and cognitive disabilities. Work is already underway on WCAG 3.0, the next major evolution of the standard.
WCAG Levels of Conformance
With the versions clarified, we can explain what it means when someone says a website must meet WCAG 2.2 AA.
WCAG defines three conformance levels: A, AA, and AAA. Each level builds on the previous one, with increasingly robust accessibility requirements. The higher the level, the wider the range of disabilities that are supported.
Level A – Basic Accessibility
The foundational level that removes the most critical accessibility barriers. Example: Adding alt text so screen readers can describe images for users with visual impairments.
Level AA – Enhanced Accessibility
A more comprehensive level that includes all Level A criteria plus additional requirements for a wider range of users. Example: Providing audio descriptions for videos so people who are blind or have low vision can fully understand visual content.
Level AAA – Highest Accessibility
The highest standard, offering the strongest support for users with diverse disabilities. Example: Providing transcripts, audio descriptions, sign language interpretation, and detailed audio narration for multimedia content.
The key differences lie in the depth of accessibility each level provides. Level A addresses basic needs, Level AA expands coverage, and Level AAA offers the most inclusive experience. While Level AAA is ideal, it is not always feasible for all content types, which is why most regulations require Level A and AA compliance.
WCAG’s success criteria determine whether a website meets Level A, AA, or AAA requirements. For example, navigation-related rules under Success Criterion 1.2 become progressively more detailed as they move from A to AAA.
Read more: What Is the Difference Between WCAG A, AA, and AAA?
4 WCAG Principles
WCAG’s four principles outline what every accessible website should aim for. They serve as a blueprint for meeting the needs of users with different abilities:
- Perceivable: Make information visible, audible, or otherwise detectable so all users can take in the content.
- Operable: Ensure that buttons, forms, menus, and navigation can be used by everyone, even people who rely on keyboard navigation or assistive technologies.
- Understandable: Present content in a clear, predictable manner so users know what to do and how to move through the site.
- Robust: Build websites that work well across browsers, devices, and assistive technologies, both now and as technology continues to advance.
13 High-Level Guidelines in WCAG Principles
WCAG includes 13 guidelines that align with the four core principles described earlier. These guidelines act as actionable steps that help translate broader accessibility goals into measurable requirements. Below is an overview of each guideline, organized by the principle it supports.
Perceivable
- Text Alternatives – Provide text-based equivalents for non-text elements, such as image descriptions or form labels, so users who cannot see or interact with visual content can still understand the information.
- Time-Based Media – Offer synchronized alternatives such as alt text, transcripts, and captions for audio and video content.
- Adaptable – Ensure that content can adjust to different display sizes and formats without losing meaning or functionality.
- Distinguishable – Present content with clear spacing, readable text sizes, and strong contrast between foreground and background elements.
Operable
- Keyboard Accessible – Make all functionality available using a keyboard alone, without interfering with common keystrokes or shortcuts.
- Enough Time – Provide sufficient time for users to read, interact with, or respond to time-based content.
- Seizures and Physical Reactions – Avoid flashing or animated content that could trigger seizures or harmful physical responses.
- Navigable – Offer logical, consistent navigation. Use headings, subheadings, and structured menus to help users find content easily.
- Input Modalities – Support multiple input methods, such as voice control, switch devices, or eye tracking, beyond just keyboard and mouse.
Understandable
- Readable – Write content in clear, plain language. Avoid unnecessary jargon or acronyms, and provide definitions when specialized terms are required.
- Predictable – Ensure the website behaves in consistent, expected ways, such as using standard scroll directions and familiar placement of navigation elements.
- Input Assistance – Assist users in completing forms by supporting browser autofill, error prevention, and correction mechanisms.
Robust
- Compatible – Build content that works reliably across a broad range of browsers, devices, and assistive technologies, both now and in the future.
Accessibility is an On-going Process
Achieving digital accessibility is an ongoing and ever-evolving effort. As user needs shift and technologies advance, laws and WCAG success criteria continue to adapt. This means organizations must regularly review and update their digital content. Accessibility is not a one-time task but a continuous commitment.
The good news: with the right tools and guidance, meeting WCAG 2.2 AA standards is entirely within reach. Explore our solution to see how Level Access can help you strengthen your digital experience and engage a broader audience.
