Comprehensive WCAG 2.2 Checklist: Explanation, Importance, and The Current State of Accessibility

US courts and regulators frequently reference WCAG as the benchmark when assessing digital accessibility, even though it is not explicitly codified in the ADA.

You’d think that in 2026, all websites are compliant, able to withstand scrutiny from users, regulators, and search engines, but the truth is far more complex. To help you understand the basics of accessibility compliance, we’ve created this WCAG 2.2 checklist and a breakdown of the essential legal and technical contexts that help you understand today’s importance of WCAG 2.2 compliance.

Accessibility in the Digital Realm

Website accessibility simply means ensuring that every single user who ends up on your website can actually use it, regardless of their abilities. This means all those who use screen readers, navigate with keyboards, voice commands, have vision problems, or use other assistive devices.

Accessibility means that your site’s content, structure, and functionality are designed in a way that allows everyone to interpret it correctly. Nowadays, accessibility is more than inclusivity, but rather, a compounding digital asset:

• Legal Compliance: Government sites, high-risk commercial sites like e-commerce and banking platforms must meet the latest guidelines to avoid legal problems
• Better Overall UX: Accessibility directly influences user experience. Features like clean contrast, larger buttons, clear content structuring, and metadata often improve web experiences for every user, not just those who use assistive technology.
• SEO: Search engines prioritize a lot of the best practices that accessibility guidelines promote, which can also help you improve your rankings.

• Wider Reach: In the US alone, 28.7% of people have some type of disability, translating into one in every four people. Having an accessible website allows them to use it, broadening your reach.

• Brand Reputation: Your brand demonstrates commitment to its users by ensuring everyone can visit your site. In addition to developing a brand that’s perceived as inclusive, you can also create deeper, more profound relationships with your customers.

Legal Importance for Website Owners

Even though ADA never mentions WCAG accessibility standards explicitly, in the US, accessibility requirements for government websites are primarily defined by Section 508, which incorporates WCAG 2.0 Level A and AA requirements, although many organizations have adopted WCAG 2.1 or higher in practice. The European Accessibility Act (EAA) aligns with similar standards, such as EN 301 549, which are evolving toward WCAG 2.2.

For instance, the EAA applies to a wide range of organizations, both in and outside the European Union (if they work with or sell to EU citizens). The following industries are affected:

• Finance and Banking: online banking apps, financial service providers
• Transportation: air, bus, and rail websites and apps.
• Retail and e-commerce: online marketplaces, shops, consumer-facing applications
• E-books: dedicated software and e-book platforms
• Media: streaming services, on-demand services, etc.
• Telecommunications: messaging apps, internet providers, etc.
• B2B and B2G: Companies that sell technology or software to the government or private sectors.

WCAG 2.2 Compliance: Understanding the POUR Principle

WCAG defines that content on your site should follow the POUR principle, which means that you should provide your users with alternatives to comprehend, interact, and identify the content, along with giving them the means to control the elements on the site.

In this sense, we can break down the POUR principle like this:

Perceivable

You should provide alternatives for non-text content like video, images, or audio. These can be captions for audio material to help better understand video content. 

Similarly, you should also have different content variations (like a simpler layout) without changing the structure or losing any vital information. There should be enough contrast between text and background, and you should stay away from using color to communicate vital info (“follow the blue signs on the page”). 

Operable

All page functionalities should be available from the user’s keyboard, and the website should avoid using design solutions that may cause seizures (like strobes or flashes). The navigation should be intuitive and offer different ways to find the content users are looking for. 

Regarding navigation, every page and content piece should have proper titles and headings that describe the page’s or article’s purpose/topic. Lastly, the website should support multiple input methods, including keyboard, touch, and assistive technologies.

Understandable

The content should be understandable and easy to read. If there are interaction features (input passwords or other info), give the users space to avoid mistakes, and opportunities to revert and correct them. 

All web pages should be intuitive and behave in a predictable manner.

Robust

Again, the website should fully support all assistive tech, and regular accessibility testing should be performed to ensure compatibility with said technologies. The code should also be clear and correct so the assistive devices can parse the content accurately. 

