---
title: 'Accessibility Testing Tutorial: WCAG 2.2: Free Online Course'
description: 'A free, hands-on accessibility testing course: WCAG 2.2 in practice,
  manual keyboard and screen reader checks, axe-core with Playwright and Selenium,
  baselines, real fixes, CI and a cloud grid.'
source_url:
  html: https://testingbot.com/resources/courses/accessibility-testing
  md: https://testingbot.com/resources/courses/accessibility-testing.md
---

Course

[Accessibility Testing Tutorial: WCAG 2.2](https://testingbot.com/resources/courses/accessibility-testing)

Chapter 1 of 10

1. [1 Accessibility Testing Tutorial: WCAG 2.2 in Practice](https://testingbot.com/resources/courses/accessibility-testing)
2. [2 Manual Accessibility Checks You Still Need](https://testingbot.com/resources/courses/accessibility-testing/manual-accessibility-checks)
3. [3 axe-core with Playwright: Your First Scan](https://testingbot.com/resources/courses/accessibility-testing/axe-core-with-playwright)
4. [4 axe-core with Selenium in Java](https://testingbot.com/resources/courses/accessibility-testing/axe-with-selenium-java)
5. [5 Scoping Scans, Rules and a Baseline of Known Issues](https://testingbot.com/resources/courses/accessibility-testing/scoping-rules-and-baselines)
6. [6 Fixing Common Violations: Contrast, Forms and ARIA](https://testingbot.com/resources/courses/accessibility-testing/fixing-common-violations)
7. [7 Running Accessibility Checks in CI](https://testingbot.com/resources/courses/accessibility-testing/accessibility-checks-in-ci)
8. [8 Accessibility Testing on TestingBot](https://testingbot.com/resources/courses/accessibility-testing/accessibility-testing-on-testingbot)
9. [9 What Automated Accessibility Testing Cannot Catch](https://testingbot.com/resources/courses/accessibility-testing/what-automation-cannot-catch)
10. [10 Knowledge check](https://testingbot.com/resources/courses/accessibility-testing/knowledge-check)

[Exit course](https://testingbot.com/resources/courses)

 Chapter 1 of 10 Intermediate 7 min read 1 quick check Updated Nov 2026 

# Accessibility Testing Tutorial: WCAG 2.2 in Practice

A free, hands-on accessibility testing course: WCAG 2.2 in practice, manual keyboard and screen reader checks, axe-core with Playwright and Selenium, baselines, real fixes, CI and a cloud grid.

## What you will learn

1. Accessibility Testing Tutorial: WCAG 2.2 in Practice
2. [Manual Accessibility Checks You Still Need](https://testingbot.com/resources/courses/accessibility-testing/manual-accessibility-checks)
3. [axe-core with Playwright: Your First Scan](https://testingbot.com/resources/courses/accessibility-testing/axe-core-with-playwright)
4. [axe-core with Selenium in Java](https://testingbot.com/resources/courses/accessibility-testing/axe-with-selenium-java)
5. [Scoping Scans, Rules and a Baseline of Known Issues](https://testingbot.com/resources/courses/accessibility-testing/scoping-rules-and-baselines)
6. [Fixing Common Violations: Contrast, Forms and ARIA](https://testingbot.com/resources/courses/accessibility-testing/fixing-common-violations)
7. [Running Accessibility Checks in CI](https://testingbot.com/resources/courses/accessibility-testing/accessibility-checks-in-ci)
8. [Accessibility Testing on TestingBot](https://testingbot.com/resources/courses/accessibility-testing/accessibility-testing-on-testingbot)
9. [What Automated Accessibility Testing Cannot Catch](https://testingbot.com/resources/courses/accessibility-testing/what-automation-cannot-catch)
10. [Knowledge check](https://testingbot.com/resources/courses/accessibility-testing/knowledge-check)

[Continue where you left off](https://testingbot.com#)

## TestingBot Accessibility Testing Certification

Turn this course into a free, resume-worthy credential: pass the exam, run the course suite on TestingBot, and get a verifiable certificate for your LinkedIn profile.

[How it works](https://testingbot.com/resources/courses/accessibility-testing/certification)On this page
1. [WCAG 2.2 in five minutes](https://testingbot.com#wcag-2-2-in-five-minutes)
2. [Automated and manual testing](https://testingbot.com#automated-and-manual-testing)
3. [How the course is organised](https://testingbot.com#how-the-course-is-organised)
4. [What you'll build](https://testingbot.com#what-you-ll-build)
5. [Prerequisites](https://testingbot.com#prerequisites)

_Last reviewed November 2026 against axe-core 4.14, @axe-core/playwright 4.14.0, @playwright/test 1.65.0 and Selenium 4.52._

Accessibility testing checks whether people with disabilities can use your site: people who navigate with a keyboard or a switch instead of a mouse, who listen to the page through a screen reader, who zoom to 400%, who cannot tell red from green. In practice that means checking your pages against the Web Content Accessibility Guidelines (WCAG), the W3C standard that most accessibility laws and procurement rules point to.

This course is hands-on. You will scan real pages with axe-core from Playwright and from Selenium, read and fix the violations it reports, keep a baseline so an existing backlog does not block every pull request, run the checks in CI and on a cloud browser grid, and, just as important, learn which checks no tool can do for you.

## WCAG 2.2 in five minutes[#](https://testingbot.com#wcag-2-2-in-five-minutes)

WCAG 2.2 became a W3C Recommendation in October 2023. It is organised in three layers:

- **Four principles** , usually abbreviated POUR. Content must be **Perceivable** (text alternatives, captions, enough contrast), **Operable** (keyboard access, enough time, no seizure-inducing flashes), **Understandable** (readable, predictable, helps people avoid and fix mistakes) and **Robust** (works with assistive technology).
- **Guidelines** under each principle, such as 1.4 "Distinguishable" or 2.1 "Keyboard Accessible".
- **Success criteria** , the testable statements. Each has a number and a level: **A** (the minimum), **AA** (what laws and contracts usually require) or **AAA** (stricter, rarely required for a whole site). "WCAG 2.2 AA" means every A and AA criterion is met.

The criteria you will meet most often in this course:

| Criterion | Level | In plain words |
| --- | --- | --- |
| 1.1.1 Non-text Content | A | Images and icon buttons have a text alternative |
| 1.3.1 Info and Relationships | A | Structure (headings, labels, lists) is in the markup, not just the styling |
| 1.4.3 Contrast (Minimum) | AA | Text has at least 4.5:1 contrast (3:1 for large text) |
| 1.4.10 Reflow | AA | Content works at 320 CSS pixels wide without horizontal scrolling |
| 2.1.1 Keyboard | A | Everything works with a keyboard alone |
| 2.4.7 Focus Visible | AA | You can see which element has keyboard focus |
| 2.5.8 Target Size (Minimum) | AA | Click targets are at least 24 by 24 CSS pixels, or have enough space around them |
| 4.1.2 Name, Role, Value | A | Controls expose a name and role that assistive technology can read |

WCAG 2.2 added nine success criteria to 2.1. Six of them are at A or AA: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication (Minimum). It also removed 4.1.1 Parsing, which modern browsers made obsolete. Because 2.2 is backwards compatible, a page that meets 2.2 AA also meets 2.1 AA and 2.0 AA.

### Why teams test against it[#](https://testingbot.com#why-teams-test-against-it)

Regulation is the usual trigger. In the EU, the European Accessibility Act has applied since 28 June 2025 to many consumer-facing digital products and services, such as online shops and banking, and its harmonised standard, EN 301 549, builds on WCAG. In the US, the Department of Justice's 2024 rule for state and local government websites references WCAG 2.1 AA. Check what applies to you with someone qualified to say; this course teaches the testing, not the law.

The better reason is that accessibility bugs are ordinary bugs. An unlabeled input, a button that only works with a mouse or grey-on-grey text is a defect that some of your users hit every day, and like any defect it is cheaper to catch in a pull request than in a complaint.

## Automated and manual testing[#](https://testingbot.com#automated-and-manual-testing)

There are two halves to accessibility testing, and you need both.

**Automated checks** run a rules engine over the rendered page. They are fast, repeatable and good at the mechanical criteria: missing alt attributes, missing form labels, insufficient contrast, invalid ARIA. This course uses [axe-core](https://github.com/dequelabs/axe-core), the open-source engine from Deque that most testing tools embed, including TestingBot's own accessibility checks.

**Manual checks** cover what a rules engine cannot judge: whether alt text actually describes the image, whether the focus order makes sense, whether a screen reader user can complete checkout. Automated tools only ever cover part of WCAG. Deque's own study of its audit data reported that axe-core found about 57% of issues by volume, and far fewer of the criteria; chapter 8 shows concrete examples of markup that passes every automated rule and still fails real users.

So the workflow this course builds is: manual checks while you develop a feature, automated checks on every commit so nothing regresses, and periodic manual audits of the critical journeys.

A contract says your web app must meet "WCAG 2.2 Level AA". Which success criteria does that include?

 Only the criteria marked AA Only the nine criteria that are new in 2.2 Every Level A and every Level AA criterion in WCAG 2.2 Every criterion at A, AA and AAA

Conformance levels are cumulative: AA means all A criteria plus all AA criteria. Meeting only the AA ones would leave basics such as keyboard access (2.1.1, Level A) untested.

## How the course is organised[#](https://testingbot.com#how-the-course-is-organised)

1. Manual checks you must still do: keyboard, screen reader basics, zoom and reflow
2. axe-core with Playwright: your first automated scan
3. axe-core with Selenium in Java
4. Scoping scans, choosing rules and keeping a baseline of known issues
5. Fixing the common violations: contrast, forms and ARIA
6. Running accessibility checks in CI
7. Accessibility testing on TestingBot: the grid, `tb:accessibility` and scheduled scans
8. What automated accessibility testing cannot catch
9. A knowledge check

The examples run against public pages so you can copy them and watch them pass or fail: Playwright's TodoMVC demo (`demo.playwright.dev/todomvc`), a login form at `the-internet.herokuapp.com`, and Deque's deliberately inaccessible "Mars Commuter" demo at `dequeuniversity.com/demo/mars/`. Two small HTML pages, a broken and a fixed sign-up form, are loaded straight into the browser with `page.setContent()`.

If you need the product rather than the how-to, TestingBot's [automated accessibility testing](https://testingbot.com/features/accessibility-testing) runs these checks inside your existing tests and as scheduled scans of any URL; chapter 7 covers how that fits in.

## What you'll build[#](https://testingbot.com#what-you-ll-build)

- A TypeScript Playwright project that scans pages for WCAG 2.2 A and AA violations, in several UI states, with a shared fixture.
- A baseline file of known issues, so CI fails on new violations without first fixing years of backlog.
- A Java and JUnit 5 project that runs the same checks through Selenium.
- Keyboard, reflow and accessibility-tree tests for things axe does not check.
- A GitHub Actions workflow, and a config that runs the suite on Chrome, Firefox and Safari on TestingBot.

## Prerequisites[#](https://testingbot.com#prerequisites)

- Node.js 22 or newer, and basic TypeScript. If Playwright is new to you, the [Playwright tutorial](https://testingbot.com/resources/courses/playwright) covers the runner in depth.
- For chapter 3, a JDK (17 or newer) and Maven. The [Selenium with Java and TestNG course](https://testingbot.com/resources/courses/selenium-testng) covers Selenium itself.
- A TestingBot account for chapter 7 (the free trial is enough).
- No assistive technology experience is needed. Chapter 1 shows you how to start the screen reader already on your computer.

The course and its knowledge check are free and need no account. The optional [TestingBot certification](https://testingbot.com/resources/courses/accessibility-testing/certification) asks for a passed exam plus your accessibility suite running on TestingBot. It is issued by TestingBot; it is not an IAAP or W3C credential and does not certify that any website is compliant.

[Next · Chapter 2 Manual Accessibility Checks You Still Need](https://testingbot.com/resources/courses/accessibility-testing/manual-accessibility-checks)

On this page

1. [WCAG 2.2 in five minutes](https://testingbot.com#wcag-2-2-in-five-minutes)
2. [Automated and manual testing](https://testingbot.com#automated-and-manual-testing)
3. [How the course is organised](https://testingbot.com#how-the-course-is-organised)
4. [What you'll build](https://testingbot.com#what-you-ll-build)
5. [Prerequisites](https://testingbot.com#prerequisites)

Certification

Earn the free, resume-worthy TestingBot Accessibility Testing Certification for this course.

[How it works](https://testingbot.com/resources/courses/accessibility-testing/certification)

## Other free courses

- [Mobile App Testing: From First Test to CI A free, hands-on mobile app testing course: emulators vs real devices, Appium vs Espresso vs XCUITest vs Ma...](https://testingbot.com/resources/courses/mobile-app-testing)
- [Flaky Tests: Find, Fix and Prevent Fix flaky tests for good: measure them, then remove the four root causes (waits, shared data, test order, r...](https://testingbot.com/resources/courses/flaky-tests)
- [Manual Testing Course A hands-on manual testing course: test design, test cases, exploratory charters, bug reports developers act...](https://testingbot.com/resources/courses/manual-testing)
- [Selenium Locators and Locator Strategies A free course on Selenium locators and locator strategies: CSS selectors, XPath, role-based and test-id loc...](https://testingbot.com/resources/courses/locator-strategies)

[Browse all courses](https://testingbot.com/resources/courses)
