Accessibility WCAG 2.2 Compliance

Website Accessibility: A Practical Guide to WCAG 2.2

Website accessibility in practice: what WCAG 2.2 requires, five common barriers including puzzle CAPTCHAs, and a checklist you can work through today.

Published May 05, 2026 · 8 min read · Updated Oct 12, 2026

Key takeaways

Accessibility starts with readable text
Website accessibility means people with disabilities can use your site without help, and WCAG 2.2 level AA is the usual target. The most common failures are text and contrast: body text should render at 15 to 16 px or more, with a contrast ratio of at least 4.5:1.
Keyboard operability is a hard requirement
Every interactive element (links, buttons, forms, modals) must be reachable and usable without a mouse. The test takes five minutes: put the mouse aside and navigate with Tab, Enter and the arrow keys only.
WCAG 2.2 AA is the right target
EU accessibility law relies on the harmonized standard EN 301 549, whose current version references WCAG 2.1 level AA. WCAG 2.2, published in October 2023, is the current W3C recommendation and a sensible target. It adds nine success criteria, including SC 3.3.8, which affects CAPTCHAs in login flows.
Puzzle CAPTCHAs can fail WCAG 2.2 SC 3.3.8
Reading distorted text or picking images is a known problem for people with visual, cognitive or motor impairments. SC 3.3.8 says no login step may require a cognitive function test, such as solving a puzzle or transcribing text, unless an alternative method or a mechanism to help the user is available. Object recognition and the user's own content are exceptions at level AA.
On this page
  1. What website accessibility means
  2. Five barriers your website may already be creating
  3. What WCAG 2.2 requires
  4. An accessibility checklist you can use today
  5. How to prioritize if you are starting from zero
  6. Accessibility as a quality standard
Share this post

What website accessibility means

Website accessibility means that people with disabilities can perceive, operate and understand your site, with or without assistive technology. Around one in four adults in the EU lives with some form of disability. For many of them, whether your website works is not a minor inconvenience. It decides whether they can complete a task on their own or not at all.

Accessibility has also become a legal baseline. The European Accessibility Act (EAA) has applied to a wide range of digital products and services since June 2025. Even for teams that no regulation covers yet, the practical case is strong: better structure, better SEO, more reach and fewer frustrated users.

This guide covers what website accessibility looks like in practice: five specific barriers your site may already have, how WCAG 2.2 translates into real decisions, and a checklist to help you prioritize the work.

Five barriers your website may already be creating

Most accessibility problems on the web come down to a short list of recurring patterns. These five barriers shut out the largest number of people.

1. Text that is difficult or impossible to read

Low contrast, small font sizes and overly complex language make each other worse. Someone with a moderate visual impairment may cope with one of these problems, but rarely with all three.

The practical baseline: body text should render at 15 to 16 px or more, with a contrast ratio of at least 4.5:1 against its background (the WCAG AA threshold). For large text (at least 18 pt, or 14 pt bold, which is roughly 24 px and 19 px) the threshold drops to 3:1. Tools like WebAIM’s contrast checker test any color pair in seconds.

Plain language is harder to test automatically, but it matters a lot for people with cognitive disabilities or lower literacy. Short sentences, active voice and no unexplained jargon all help.

2. Images with no text alternative

A web page with an image and its text alternative, high-contrast text and a button with a visible focus ring, surrounded by icons for accessibility, vision, audio and keyboard use

A screen reader user reaches an image and hears nothing or, worse, a raw file name like img_20240312_banner_v3.jpg read out letter by letter.

The fix is alt text: a short, accurate description of what the image shows and, where relevant, what it says. Decorative images that add no meaning should carry an empty alt="" attribute so screen readers skip them. Images of text are a particular problem: the text belongs in the document itself, not inside a graphic.

This is one of the fastest accessibility fixes and one of the most often overlooked. Every image on your site should either have descriptive alt text or be marked as decorative.

3. Video and audio with no captions or transcripts

A deaf or hard-of-hearing user cannot follow audio-only content. Someone with cognitive or attention difficulties may take in a written transcript far more easily than spoken narration. Captions (synchronized text shown during playback) help the first group. A full transcript, available separately, helps both.

For marketing content, product demos and webinars, people now expect captions. Most video platforms offer automatic captions, and they have improved a lot, but auto-generated captions still get technical terms and product names wrong, so review them before publishing.

4. Keyboard traps and inaccessible navigation

Not everyone uses a mouse. People with motor impairments, screen reader users and people who simply prefer the keyboard all navigate with Tab, Enter and the arrow keys. A site that only works with a pointing device shuts out a large part of that group.