What’s New in WCAG 2.2 Compared to 2.1?

WCAG 2.2 was released in October 2023. This was the latest update from the W3C (World Wide Web Consortium), building on the previous 2.1 release, rather than replacing it. The update focuses more on providing a better accessibility framework for individuals with learning, cognitive, motor, and visual disabilities. The update also aims to address more specifics on mobile accessibility, as people use several devices to access digital content. 

Upgrading from WCAG 2.1 to align with WCAG 2.2 AA has immense value. Apart from further improving accessibility for mobile users, it can also help you to keep pace with evolving regulations (see the EAA’s standards spanning across several industries).

To be more specific, WCAG 2.1 also focused on improving accessibility for people with low vision, but WCAG 2.2 adds more guidelines and specifics, like specifying minimum visibility, and not letting focused elements get hidden by other content. Accessible touch gestures also have more formalized requirements, adding small nuances that make a world of difference (like tapping a volume bar instead of dragging it to avoid your finger slipping).

Understanding A, AA, and AAA in WCAG 2.2 Guidelines

The 2.2 update introduces nine new success criteria. As you may remember, every update from WCAG 1.0 through 2.2 builds upon the others. This means that WCAG 2.1 had 78 success criteria, and the latest update has 86 (adding nine new ones and removing one obsolete parsing criterion from the previous 78).

Also, similarly to previous versions, the WCAG 2.2 guidelines break down the success criteria into three testable levels, which are A, AA, and AAA. The first level (A) represents the bare minimum conformance level, while the triple A level is up to the highest standards. The levels are backwards compatible, meaning that a level AA conformance also holds up with Level A.

Which level of conformance would be optimal? The majority of the most important accessibility regulations (like the Section 508 of the Rehabilitation Act of 1973 in the U.S., EN 301 549 in Europe) all require at least Level AA. Reaching the highest level of conformance can be something you can strive for, but at the moment, these advanced measures are not required by law.

That said, Level AA is the globally accepted accessibility standard.

Why Care About WCAG 2.2 Compliance 

While your industry or website may not fall under the categories where being WCAG 2.2 compliant is a must, WCAG AA compliance is a smart digital investment.

By satisfying the nine added success criteria, your site (and brand and business) will better serve your current and future users and can serve users with a broader range of disabilities. On the other hand, WCAG AA compliance simply signals that your brand is up-to-date with digital best practices, highlighting your commitment to making the web an accessible place for everyone.

Conforming to these standards also opens up global opportunities. The UK public sector has incorporated these standards in 2024. The European Accessibility Act aligns with standards such as EN 301 549, which are evolving to incorporate WCAG 2.2 requirements. So, even if you are not obligated to, meeting the criteria now means that you will stay ahead if regulations change.

New WCAG 2.2 Success Criteria (What’s Added in 2.2)

As mentioned, WCAG 2.2 introduces nine new success criteria that address accessibility gaps across the POUR principles. These criteria span Levels A, AA, and AAA and build upon previous versions rather than replacing them.

Below is a clear breakdown of all nine new criteria:

• Focus Not Obscured (Minimum): 2.4.11 (Level AA)

Focused elements must not be completely hidden by other content when navigating via keyboard. This ensures users can always identify their current position on the page. 

• Focus Not Obscured (Enhanced): 2.4.12 (Level AAA)

A stricter version of the above: focused elements must not be obscured at all. 

• Focus Appearance: 2.4.13 (Level AAA)

Focus indicators must meet specific visibility requirements, making them easier to identify for users with low vision or those navigating via keyboard. 

• Dragging Movements: 2.5.7 (Level AA)

All functionality that uses dragging must also be operable with a single pointer (e.g., tapping), making interactions more accessible for users with motor impairments. 

• Target Size (Minimum):  2.5.8 (Level AA)

Interactive elements must be at least 24×24 CSS pixels or have sufficient spacing to prevent accidental activation. 

• Consistent Help: 3.2.6 (Level A)

Help mechanisms (such as contact pages, chat, or support links) must appear in a consistent location across pages. 

