---
title: WCAG 2.0 vs 2.1 vs 2.2 - How is it different for documents?
description: Compare WCAG 2.0, 2.1, and 2.2 for document accessibility and understand how these updates impact digital content compliance in Australia.
image: https://meetaandi.com/hubfs/6.png
---

[Skip to content](https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents#main-content)

[![](https://meetaandi.com/hs-fs/hubfs/MeetAandi-Logo-web.png?width=248&height=50&name=MeetAandi-Logo-web.png)](https://meetaandi.com)

- Products
  
  Show submenu for Products 
  
    - [Video Accessibility](https://meetaandi.com/video-accessibility)
    - [Document Accessibility](https://meetaandi.com/document-accessibility)
    - [Coach Aandi](https://meetaandi.com/coach-aandi-feb-2026)
    - [Accessible Design](https://meetaandi.com/writing-and-designing-for-accessibility)
    - [Accessibility Training](https://meetaandi.com/accessibility-training)
    - [DE&I Consulting](https://meetaandi.com/dei-consulting)
    - [Music Accessibility](https://meetaandi.com/music-accessibility)
- Video Tool
  
  Show submenu for Video Tool 
  
    - [Upload video](https://www.meetaandi.com/video-tool?#uploadVideos)
    - [Manage videos](https://www.meetaandi.com/video-tool?#manageVideos)
- [Pricing](https://meetaandi.com/price-guide)
  
  Show submenu for Pricing 
  
    - [Legacy Documents](https://meetaandi.com/legacy-packages-v1)
    - [Government Glow-up](https://meetaandi.com/government-glow-up)
    - [Access for Every Brain](https://meetaandi.com/access-for-every-brain)
- [About](https://meetaandi.com/about)
- [Blog](https://meetaandi.com/blog)
- [Login](https://www.meetaandi.com/video-tool?#login)
- Profile
  
  Show submenu for Profile 
  
    - [Manage Credits](https://www.meetaandi.com/video-tool?#credits)
    - [Logout](https://www.meetaandi.com/video-tool?#logout)
- Admin
  
  Show submenu for Admin 
  
    - [Inbox](https://www.meetaandi.com/video-tool?#inbox)
    - [Manage Blog](https://www.meetaandi.com/video-tool?#adminBlog)
    - [Manage Credits](https://www.meetaandi.com/video-tool?#adminCredits)
    - [Dashboard](https://www.meetaandi.com/video-tool?#adminDashboardMain)

Open main navigation

Close main navigation

- Products
  
  Show submenu for Products 
  
    - [Video Accessibility](https://meetaandi.com/video-accessibility)
    - [Document Accessibility](https://meetaandi.com/document-accessibility)
    - [Coach Aandi](https://meetaandi.com/coach-aandi-feb-2026)
    - [Accessible Design](https://meetaandi.com/writing-and-designing-for-accessibility)
    - [Accessibility Training](https://meetaandi.com/accessibility-training)
    - [DE&I Consulting](https://meetaandi.com/dei-consulting)
    - [Music Accessibility](https://meetaandi.com/music-accessibility)
- Video Tool
  
  Show submenu for Video Tool 
  
    - [Upload video](https://www.meetaandi.com/video-tool?#uploadVideos)
    - [Manage videos](https://www.meetaandi.com/video-tool?#manageVideos)
- [Pricing](https://meetaandi.com/price-guide)
  
  Show submenu for Pricing 
  
    - [Legacy Documents](https://meetaandi.com/legacy-packages-v1)
    - [Government Glow-up](https://meetaandi.com/government-glow-up)
    - [Access for Every Brain](https://meetaandi.com/access-for-every-brain)
- [About](https://meetaandi.com/about)
- [Blog](https://meetaandi.com/blog)
- [Login](https://www.meetaandi.com/video-tool?#login)
- Profile
  
  Show submenu for Profile 
  
    - [Manage Credits](https://www.meetaandi.com/video-tool?#credits)
    - [Logout](https://www.meetaandi.com/video-tool?#logout)
- Admin
  
  Show submenu for Admin 
  
    - [Inbox](https://www.meetaandi.com/video-tool?#inbox)
    - [Manage Blog](https://www.meetaandi.com/video-tool?#adminBlog)
    - [Manage Credits](https://www.meetaandi.com/video-tool?#adminCredits)
    - [Dashboard](https://www.meetaandi.com/video-tool?#adminDashboardMain)
- [Contact us](https://meetaandi.com/contact-us)

[Contact us](https://meetaandi.com/contact-us)

 Jul 16, 2025, 12:39:44 PM

# WCAG 2.0 vs 2.1 vs 2.2 - How is it different for documents?

![Picture of Alex Bey](https://meetaandi.com/hs-fs/hubfs/Alex%20Headshot%20smaller.jpg?width=50&name=Alex%20Headshot%20smaller.jpg) [Alex Bey](https://meetaandi.com/blog/author/alex-bey)

Share: [facebook-f icon](http://www.facebook.com/share.php?u=https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents) [linkedin-in icon](http://www.linkedin.com/shareArticle?mini=true&url=https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents) [Twitter icon](https://twitter.com/intent/tweet?url=https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents) [pinterest-p icon](http://pinterest.com/pin/create/link/?url=https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents) [envelope icon](mailto:?body=https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents)

# **![6](https://meetaandi.com/hs-fs/hubfs/6.png?width=1200&height=628&name=6.png)**

# **WCAG 2.0 vs 2.1 vs 2.2 – How Is It Different for Documents?**

**Summary**

Understanding the differences between WCAG 2.0, 2.1 and 2.2 is essential for creating accessible documents. This blog outlines what’s changed in each version and what Australian organisations need to consider when remediating PDFs and other digital files.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

When it comes to digital accessibility, WCAG (Web Content Accessibility Guidelines) is the international standard. While originally focused on websites, WCAG also applies to downloadable content like PDFs and Word documents. With each new version, the guidelines evolve to reflect the needs of more users, including people with low vision, cognitive disability and mobility impairments.

For Australian organisations that share reports, forms or manuals online, staying up to date with the latest version of WCAG is important. But what are the real differences between WCAG 2.0, 2.1 and 2.2 when it comes to document accessibility?

At Meet Aandi, we specialise in helping you understand and meet these standards so your documents remain inclusive, usable and compliant.

## What is WCAG?

WCAG stands for the *Web Content Accessibility Guidelines*. Published by the W3C, these standards help ensure that digital content is:

- Perceivable
- Operable
- Understandable
- Robust

These four principles guide how we create and fix content for users of assistive technologies such as screen readers, screen magnifiers, and keyboard-only navigation.

## WCAG 2.0 – The baseline

WCAG 2.0 was released in 2008 and became the minimum standard for accessibility compliance in many Australian government agencies and institutions. It focuses on visual presentation, keyboard navigation, and screen reader compatibility.

For documents, this means:

- Proper tagging of headings, lists and tables
- Text alternatives for images
- Logical reading order
- Clear link text
- Sufficient colour contrast

If your PDFs were made to meet WCAG 2.0, they likely meet a basic level of accessibility. But they may still fall short for many users.

## WCAG 2.1 – Supporting touch, zoom and more users

Released in 2018, WCAG 2.1 builds on 2.0 by adding 17 new success criteria. These mainly address the needs of people with low vision, cognitive disability, and those using mobile or touch devices.

For documents, WCAG 2.1 adds focus to:

- **Reflow:** Content should adapt when zoomed up to 400%, without requiring horizontal scrolling
- **Text spacing:** Users should be able to adjust line height, paragraph spacing and letter spacing without losing content or functionality
- **Keyboard shortcuts:** Avoiding issues caused by single-key shortcuts
- **Pointer gestures:** Making interactive content accessible without complex gestures

If you’re remediating or designing a document today, WCAG 2.1 is the recommended benchmark.

## WCAG 2.2 – Enhancing usability and cognitive accessibility

Released in late 2023, WCAG 2.2 introduces 9 new success criteria. Many are designed to improve the experience for people with cognitive disability or those with limited motor function.

Document-related highlights include:

- **Consistent help:** Help options should appear consistently across documents if applicable
- **Dragging movements:** Avoid requiring drag-and-drop where possible
- **Target size:** Interactive elements (such as links in PDFs) must meet minimum size guidelines

While these changes may seem subtle, they significantly improve access for people with disability.

## What version should you follow?

Most Australian organisations are currently required to meet WCAG 2.1, especially for government or public-facing content. However, moving toward WCAG 2.2 ensures better access for more people and shows leadership in inclusive practice.

At Meet Aandi, we encourage all clients to follow the latest guidelines to future-proof their documents and improve usability across the board.

**WCAG 2.0 vs 2.1 vs 2.2: Key Differences for Document Accessibility**

The table below compares WCAG 2.0, 2.1 and 2.2 guidelines, highlighting how each version affects accessible document creation. It outlines key differences in success criteria, support for low vision and cognitive disabilities, and how these changes apply to PDFs, forms and other digital documents.

This comparison helps Australian organisations understand why updating to the latest WCAG version matters especially when aiming for inclusive, compliant content.

 

|   **Criteria**   |   **WCAG 2.0**   |   **WCAG 2.1**   |   **WCAG 2.2** |
| --- | --- | --- | --- |
|   **Release Year**   |   2008   |   2018   |   2023 |
|   **Guideline Focus**   |   Core principles: Perceivable, Operable, Understandable, Robust   |   Adds mobile and cognitive accessibility   |   Further supports users with cognitive and low vision disabilities   |
|   **Number of Success Criteria**   |   61   |   78   |   86   |
|   **Impact on PDFs and Documents**   |   Sets the foundation for accessible text, reading order, tagging and alt text   |   Introduces criteria that impact touch navigation, reflow and input labelling in documents   |   Adds requirements like visible focus indicators and accessible authentication, relevant to interactive forms and documents   |
|   **Support for Low Vision Users**   |   Basic zoom and text alternatives   |   Enhanced reflow, better contrast for text and images   |   Clear focus indicators and consistent navigation across document elements   |
|   **Support for Cognitive Disabilities**   |   Limited   |   Begins to address with input purpose and label criteria   |   Expands with criteria like avoiding timeouts and making authentication easier   |
|   **Example Relevant Criteria**   |   - Text alternatives (1.1.1)     - Reading order (1.3.2)   |   - Reflow (1.4.10)     - Input purpose (1.3.5)   |   - Focus appearance (2.4.11)     - Accessible authentication (3.3.7)   |
|   **Applicability to Document Remediation**   |   Foundational – required for tagged PDFs   |   Enhances user experience on mobile and tablets   |   Essential for inclusive forms, interactive PDFs and documents requiring login or input   |

## How Meet Aandi can help

We stay up to date with the evolving standards so you don’t have to. Our team ensures your PDFs and digital documents are tagged, structured and reviewed according to the latest WCAG version — whether that’s 2.0, 2.1 or 2.2.

From reflow and alt text to link navigation and interactive form elements, we handle the details that make your content work for everyone.

## Related posts

[![Hand holding blocks that say accessibility](https://meetaandi.com/hs-fs/hubfs/23.png?height=200&name=23.png)](https://meetaandi.com/blog/compliance-with-the-web-content-accessibility-guidelines-wcag-2.0)

## [Compliance with the Web content accessibility guidelines (WCAG 2.0)](https://meetaandi.com/blog/compliance-with-the-web-content-accessibility-guidelines-wcag-2.0)

![Picture of Alex Bey](https://meetaandi.com/hs-fs/hubfs/Alex%20Headshot%20smaller.jpg?width=50&name=Alex%20Headshot%20smaller.jpg) [Alex Bey](https://meetaandi.com/blog/author/alex-bey) 

 Apr 15, 2024, 4:55:40 PM

Learn about the importance of complying with Web Content Accessibility Guidelines (WCAG 2.0) for...

[Read more](https://meetaandi.com/blog/compliance-with-the-web-content-accessibility-guidelines-wcag-2.0)

[![](https://meetaandi.com/hs-fs/hubfs/24.png?height=200&name=24.png)](https://meetaandi.com/blog/captions-vs-transcripts-vs-audio-descriptions-whats-the-difference-and-why-do-you-need-all-three)

## [Captions vs Transcripts vs Audio Descriptions: What’s the Difference — and Why Do You Need All Three?](https://meetaandi.com/blog/captions-vs-transcripts-vs-audio-descriptions-whats-the-difference-and-why-do-you-need-all-three)

![Picture of Meet Aandi](https://meetaandi.com/hs-fs/hubfs/Licquorice%20Icon%20-%20larger%20area.png?width=50&name=Licquorice%20Icon%20-%20larger%20area.png) [Meet Aandi](https://meetaandi.com/blog/author/meet-aandi) 

 Jul 16, 2025, 12:46:57 PM

Let’s be honest — digital accessibility jargon can feel like alphabet soup. Captions, transcripts,...

[Read more](https://meetaandi.com/blog/captions-vs-transcripts-vs-audio-descriptions-whats-the-difference-and-why-do-you-need-all-three)

[![](https://meetaandi.com/hs-fs/hubfs/9-2.png?height=200&name=9-2.png)](https://meetaandi.com/blog/wcag-compliance-gap-old-documents)

[Inclusion](https://meetaandi.com/blog/tag/inclusion)

## [The WCAG Compliance Gap: Why Old Documents Put Organisations at Risk](https://meetaandi.com/blog/wcag-compliance-gap-old-documents)

![Picture of Meet Aandi](https://meetaandi.com/hs-fs/hubfs/Licquorice%20Icon%20-%20larger%20area.png?width=50&name=Licquorice%20Icon%20-%20larger%20area.png) [Meet Aandi](https://meetaandi.com/blog/author/meet-aandi) 

 Oct 9, 2025, 10:00:01 AM

Accessibility isn’t just about new content. Legacy documents that remain online can still create...

[Read more](https://meetaandi.com/blog/wcag-compliance-gap-old-documents)

[Document accessibility](https://meetaandi.com/document-accessibility)  
[Video accessibility](https://meetaandi.com/video-accessibility)  
[Music accessibility](https://meetaandi.com/music-accessibility)  
<https://www.meetaandi.com.au/?#training><https://www.meetaandi.com.au/?#training>[Writing & designing for accessibility](https://meetaandi.com/writing-and-designing-for-accessibility)  
[Accessibility training](https://meetaandi.com/accessibility-training)  
[DE&I consulting](https://meetaandi.com/dei-consulting)

#### Connect with us

facebook-f icon linkedin-in icon Twitter icon instagram icon

Terms & Conditions  
Privacy Policy

© Brio Group 2025

**Brio Group is all about accessible communication and is made up of:**

Accessible Design

[![BrioWebsiteLogos_BrioGroup - Cropped](https://meetaandi.com/hs-fs/hubfs/BrioWebsiteLogos_BrioGroup%20-%20Cropped.png?width=142&height=100&name=BrioWebsiteLogos_BrioGroup%20-%20Cropped.png)](https://www.briogroup.com.au/)

Accessible Education

[![thumbnail_Meet Aandi Logo Only_White (1)](https://meetaandi.com/hs-fs/hubfs/thumbnail_Meet%20Aandi%20Logo%20Only_White%20(1).png?width=252&height=63&name=thumbnail_Meet%20Aandi%20Logo%20Only_White%20(1).png)](https://www.meetaandi.com.au/)

 

Delivering Accessibility Globally

[  +61 1300 255 733](tel:1300255733)

[  info@meetaandi.com](mailto:info@meetaandi.com)

[ Contact us](https://www.meetaandi.com.au/?#contact)  
[   About us](https://meetaandi.com/about)

---

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Alex Bey",
    "url" : "https://meetaandi.com/blog/author/alex-bey"
  },
  "dateModified" : "2025-07-16T02:39:53.753Z",
  "datePublished" : "2025-07-16T02:39:44.000Z",
  "headline" : "WCAG 2.0 vs 2.1 vs 2.2 - How is it different for documents?",
  "image" : [ "https://meetaandi.com/hubfs/6.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://meetaandi.com/blog/wcag-2.0-vs-2.1-vs-2.2-how-is-it-different-for-documents",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://meetaandi.com/hubfs/MeetAandi-Logo-web.png"
    },
    "name" : "Brio Group Pty Ltd"
  }
}
```