How to Make Your Website WCAG 2.2 Compliant: A Practical Checklist

Web accessibility is no longer a niche concern. With digital accessibility legislation expanding across the US, Europe, Canada, Australia, and beyond, businesses that build and maintain websites face a growing obligation to ensure those sites work for everyone. WCAG 2.2, published in October 2023, is the current version of the World Wide Web Consortium’s accessibility […]

Web accessibility is no longer a niche concern. With digital accessibility legislation expanding across the US, Europe, Canada, Australia, and beyond, businesses that build and maintain websites face a growing obligation to ensure those sites work for everyone. WCAG 2.2, published in October 2023, is the current version of the World Wide Web Consortium’s accessibility guidelines, and it introduces new success criteria that tighten requirements around authentication, navigation, and error handling. This WCAG 2.2 compliance checklist walks you through what the standard actually requires, what changed from previous versions, and how to apply the guidelines practically to a live website without getting lost in technical jargon.

We build and audit websites for brands across healthcare, e-commerce, fitness, and education at Monk Creatives. The accessibility principles in this guide apply to every site we develop, and they’re the same ones we evaluate during our website development process.

What Is WCAG 2.2 and Why Does It Matter

The Web Content Accessibility Guidelines, maintained by the W3C, are the globally recognised standard for making digital content accessible to people with disabilities. WCAG 2.2 builds on the earlier 2.0 and 2.1 versions by adding nine new success criteria specifically aimed at helping users with cognitive, motor, and low-vision disabilities. These new criteria address gaps that earlier versions left open, such as the difficulty of passwort-protected login flows for users who can’t type easily, or the confusion caused by inconsistent help-link placement across pages.

WCAG 2.2 compliance matters for three reasons. First, it aligns your site with the legal accessibility requirements referenced by regulations like the Americans with Disabilities Act in the US, the European Accessibility Act, Canada’s Accessible Canada Act, and similar frameworks elsewhere. Second, it makes your site genuinely usable for the roughly 1 billion people worldwide who live with some form of disability. Third, accessible design tends to produce better outcomes for all users, clearer navigation, faster load times, more readable copy, and more strong mobile experiences. An accessible site is usually a better site.

Understanding the Four Core Principles

WCAG is built around four principles abbreviated as POUR: Perceivable, Operable, Understandable, and Strong. Every success criterion under WCAG 2.2 maps to at least one of these principles, and a site that satisfies all four simultaneously is considered conformant. Think of it this way: information must be available in ways users can perceive, interface elements must be operable by everyone, content and operation must be understandable, and the site must be strong enough that assistive technologies can interpret it reliably.

The perceivable principle covers everything from text alternatives for images to captions for video, sufficient colour contrast, and the ability to resize text without loss of content. Operable addresses keyboard accessibility, timing controls, seizure-safe animations, and navigable site structures. Understandable focuses on readable text, predictable behaviour, and accessible error handling. Strong covers the technical side, valid markup, proper ARIA use, and compatibility with assistive technologies like screen readers.

WCAG Compliance Levels: A, AA, and AAA

WCAG 2.2 success criteria are organised into three levels. Level A is the minimum, removing the most severe barriers that prevent people from using a site at all. Level AA addresses the most common accessibility gaps and is the level most legislation and procurement policies reference. Level AAA represents the highest level of accessibility, covering additional criteria that improve usability for people with more significant impairments.

Most organisations target Level AA compliance. AAA criteria include requirements like sign language interpretation for prerecorded video, extended audio descriptions, and highly specific contrast ratios for large text that exceed what AA already mandates. Pursuing AAA is worthwhile for some audiences, but it can be impractical for others. The table below summarises how each level maps to practical implementation across common content types.

Content TypeLevel ALevel AALevel AAA
Images with meaningful contentAlt text requiredAlt text required; extended descriptions for complex imagesAlt text plus text alternatives for complex charts and diagrams
Video contentCaptions for prerecorded audioCaptions for live audio; audio description for prerecorded videoSign language interpretation; extended audio description
Text readabilityNo requirement4.5:1 contrast for normal text; 3:1 for large text7:1 contrast for normal text; 4.5:1 for large text
Keyboard navigationAll functionality keyboard accessibleNo keyboard traps; visible focus indicatorsAdditional focus management requirements
Form errorsError identificationError suggestions; accessible validation messagesContext-sensitive help text on required fields

What Is New in WCAG 2.2

