WCAG stands for Web Content Accessibility Guidelines, the international standards developed by the W3C (World Wide Web Consortium) to ensure that web content is accessible to people with disabilities. They are divided into three progressive levels of compliance (to declare conformity with a given level, all criteria for that level and all lower levels must be met). These levels indicate the extent to which web pages comply with accessibility standards.
🅰️ Level A
This is the minimum level of web accessibility, aimed at removing the main barriers that prevent access. It focuses on the most basic requirements that allow users with disabilities to navigate and interact with digital content.
🅰️🅰️ Level AA
This includes all Level A criteria and adds more advanced requirements. It represents the minimum compliance level required for websites, apps, and digital products – except in special cases where compliance would impose a disproportionate burden (as defined by specific evaluation criteria).
🅰️🅰️🅰️ Level AAA
This level includes all requirements from Levels A and AA and represents the highest standard of accessibility. While not mandatory in most cases, it is recommended for websites that primarily serve users with disabilities.
2️⃣.0️⃣ WCAG 2.0 (Published in 2008)
The foundation of WCAG 2.0 rests on four core principles, known by the acronym POUR, which define the characteristics of an inclusive digital experience:
- Perceivable: Information must be perceivable by everyone, regardless of sensory disabilities.
Technically, this means providing text alternatives for images and non-text content (1.1.1), captions for videos (1.2.2), and audio descriptions for complex multimedia content (1.2.3). - Operable: Users must be able to interact and navigate without obstacles, even without a mouse.
Features should be keyboard-accessible (2.1.1), free of “focus traps” (2.1.2), and allow users to pause, stop, or hide moving or flashing elements (2.2.2). - Understandable: Content and interfaces must be clear and predictable.
Menu items, form labels, and error messages should be consistent and easy to understand (3.3.2). Readability should be ensured through simple language and defined abbreviations (3.1.4). - Robust: Content should work reliably across browsers, devices, and assistive technologies.
This requires correct semantic markup, well-defined ARIA roles, and accessible names for screen readers (4.1.2).
WCAG 2.0 remains the foundational framework for accessible digital experiences. Later versions (2.1 and 2.2) build upon it, strengthening an already solid and widely recognized technical standard.
2️⃣.1️⃣ WCAG 2.1 (Published in 2018)
WCAG 2.1 does not rewrite the core rules from WCAG 2.0 — it expands them to address previously overlooked needs and to align with technological advances.
The new criteria focus on three main areas:
- Mobile devices
- Cognitive disabilities
- Users with limited vision or complex input needs
Mobile Access and Responsiveness
WCAG 2.1 enhances support for small screens and different orientations (portrait/landscape). Text must remain legible at up to 400% zoom without requiring horizontal scrolling.
Simpler and More Controlled Interactions
Touch targets must meet minimum size requirements, gestures must have simple alternatives, and users must be able to disable unwanted animations or keyboard shortcuts — improving usability for users with motor or cognitive impairments.
Clearer Content and Status Feedback
WCAG 2.1 introduces contrast rules not only for text but also for graphical elements, icons, and buttons. Input fields and interface components must be correctly labeled for assistive technologies. Interactive feedback and status messages must be accessible and non-disorienting.
Why WCAG 2.1 Level AA Matters
WCAG 2.1 Level AA is now the technical benchmark for ensuring that websites, apps, and digital content are accessible to people with sensory, motor, and cognitive disabilities.
It not only includes the basics (from WCAG 2.0) – such as readable text, alternative text, sufficient contrast, and clear navigation – but also covers mobile usage, keyboard navigation, and assistive technology compatibility.
Legally, WCAG 2.1 Level AA has become the minimum compliance level required under the European Accessibility Act, ensuring that content remains perceivable, operable, understandable, and robust — the four POUR principles.
Flexible and Adaptable Content
Users on mobile or with high zoom levels must be able to read and interact without horizontal scrolling or layout breakage. Text, images, and components must adapt fluidly to screen size and orientation.
Clear Visual Contrast
Elements such as icons and buttons must have sufficient contrast to remain distinguishable. Users should also be able to customize text spacing without breaking the layout.
Simple and Predictable Navigation
The focus indicator must always be visible. Buttons and links must meet minimum size standards. Elements that appear on hover (like tooltips) should stay visible until dismissed by the user.
Clear Feedback and Error Handling
Screen readers must be notified automatically when something important changes on a page. Status messages and form errors should be readable without forcing the user to search manually.
2️⃣.2️⃣ WCAG 2.2 (Published in 2023)
WCAG 2.2 introduces criteria that better address keyboard navigation, interactive form usability, and content comprehension for users with cognitive disabilities. It adds new success criteria without removing any from previous versions.
Visible Focus and Frustration-Free Navigation
For keyboard-only users, maintaining awareness of where they are on a page is essential. WCAG 2.2 strengthens this with:
- Focus Not Obscured (Minimum & Enhanced): The focus indicator must never be hidden by sticky headers, pop-ups, or floating elements.
- Focus Appearance: Defines minimum contrast and size requirements for focus indicators.
Touch and Gestures for Everyone
WCAG 2.2 introduces the Dragging Movements criterion, requiring simple alternatives to complex drag-and-drop actions.
It also reinforces Target Size (Minimum) – ensuring that clickable areas are large enough to prevent accidental taps.
Consistent and Accessible Help
With Consistent Help, support resources such as chatbots, FAQs, or contact links must appear in the same location on similar pages, so users don’t need to search for them repeatedly.
No Redundant Data Entry
Redundant Entry prohibits requesting users to re-enter information already provided unless absolutely necessary — reducing frustration and errors.
Accessible and Inclusive Authentication
WCAG 2.2 introduces Accessible Authentication, requiring login processes that don’t rely solely on memory or complex codes (e.g., supporting biometrics, one-time links, or simple prompts). An enhanced version further broadens flexibility for users with cognitive impairments.
