Skip to main content

Compliance guide · WCAG

Understanding WCAG. Levels, versions and core accessibility principles.

WCAG, the Web Content Accessibility Guidelines, are the global standards from the W3C that help make websites usable for everyone. Here is how its principles, levels and versions fit together in practice.

  • W3CGlobal accessibility standards
  • POURFour core principles
  • A, AA and AAAThree conformance levels
  • WCAG 2.2The latest version, 2023

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines: global standards from the W3C that help make websites usable for everyone.

They guide designers and developers in removing barriers for people with different abilities, making the web easier to browse, read and interact with.

Below, we look at WCAG’s principles, levels and versions to see how everything fits together in practice.

Play video Play the video: WCAG 2.2 AA explained in simple terms

Video explainer · 2 min

WCAG 2.2 AA explained in simple terms

A quick video, under two minutes, that explains WCAG 2.2 AA and why it matters for accessibility.

By the tabnav team · November 12, 2025

What are the 4 principles of WCAG?

WCAG is built on four core ideas, known as POUR: Perceivable, Operable, Understandable and Robust. Together, they shape how people see, use and interact with your website.

  • P

    Perceivable

    Content should be presented in ways everyone can recognize and process, regardless of ability. Examples: alt text for images, captions for videos, strong color contrast and clear headings.

    In tabnav Academy: 1.1.1 Non-text content

  • O

    Operable

    Users must be able to navigate and interact with your site easily, even without a mouse. Examples: keyboard navigation, visible focus indicators, no flashing content and consistent menus.

    In tabnav Academy: 2.1.1 Keyboard

  • U

    Understandable

    Visitors should be able to read and use your site without confusion. Examples: clear language, predictable navigation, labeled forms and helpful error messages.

    In tabnav Academy: 3.3.2 Labels or instructions

  • R

    Robust

    Your website should work well across devices, browsers and assistive technologies. Examples: valid HTML, ARIA labels, screen reader testing and mobile-friendly design.

    In tabnav Academy: 4.1.2 Name, role, value

What are the WCAG conformance levels?

WCAG is divided into three levels of conformance: A, AA and AAA. Each level represents how accessible a website is and how closely it follows the guidelines.

  • A

    Level A

    Covers the most basic accessibility requirements that every website should meet.

  • AARecommended

    Level AA

    The recommended level in most laws and regulations. It ensures strong accessibility for a wider range of users.

  • AAA

    Level AAA

    The highest level of accessibility. It goes beyond standard compliance, though it’s not always practical for all content.

Most organizations aim for Level AA to stay compliant with accessibility laws and create a usable experience for everyone.

What are the different WCAG versions?

The Web Content Accessibility Guidelines have evolved over time to match new technologies and user needs. Each version builds on the previous one with more guidance and clarity.

  1. 1999

    WCAG 1.0

    The first version, now outdated. It focused mainly on basic web accessibility for early websites.

  2. 2008

    WCAG 2.0

    A major update that introduced the four principles: Perceivable, Operable, Understandable and Robust (POUR).

  3. 2018

    WCAG 2.1

    Added new success criteria for mobile accessibility, people with low vision and users with cognitive disabilities.

  4. 2023

    WCAG 2.2 Latest

    Expands coverage with nine new success criteria that improve accessibility for users with low vision, mobility challenges and cognitive differences.

Each new version builds on the one before it, so a site that meets WCAG 2.2 also conforms to WCAG 2.1 and 2.0. It’s always best to follow the most recent version to stay compliant and future-ready.

How can you check and improve WCAG accessibility?

Free accessibility tools can give a quick overview of your website’s WCAG status, showing common issues like missing alt text or low contrast. Still, automated scans alone don’t catch everything.

The best results come from combining quick scans with human testing. This ensures your website truly meets WCAG 2.2 AA and works well for every user.

Start by running a quick scan with the tabnav Free Accessibility Checker to see how accessible your site really is.

Keep learning

How tabnav helps

Meet WCAG 2.2 AA with tabnav. Scan, fix, monitor and document, with tools and experts.

Free accessibility checker

How does your website score against WCAG?

Enter your website address and get a free report on WCAG 2.2 AA issues, with code-level findings and a clear explanation of each one.

Free. The scan can take a few minutes.

FAQ

WCAG questions, answered.

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines. They are global standards from the W3C that help make websites usable for everyone by removing common barriers.

What are the 4 principles of WCAG?

WCAG is built on four principles known as POUR: Perceivable, Operable, Understandable, and Robust. They guide how people see, use, and interact with content.

What are the WCAG conformance levels?

WCAG has three conformance levels: A, AA, and AAA. Level A covers basic accessibility, Level AA meets most regulations, and Level AAA provides the highest accessibility where possible.

What are the different WCAG versions?

WCAG has evolved through versions 1.0, 2.0, 2.1, and 2.2. Each builds on the last, and meeting WCAG 2.2 means you also conform to earlier versions.

How can you check and improve WCAG accessibility?

Combine automated scans with human testing to meet WCAG 2.2 AA. Start by running a quick scan with the tabnav Free Accessibility Checker to see how accessible your site really is.

Need help meeting WCAG 2.2 AA?

Our accessibility specialists audit, fix and document your site, so you know exactly where you stand.

WCAG 2.2 AA explained in simple terms