SoftwareTestPilot
QA StrategyPublished: 12 min read

Accessibility Testing — WCAG 2.2 Complete Guide for QA (2026)

Ship WCAG 2.2 AA in every release: axe-core in CI, keyboard-only test scripts, screen reader checks, and the 12 automated + 8 manual tests that catch 90% of a11y bugs.

Avinash K
Founder & QA Engineer at SoftwareTestPilot
Share:XLinkedInWhatsApp
WCAG 2.2 accessibility testing checklist for QA teams.
WCAG 2.2 accessibility testing checklist for QA teams.

Last updated 2026-07-20 · 12 min read · By Avinash K

Accessibility is no longer optional — the EU Accessibility Act (June 2025) and updated ADA guidance mean WCAG 2.2 AA is now a legal baseline for most consumer products. Automation catches ~30-40% of issues; the rest need keyboard and screen reader passes. This guide gives you both.

Key takeaways

  • The 12 axe-core rules that catch the highest-impact bugs.
  • Keyboard-only test script (10-minute pass per page).
  • Screen reader setup for macOS, Windows, and iOS.
  • How to add a11y as a merge-block in CI.

1. axe-core in Playwright CI

import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test('home page has no serious a11y violations', async ({ page }) => {
  await page.goto('/');
  const results = await new AxeBuilder({ page })
    .withTags(['wcag2a', 'wcag2aa', 'wcag22aa'])
    .analyze();
  const serious = results.violations.filter(v => ['serious', 'critical'].includes(v.impact));
  expect(serious).toEqual([]);
});

Fails on serious/critical only — noisy rules like color-contrast on ads live in the report but do not block merge until triaged.

2. Keyboard-only pass (10 min per page)

  1. Unplug the mouse. Really.
  2. Tab through — every interactive element visible focus?
  3. Shift+Tab reverses cleanly, no traps?
  4. Skip link jumps to main content?
  5. Enter activates buttons; Space toggles checkboxes?
  6. Escape closes modals?
  7. Arrow keys navigate menus, tabs, sliders?
  8. Focus returns to trigger after modal close?

3. Screen reader quick check

macOS: VoiceOver (Cmd+F5). Windows: NVDA (free). iOS: VoiceOver (Triple-click Home/Side). Read the first 5 headings — do they describe the page? Read a form — does every input announce its label and error state? That is 80% of the SR check.

4. The merge-block checklist

Block the PR on: (a) no critical/serious axe violations, (b) new pages have manual keyboard sign-off, (c) contrast ≥4.5:1 on body text and 3:1 on UI, (d) images have alt or role="presentation". Reference: W3C WCAG 2.2 Quick Reference. Related: Playwright locators guide, shift-left playbook.

Frequently asked questions

1.Automation alone enough?
No. Axe catches ~30-40% of WCAG issues. Keyboard + screen reader passes are still required for AA compliance.
2.WCAG 2.1 or 2.2?
2.2 AA is the current baseline as of Oct 2023 and required by the EU Accessibility Act. 2.1 is now legacy.
3.Do component libraries fix this for me?
shadcn, Radix, Reach, and Material handle keyboard + ARIA well when used unchanged. Custom styling often breaks focus indicators — always retest.
4.What about PDFs and videos?
PDFs need tagged structure; videos need captions + audio description. Both are usually the biggest gaps in a11y audits.