Keyboard accessibility comes with concrete requirements: every interactive element (links, buttons, form fields, dropdowns, dialogs) must be reachable with Tab; the current focus position must be visible at all times; modals must not trap the focus; and the focus order must follow a logical sequence that matches the visual layout.

Testing this takes five minutes and no tools: put your mouse aside and move through your site using only Tab, Shift+Tab, Enter and the arrow keys. If you get stuck, cannot see where you are or cannot activate an element, you have keyboard accessibility issues.

5. Forms and CAPTCHAs that people cannot get past

Checks in a login flow under WCAG 2.2 SC 3.3.8 at level AA: solving a puzzle or transcribing text only with an alternative method or a mechanism that helps, recognizing objects or your own content is an exception at level AA, and a check that runs in the background asks for no test at all

Forms are where accessibility matters most. Contact pages, login flows, registration screens and checkout pages are where people get things done: someone who cannot complete the form cannot do what they came for.

Traditional image-based CAPTCHAs are among the best documented accessibility problems in web design. Reading distorted letters or picking images that contain certain objects is a known problem for people with visual impairments, people with cognitive disabilities and screen reader users. Audio alternatives help, but they create their own difficulties for people with hearing impairments, and the audio versions of common CAPTCHAs are often hard even for people without any impairment.

WCAG 2.2 addresses this directly. Success Criterion 3.3.8, Accessible Authentication (Minimum), says no step in an authentication process may require a cognitive function test, such as solving a puzzle or transcribing text, unless an alternative method or a mechanism to help the user is available. Tests that ask users to recognize objects or identify content they provided themselves are exceptions at level AA.

The practical fix is to replace challenge-based CAPTCHAs with an accessible CAPTCHA. TrustCaptcha runs bot detection in the background while a visitor fills in a form, so there is no puzzle to solve, no image to interpret and nothing to click. The check happens during normal interaction and does not interrupt the form for anyone. This approach is in line with WCAG 2.2 SC 3.3.8 and removes one of the most common barriers from the flows where people most need to succeed.

What WCAG 2.2 requires

The Web Content Accessibility Guidelines (WCAG) are the international standard for accessible web content. Published by the W3C, they are the basis for most national and EU accessibility laws. The current version is WCAG 2.2, published in October 2023. EU accessibility law (the Web Accessibility Directive and the European Accessibility Act) relies on the harmonized standard EN 301 549, whose current edition references WCAG 2.1 level AA.

WCAG is built on four principles: content must be perceivable, operable, understandable and robust, often shortened to POUR. Each principle is split into guidelines, and each guideline into testable success criteria.

The conformance levels define what “compliant” means in practice:

  • Level A: the minimum. Failing level A criteria creates serious barriers for people who use assistive technology.
  • Level AA: the legal target in most jurisdictions, including the EU. This is what “WCAG compliance” usually means.
  • Level AAA: the highest level. No law requires it, and it is often impractical for a whole site, but it is achievable for specific high-priority components.

WCAG 2.2 added nine success criteria to WCAG 2.1. The most important additions cover focus appearance (making keyboard focus easier to see), accessible authentication (which directly affects how CAPTCHAs and login flows are designed) and alternatives to drag-and-drop. WCAG 2.2 is backwards compatible: meeting 2.2 AA also satisfies all 2.1 AA criteria, apart from one removed criterion (4.1.1 Parsing, obsolete in 2.2).

For most business websites, WCAG 2.2 level AA is the right goal and the legally relevant one.

An accessibility checklist you can use today

This is a practical starting point, organized by area, not a full audit. Work through it from the top.

Text and visual presentation

  • Body text renders at 15 px or larger
  • Contrast ratio is at least 4.5:1 for body text, 3:1 for large text
  • Text can be resized to 200% in the browser without losing content or function
  • No content is presented as text inside an image (except logos and decorative graphics)
  • Language and reading level suit your audience

Images and media

  • Every meaningful image has accurate alt text
  • Decorative images carry alt=""
  • Videos have accurate, synchronized captions
  • Audio-only content has a written transcript

Keyboard and navigation

  • All interactive elements are reachable and usable with the keyboard alone
  • The focus indicator is clearly visible at all times
  • No keyboard traps in modals, dialogs or custom components
  • A skip link appears at the top of each page
  • Tab order matches the visual reading order

Forms and authentication

  • Form labels are programmatically linked to their inputs via for/id or aria-labelledby
  • Error messages name the field that failed and explain how to fix it
  • No fixed time limits on completing a form, unless users can adjust them
  • No CAPTCHA that requires solving an image puzzle or an audio challenge
  • Authentication flows do not require cognitive function tests (WCAG 2.2 SC 3.3.8)