• Redundant Entry: 3.3.7 (Level A)

Users should not need to re-enter the same information within a process if it has already been provided. 

• Accessible Authentication (Minimum): 3.3.8 (Level AA)

Authentication should not rely solely on memory-based tasks. Alternatives or assistance (e.g., password managers) must be supported. 

• Accessible Authentication (Enhanced): 3.3.9 (Level AAA)

Authentication must not require cognitive function tests unless an alternative is provided. 

Practical WCAG 2.2 AA Checklist (Design, Development, and Testing)

This checklist translates WCAG 2.2 Level AA requirements into practical actions for designers, developers, and QA teams. While WCAG defines what needs to be achieved, the items below focus on how to implement and validate accessibility in real-world workflows. 

For a more hands-on, beginner-friendly walkthrough of these fundamentals — from picking an accessible CMS to designing forms and color systems — see our 10 practical ways to make a website accessible.

Design — Visual and Interaction Foundations

• Maintain contrast ratios (4.5:1 for body text, 3:1 for large text and UI components)
• Do not rely on color alone to convey meaning
• Ensure visible and high-contrast focus states
• Use readable typography (scalable up to 200%, proper line height and spacing)
• Ensure layouts reflow properly at 320px width
• Design all interaction states (default, hover, focus, active, disabled)
• Maintain minimum target size of 24×24 CSS pixels (44×44 recommended)
• Avoid autoplaying media with sound and respect reduced motion preferences

Development — Structure and Accessibility Support

• Use semantic HTML before ARIA
• Ensure full keyboard operability (no traps, logical tab order, skip links)
• Provide accessible names for all interactive elements
• Properly associate labels with inputs
• Support autofill and reduce redundant data entry
• Include captions, transcripts, and audio descriptions for media
• Manage focus and announcements in dynamic content (SPAs)
• Ensure proper heading structure (H1–H6) to support screen reader navigation

Testing — Validation and Compliance

• Use automated tools (axe, WAVE, Lighthouse) for initial checks (~30% coverage)
• Perform manual keyboard and screen reader testing
• Test zoom (200%) and reflow (320px width)
• Include testing with users with disabilities when possible
• Document findings using VPAT or equivalent reports
• Prioritize fixes based on severity and impact

Benefits of Adopting WCAG 2.2 AA

Implementing these guidelines has several potential benefits for your website and business. When the content is easier to access overall, you can strengthen your relationship with customers and improve your reputation as an inclusive brand. Meeting these standards also helps you avoid legal problems related to accessibility compliance.

On the other hand, running more accessible websites is a great business opportunity. According to data, businesses could open a $13 trillion market opportunity globally by improving accessibility. Accessible websites are easier to navigate for all users, meaning they are more likely to interact with and regularly return to. Having a stellar user experience is key to building a strong online presence, not to mention that accessible platforms also perform better in search results. 

Still, you shouldn’t forget that upgrading to WCAG 2.2 guidelines doesn’t eliminate core requirements. Proper alt text, captions, and color contrast, heading structures, and skip-to-content links are still musts. As we mentioned above, the new update builds upon the foundation of the previous ones.

Accessibility Scanning and Common Issues

It’s one thing to implement accessibility features, but ensuring that they work properly is another. Many site owners and developers rely on accessibility tools, but on average, they only capture 25% of the issues, according to some sources. Others cite higher percentages, between 30% and 50%, but that’s still only half of the problems in a hypothetical scenario.

Another problem that may arise during automated testing is generating false positives and negatives, i.e., flagging non-issues and ignoring real ones. 

That said, comprehensive accessibility testing should still incorporate manual evaluation with the help of keyboards, screen readers, and human judgment. Again, we are not saying that automated testing is useless: it can still flag a lot of potential problems, but it isn’t comprehensive. That’s why balancing out the two methods can provide the best results: thoroughness, accuracy, and efficiency.

Most Common WCAG Violations

By now, you’d assume that websites that consider themselves accessible are flawless in this respect. The truth is that there are still a lot of distinct issues, even though the WCAG 2.2 guidelines have been out since 2023. Out of a million home pages, experts detected a total of 56,114,377 distinct accessibility errors across the web, which is 56.1 errors per page.