WCAG 2.2 adds nine new Level A or AA success criteria that were not present in WCAG 2.1. These are the criteria most organisations upgrading from earlier versions will need to evaluate. Dragging movements, which covers interfaces that require users to drag elements rather than use buttons, must now offer an alternative single-pointer input. Target size requirements set minimum dimensions for clickable elements to accommodate users with motor impairments. Consistent help means that if your site offers a help link in the header, it must appear in the same location on every page.

Redundant entry requires that if a user enters the same information in multiple steps of a process, you must offer to pre-fill it rather than asking them to retype. Accessible authentication eliminates password-based challenges that depend on recalling information, such as remembering a specific word, and requires alternatives like confirming via email or using a password manager. Accessible authentication also removes CAPTCHAs that require visual or cognitive tests. Finally, focus not obscured and focus not diminished address situations where a focused element becomes visually hidden or significantly altered by sticky headers and footers, which can disorient keyboard and screen-reader users.

A Practical WCAG 2.2 Compliance Checklist

The most effective way to audit a site is to work through each principle systematically and test against actual user flows rather than pages in isolation. A homepage might pass every automated check but still fail in the checkout process, where hidden error messages and inaccessible form validation create real barriers. The checklist below groups the most common success criteria by principle, which mirrors how a professional audit is structured. For each criterion, test with both automated tools and manual keyboard and screen-reader navigation.

Perceivable: Can Users Access and Understand Your Content

Every meaningful image needs alt text that describes its function, not just its appearance. A photograph of a doctor in a clinic needs alt text like “Dr Raj Palaniappan in consultation” rather than “doctor-office-001.jpg.” Decorative images should carry empty alt attributes so screen readers skip them. For complex images like charts or infographics, the alt text should point to a longer description on the same page. Video content must have captions that capture not just dialogue but also meaningful sound cues. Audio-only content like podcasts should have transcripts.

Colour contrast is one of the most consistently failed criteria. Normal body text needs a contrast ratio of at least 4.5:1 against its background under WCAG 2.2 Level AA. Large text, defined as 18pt or 14pt bold and above, needs a ratio of 3:1. The easiest way to test this is with browser tools like the WebAIM contrast checker or built-in dev tools in Chrome and Firefox. Don’t rely on visual judgement alone; the difference between “looks fine” and actually passing the threshold can be surprisingly small. Text should also remain readable when a user zooms their browser to 400% without requiring horizontal scrolling or losing access to content.

Operable: Can Users Navigate and Interact with Your Site

Keyboard operability is non-negotiable. Every interactive element, links, buttons, form fields, dropdowns, modal dialogs, accordion panels, must be reachable and operable using the Tab key, Enter or Space for activation, and arrow keys where appropriate. The visible focus indicator must be clear. Many modern CSS frameworks suppress default focus outlines, so you need to ensure custom focus styles are present and have sufficient contrast against the page background. A keyboard trap, where a user can tab into an element but cannot tab out of it, is a Level A violation and one of the most frustrating barriers a user can encounter.

Touch targets need sufficient size. WCAG 2.2 Level AA requires interactive elements to have a target size of at least 24 by 24 CSS pixels, though 44 by 44 pixels is the recommended best practice and aligns with Apple’s Human Interface Guidelines and Google’s Material Design standards. Buttons, links in navigation, and form inputs need to meet this threshold. Timing is also important: if your site uses timeouts, for example, an authentication session that expires after fifteen minutes of inactivity, you must either allow users to extend the session or give them adequate warning before it expires.

Understandable: Is Your Site Predictable and Clear

Navigation must be consistent. If your primary navigation uses a hamburger menu on one page, it should use the same structure on every page. If your logo in the top-left corner links to the homepage, it should do so consistently. Links with identical text should point to the same destination every time. This consistency helps screen-reader users build a reliable mental model of how your site is structured, and it reduces cognitive load for all users.

Forms deserve particular attention under WCAG 2.2. Every input that fails validation needs an accessible error message: the error must be programmatically associated with the field, the message must be specific, and the user must be told how to correct the error. Vague messages like “Invalid entry” are not sufficient; instead, use something like “Please enter a valid email address, such as name@example.com.” Labels must be present and properly associated with each input. Placeholder text alone is not a label, because it disappears when the user begins typing. For multi-step forms, pre-filling previously entered information where possible is now a Level AA requirement under the redundant entry criterion.

Strong: Does Your Site Work with Assistive Technologies

