WCAG 2.2.
New obligations.
Real benefits.
WCAG 2.2 is a set of guidelines designed to help create websites and digital applications in an accessible and user-friendly way.
By following these guidelines, websites become usable for people who are blind, visually impaired, deaf, have mobility issues, cognitive impairments, or use assistive technologies such as screen readers.
Non-compliance brings risks such as penalties, customer complaints, and even the loss of competitive advantage.
What Are the WCAG 2.2 Requirements?
The WCAG 2.2 guidelines are structured around four key principles that form the foundation of digital accessibility:
Perceivability
Information and elements on a website or application must be presented in a way that allows users to notice and understand them—regardless of the sense they rely on or the assistive technology they use.
Examples:
ALT Text for Images
A blind person won’t see a product photo, but thanks to a screen reader, they can hear its description, e.g., “Green armchair with metal legs.”
Good Color Contrast
Too low a contrast between colors, such as gray text on a white background, makes reading difficult for people with low vision.
Text Zoom Capability
Older users or those with vision impairments should be able to easily enlarge text without breaking the page layout.
Operability
A website should be accessible and easy to use regardless of the navigation method—whether by keyboard, touchscreen, or assistive technologies. Its functionality must not rely solely on using a mouse.
Examples:
Keyboard Support
A person with limited hand mobility may navigate the site using only the Tab key.
Thoughtful Navigation
Users should always know where they are and how to return to the previous page.
No Traps
A form that can’t be exited using the keyboard is an insurmountable barrier for many users.
Understandability
Content and interactions on the site must be clear, logical, and predictable—without complicated language, confusing navigation, or unexpected system behavior.
Examples:
Simple Language
Instead of the message “please authorize access,” it’s better to use clear and understandable wording like: “Log in.”
Clear Buttons
Instead of a generic “Perform action,” use a specific label like “Add to cart.”
Error Messages
After entering an incorrect email, the form should clearly indicate the problem: “The email address is invalid.”
Compatibility
The website should be reliable and compatible with various browsers, devices, and assistive technologies for people with disabilities. Examples:
Correct HTML Code
Ensures the site works properly across all technical environments.
Screen Reader Compatibility
Page elements must be described in a way that allows them to be read by tools used by blind users.
Dynamic Messages
Notifications (e.g., “added to cart”) should be accessible to assistive technologies (using aria-live).
WCAG Compliance Levels – Which One Is Mandatory?
The Web Content Accessibility Guidelines (WCAG) are divided into three levels of compliance. Each level indicates how well a website meets digital accessibility requirements. The higher the level, the more inclusive and user-friendly the site is for people with diverse needs and limitations.
Level A
The bare minimum, ensuring basic access to content.
Level AA
Legally required; it addresses the majority of barriers that prevent users from fully using websites.
Level AAA
The highest standard—recommended but not legally required.
-
The law introducing the WCAG 2.2 standard comes into force on June 28, 2025.
-
Organizations have until June 28, 2030 to comply with its requirements.
-
Given the number of elements that need to be reviewed and improved, it’s wise to start preparations early to ensure compliance without last-minute pressure or unexpected costs.
Why implement digital accessibility now?
Implementing accessibility in line with WCAG 2.2 is not just a legal obligation—it’s a real opportunity for growth, service improvement, and building a socially responsible brand. Here are the key reasons not to wait until the last minute:
Downloadable Accessibility Checklist
We’ve prepared a checklist to help you assess your website or app’s accessibility in line with WCAG 2.2 (Levels A and AA – legally required):
- Nearly 50 WCAG 2.2 requirements with explanations
- Perfect for audits – simply mark YES / NO / NOT APPLICABLE
- Saves hours of analysis – ready to use by your team or contractor
We will design and develop your online store in full compliance with WCAG 2.2 requirements.