The most common errors were low contrast text in 83.9% of cases, followed by missing alt text for images (53.1%) and missing form input labels (51%). Empty links took fourth place (46.3%), followed by empty buttons (30.6%), and missing document language with 13.5%

While inclusivity and accessibility are starting to become increasingly important UX and ranking factors, still, as you can see in the table below, some of the most common issues remain consistent across the board. 

Taken from: https://webaim.org/projects/million/

Issues Across Industries

As you can see, six main issues cause the most headaches. Still, how prevalent are the different sectors in industries? 

US Government Websites

For instance, in the US, websites that are subject to Section 508 requirements offer better overall accessibility when compared to commercial platforms. More specifically, government websites, on average, have roughly half the automatically detectable errors when compared to private sites.

This trend can be interpreted as a direct consequence of more stringent legal obligations and sustained compliance efforts. And even though these sites still aren’t fully accessible, they demonstrate a willingness to resolve the issues.

Also, the gap between commercial and government tells us that legal obligations work and that commercial entities that face similar accessibility requirements can expect similarly improved scores if the changes are implemented successfully. 

Finance Has the Best WCAG 2.2 Compliance Scores, While Retail Faces the Most Lawsuits

When looking at commercial platforms, financial service sites have the best average scores, with roughly 34% less accessibility errors than the majority. This comes as no surprise, as banking and financial entities have always been subject to more thorough regulatory scrutiny, litigation exposure, and customer expectations. 

On the other hand, financial platforms tend to prioritize accessibility by default. Especially as their customer base widens, there are more older people accessing their apps with mobility and vision problems. In their cases, inaccessibility to online banking features equals losing customers.

In the private sector, retail sites account for 77% of all accessibility lawsuits, even though their performance in this regard is average. However, it seems as though the pressure of being sued hasn’t led to real improvements across the industry.

Also, the high number of lawsuits creates a strange situation in retail. Due to legal pressure, the company fixes the accessibility issue, but often ignores bigger changes in the site’s design or code. Due to this, sites do improve over time, but never get fully accessible for every user.

Interpreting the Data

Even though incorporating accessibility features and solutions into development and design has several benefits, the adaptation rate is slow, with high failure percentages despite decades of established and continuously improving standards. 

The good news is that the majority of the problems stem from six common issues, like missing alt text, contrast problems, and missing form labels. Addressing these would make drastic changes in the statistics.

While legal actions work, they shouldn’t be the only solution. That’s why experts recommend integrating accessibility into the development process. Compliance becomes less of an “added burden” when it’s an integral part of the workflow, and treating it as a development practice rather than a post-launch quick fix is guaranteed to change results.  

Addressing WCAG 2.2 Compliance Problems When They Arise

When complaints about (let’s say a finance site) arise, the resolution will usually follow the same pattern. Namely, the site owners (service provider) agree to adopt the necessary WCAG standards, conduct a full audit, try to correct the identified issues within the predefined timeline, and adhere to ongoing monitoring. 

However, it’s vital to understand that accessibility isn’t purely a legal obligation. It’s about serving your customers better, improving SEO, user experience, and setting up your digital presence for the future. Many WCAG improvements, like better contrast, structured content, and simpler authentication, simply make life easier for everyone who ends up on your website. In the end, accessibility is just a natural part of professional web design services.

Implementing WCAG 2.2 for The Future

The latest updates aim to make digital content more accessible to an even wider audience, and by implementing these features, such as improved focus appearance, simplified gestures, and alternative authentication processes, you are creating a more inclusive website for all users.

Regarding accessibility, one thing is certain: digital inclusivity standards will continue to improve. The W3C has been working on WCAG 3.0 for some time now, and it’s said that it will be released around 2028. The future update promises to be even more comprehensive and offer even more nuanced guidelines for common issues. 

Those businesses that adopt WCAG 2.2 now won’t only meet current compliance standards, but also invest in a smoother transition in the future, when the trends and standards further evolve.