This is the most technical principle, but its practical implications are straightforward. Your HTML should be valid and follow established standards. Custom interactive components, accordions, carousels, tabbed interfaces, modal dialogs, need to implement ARIA roles, states, and properties correctly so screen readers can interpret them. The W3C’s ARIA Authoring Practices Guide provides tested patterns for most common components.

One common mistake is overusing ARIA. The first rule of ARIA is simple: if a native HTML element does the job, use that element. A native button element is inherently accessible and requires no ARIA markup. Adding ARIA roles to native elements without understanding the implications can actually make things worse. The safest approach is to build with semantic HTML first and reach for ARIA only when native elements genuinely cannot express the required behaviour.

Testing and Validating Your WCAG 2.2 Compliance

Automated tools catch roughly 30 to 40 percent of accessibility violations. They are a useful starting point, but they cannot identify most perceivable, understandable, or strong failures. For example, an automated tool will flag missing alt text, but it cannot determine whether your alt text is actually descriptive or just filler. It can check contrast ratios but cannot evaluate whether your error messages are meaningful or whether your navigation structure makes sense. At our blog, we share practical guidance on auditing digital experiences, including accessibility.

The most reliable testing combines three approaches. First, run automated scans using tools like the WAVE browser extension, axe DevTools, or Google Lighthouse, which is built into Chrome DevTools. Second, navigate your entire site using only a keyboard, no mouse, trying every primary user flow from landing through checkout or enquiry. Third, test with an actual screen reader. VoiceOver is available free on macOS and iOS devices. NVDA is a free, powerful option for Windows. Spend at least twenty minutes navigating your core flows with a screen reader before and after making changes.

Common Pitfalls and How to Avoid Them

The most frequently missed WCAG 2.2 criteria in real-world audits cluster around a small number of recurring mistakes. Missing or inadequate alt text on images, especially in content management systems where authors can leave the alt field blank, is the single most common failure. Auto-playing video with audio that cannot be paused by the user violates Level A requirements. Inconsistent heading structure, skipping from h2 directly to h4, or using headings for visual styling rather than document structure, breaks navigation for screen-reader users who rely on heading lists to orient themselves. Modal dialogs that don’t trap focus properly or that can’t be closed via keyboard are another frequent and serious failure. Forms that display error messages without moving focus to the error, or that don’t associate the error message with the input programmatically, leave users stranded without knowing what went wrong.

Accessibility by Industry and Project Type

The same WCAG principles apply across all sectors, but the practical priority shifts depending on what you’re building. Healthcare websites need accessible appointment booking forms, legible medical content, and clearly labelled emergency contact information. The Baros Trust website we developed for a Chennai-based healthcare trust prioritised clear service navigation and optimised enquiry pathways to make the user journey accessible and intuitive. E-commerce sites benefit most from accessible product descriptions, filterable search results, and checkout flows that work smoothly with assistive technology. Educational platforms need accessible course content, quizzes, and navigation, as demonstrated by the custom learning management system we built for KV School of Psychology, which included student registration, course access controls, and interactive quizzes.

For lifestyle and wellness brands, accessible Instagram content and social posts matter because that is where discovery happens. Our social media management service addresses platform-level accessibility by ensuring caption text, video subtitles, and image descriptions are part of the content strategy. Professional services sites, law firms, consultants, clinics, need accessible contact forms and clear information architecture so potential clients can find and reach the business without barriers. When we built the website for Dr Raj Palaniappan, a bariatric surgeon in Chennai, we focused on responsive design and navigable content sections so patients can access information about procedures, credentials, and contact options across all devices.

Building Accessibility into Your Process, Not Patching It Later

Retrofitting accessibility onto an existing site is significantly more expensive and disruptive than building it in from the start. Every accessibility decision made during design and development compounds: semantic HTML established early means no rework later. A colour palette chosen with contrast in mind means no redesign to pass AA ratios. Keyboard-navigable components built from the start mean no retrofitting of JavaScript event handlers. This is why accessibility should be a criterion in your design brief, not an afterthought.

For teams that are maintaining an existing site, the priority should be high-impact, high-traffic pages. Audit your analytics to identify the twenty percent of pages that receive eighty percent of your traffic. Start with those. Fix the keyboard traps, missing alt text, and contrast failures on those pages first, then work outward. Every new page or feature should be evaluated against WCAG 2.2 as it is developed, not after it goes live. This incremental approach means you steadily improve overall conformance without the cost and disruption of a full-site overhaul.