Structure and semantics

  • Headings follow a logical hierarchy without skipped levels
  • Landmark regions are used (header, nav, main, footer)
  • Each page has a descriptive and unique <title> element
  • Links use descriptive anchor text, not “click here” or “read more”
  • Tables define headers with <th> and appropriate scope attributes

How to prioritize if you are starting from zero

Where to start: in the first two weeks, high impact and low effort fixes such as image alt text, contrast failures, form labels linked to their fields and errors flagged by automated tools; in the next month, keyboard navigation and focus, modals, dropdowns and custom controls, and replacing puzzle CAPTCHAs; ongoing, heading hierarchy, reading level and captions on new videos. A WCAG 2.2 AA baseline takes two to four weeks of focused work on a typical business website

A full accessibility audit of an established site can turn up hundreds of issues. If you are starting without any prior accessibility work, sort the tasks by impact and effort instead of trying to fix everything at once.

First two weeks: Fix the high-impact, low-effort items. That almost always means image alt text, contrast failures and form labels that are not linked to their fields. Run your site through Lighthouse (built into Chrome DevTools) or the WAVE browser extension and fix everything flagged as an error (an error, not a warning). These are hard failures that the tools catch reliably.

Next month: Work on keyboard navigation and focus management. This needs manual testing and often a developer for interactive components (modals, dropdowns, custom form controls) that automated tools only partly check. Replace any puzzle-based CAPTCHA in this phase too: it makes a big difference and is technically simple to do.

Ongoing: Structural and content accessibility (heading hierarchy, reading level, captions on new videos) becomes part of how you produce content, not a one-time cleanup.

Reaching a WCAG 2.2 AA baseline on a typical business website takes two to four weeks of focused development work, more for sites with complex interactive components or large content archives.

Accessibility as a quality standard

Accessibility is not a one-time audit or a compliance checkbox. It is an ongoing quality standard, and WCAG 2.2 level AA is both achievable and increasingly expected. The five barriers described here cause most of the problems that shut people out of websites, and most of them take less time to fix than teams expect.

One of the quickest wins for form accessibility is replacing a puzzle-based CAPTCHA with an invisible CAPTCHA that verifies visitors without a task. Try TrustCaptcha free: designed for WCAG 2.2, with EU hosting on every plan.

FAQs

Is website accessibility legally required?
It depends on who you are and what you offer. The Web Accessibility Directive has applied to EU public-sector websites in stages from 2018 to 2020. The European Accessibility Act has extended requirements to many private-sector consumer services since June 2025. If no specific law covers you yet, accessibility is not a hard legal requirement today, but the scope keeps growing, and building to WCAG 2.2 AA now costs far less than retrofitting under a deadline.
What is the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2, published in October 2023, adds nine success criteria to the previous version. For most teams the most relevant ones cover visible keyboard focus, accessible authentication (which directly affects CAPTCHA and login design) and alternatives to dragging gestures. WCAG 2.2 is backwards compatible: a site that meets 2.2 AA also meets 2.1 AA, apart from one removed criterion (4.1.1 Parsing, obsolete in 2.2).
Can automated tools catch all accessibility issues?
No. Automated testing tools (Lighthouse, WAVE, axe and similar) reliably find roughly 30 to 40% of WCAG failures. The rest needs manual testing: walking through the site with a keyboard, testing with a screen reader and judging how clear the content is. Automated tools are a necessary starting point, but they do not replace a manual review.
What makes TrustCaptcha accessible?
TrustCaptcha runs its proof-of-work check in the background while people use a form as usual. They never see a puzzle, an image selection task or an audio challenge. That removes exactly the barrier WCAG 2.2 SC 3.3.8 targets: a cognitive function test in an authentication flow. It also removes the audio CAPTCHA problem, since no challenge is shown in the first place.
How does accessibility relate to SEO?
Closely. Many accessibility requirements overlap with what search engines use to understand and rank content: descriptive page titles, a clear heading hierarchy, descriptive link text, image alt attributes and a logical document structure. A site that meets WCAG 2.2 AA is usually also easier for search engines to crawl and understand.
Do I need a specialist to make my site accessible?
Not necessarily. A developer who knows semantic HTML and the WCAG success criteria well can fix most issues on a typical business website without outside help. For large or complex sites, especially those with many interactive components or big content archives, a specialist audit finds issues faster than testing on your own, and it is often worth it before a compliance deadline.

Stop bots and spam

Stop spam and protect your website from bot attacks. Secure your website with our user-friendly and GDPR-compliant CAPTCHA.