Frequently asked questions

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 introduces nine new Level A and AA success criteria that were not present in WCAG 2.1. These new criteria address authentication accessibility, consistent help-link placement, redundant entry prevention, dragging alternatives, target size minimums, accessible error handling, and focus management when sticky headers overlap focused elements. The earlier criteria from 2.0 and 2.1 remain in force, so 2.2 is fully backward-compatible. Sites already conformant at WCAG 2.1 Level AA need to evaluate the nine new criteria to confirm continued compliance under 2.2. The practical impact is most felt by sites with complex forms, authentication systems, and dynamic interface components.

Is WCAG 2.2 legally required?

WCAG 2.2 is not itself a law, but it is referenced by an increasing number of national and regional regulations. The Americans with Disabilities Act in the US, the European Accessibility Act covering the EU market, Canada’s Accessible Canada Act, Australia’s Disability Discrimination Act, and emerging frameworks in the UK, India, and Southeast Asia all reference WCAG, most commonly at Level AA, as the benchmark for digital accessibility compliance. The legal risk of non-compliance extends beyond regulatory fines to include accessibility-related litigation, which has been growing steadily across multiple jurisdictions. The safest approach is to treat WCAG 2.2 Level AA as the baseline standard your site should meet, regardless of which jurisdiction applies to your organisation.

How long does it take to make a website WCAG 2.2 compliant?

The timeline depends heavily on the starting point. A new site built with accessibility in mind from the design stage through development typically takes the same amount of time as a non-accessible site when accessibility is part of the standard process. Retrofitting an existing site can take anywhere from a few days for a small brochure site with minor issues to several weeks for a large e-commerce or SaaS platform with complex interactive components. The best approach is to run an initial audit to scope the work, prioritise the highest-impact issues first, and address accessibility incrementally across subsequent sprints or development cycles rather than trying to fix everything at once.

What is the fastest way to run a WCAG 2.2 compliance audit?

Start with an automated scan using a tool like WAVE, axe DevTools, or Lighthouse to identify low-hanging fruit such as missing alt text, low-contrast colour combinations, and empty or missing form labels. Then navigate your site’s primary user journeys using only the keyboard, checking for keyboard traps, visible focus indicators, and accessible form interactions. Finish with a screen-reader pass using VoiceOver or NVDA, spending at least twenty minutes on your most important pages and user flows. This three-step manual approach will surface the vast majority of real-world accessibility barriers more effectively than automated scanning alone. For a thorough evaluation, engaging an accessibility professional who can test with users who have disabilities provides the most complete picture.

Does my website need to meet AAA standards?

For most organisations, Level AA is the appropriate target. Level AAA criteria include sign language interpretation for prerecorded video, extended audio descriptions, and significantly higher colour contrast requirements that can be impractical for certain brand palettes. WCAG itself recommends that organisations not treat AAA as a blanket policy requirement because it is not possible to satisfy all AAA criteria for some types of content. If your organisation serves audiences with specific accessibility needs that AAA criteria address, or if you want to provide the most inclusive experience possible, pursuing AAA on specific content types is valuable. But for general legal compliance and broad usability, Level AA remains the widely accepted standard.

How do I maintain WCAG 2.2 compliance over time?

Accessibility compliance is not a one-time achievement; it degrades as content and features change. Every new page, form, media asset, or interactive component introduced to your site needs to be evaluated against the same standards. The most effective maintenance approach is to establish an accessibility style guide that documents your colour contrast values, heading structure conventions, alt text standards, and form design patterns. Train content creators, designers, and developers on the guide. Include accessibility checks in your content publication workflow. Conduct a full re-audit at least annually, and after any major site redesign or migration. If you work with an agency on ongoing web design and development, ensure accessibility is a standing requirement in your engagement scope.

If your website needs a full accessibility audit or a redesign that puts WCAG 2.2 compliance at the centre of the process, the team at Monk Creatives can help. We build accessible, performant websites for brands in healthcare, e-commerce, fitness, education, and beyond. Reach us at info@monkcreatives.com or visit our contact page to start a conversation about your project.

Leave a Reply

Your email address will not be published. Required fields are marked *

Let's Create Together

Tell us about your brand — our creative team gets back to you fast with fresh ideas and clear next steps.

  • Branding, design & content that stands out
  • A dedicated creative team for your brand
  • Transparent pricing — no hidden fees

Get a Free Consultation

Takes 30 seconds

Select a service…
  • Branding & Identity
  • Logo Design
  • Graphic Design
  • Web Design & Development
  • Social Media Management
  • Content Creation
  • Search Engine Optimization (SEO)
  • Digital Marketing
  • Video & Motion
  • Other