Skip to content
Quality Assurance Labs
QA Testing

WCAG 2.2 Accessibility Testing — Developer's Field Guide

Kawsher, Founder, QA Labs4 min readPublished Updated

Accessibility used to be a nice-to-have. In 2026, it's a legal requirement in the EU, US, and multiple APAC markets. Non-compliant products are exposed to fines, lawsuits, and lost enterprise deals. Here's how to actually test for it.

Braille controls and headphones beside an accessible interface
  • accessibility
  • WCAG-2.2
  • a11y
  • axe
  • screen-reader-testing

Short answer

WCAG 2.2 testing checks that people with disabilities can use your product, measured against the Web Content Accessibility Guidelines. Combine automated scanners such as axe or WAVE with keyboard-only and screen reader testing. The most common failures are contrast, missing labels and focus states. Add axe-core to CI so fixed issues stay fixed.

Key takeaways

  • WCAG 2.2 is law — not preference
  • Test with axe/WAVE + screen readers + keyboard-only
  • Contrast, labels, focus states are the top 3 issues
  • Respect prefers-reduced-motion
  • Add axe-core to CI to prevent regressions

Accessibility used to be a "nice to have." That era is over.

In 2026, accessibility is legally required in the EU (European Accessibility Act), US (ADA), and multiple APAC markets.

The four WCAG principles (POUR)

  • Perceivable — Can users perceive all content?
  • Operable — Can users interact with the product?
  • Understandable — Is content clear and predictable?
  • Robust — Does it work with assistive technologies?

Testing checklist

  • Automated tools: axe, WAVE, Lighthouse, Pa11y CI
  • Manual keyboard testing: Tab order, focus states, escape closes modals
  • Screen reader testing: VoiceOver, NVDA, TalkBack
  • Color and contrast: 4.5:1 (normal), 3:1 (large), 3:1 (UI)
  • Motion: respect prefers-reduced-motion
  • Forms: labels, error messages, required fields

What are the most common WCAG failures?

  • Missing alt text (still #1)
  • Contrast ratios under 4.5:1
  • Focus indicators removed by CSS resets
  • Unlabeled form inputs
  • Focus traps in modals
  • Motion without reduced-motion fallback
  • Interactive elements under 44×44px

What is new in WCAG 2.2?

  • Focus Not Obscured
  • Dragging Movements
  • Target Size Minimum (24×24)
  • Consistent Help
  • Accessible Authentication

WCAG levels: A, AA and AAA

Each WCAG success criterion has a level. Level A is the minimum, level AA adds the requirements most organisations aim for, and level AAA is the strictest. Most laws, public-sector rules and procurement requirements point to level AA, so that is the usual target, with AAA criteria adopted where they make sense.

How do you run a keyboard test?

  • Put the mouse away and use Tab, Shift+Tab, Enter, Space, the arrow keys and Escape
  • Check every link, button, field and menu can be reached and used
  • Check focus is always visible and never hidden behind sticky headers or banners
  • Check the focus order follows the visual order of the page
  • Open and close every dialog: focus should move into it and return when it closes

How do you run a screen reader test?

Use VoiceOver on Mac and iOS, NVDA on Windows (it is free) and TalkBack on Android. Complete one key task with the screen off or your eyes closed. Listen for a clear name, role and state on every control, check that headings let you jump through the page, and make sure form errors and status messages are announced when they appear.

Fixing issues in the right order

Start with anything that stops a user finishing a key task, such as an unlabelled button in checkout or a dialog that traps keyboard focus. Then fix problems that affect many pages through shared components, because one fix repairs them everywhere. Leave cosmetic issues until the blockers are gone.

Writing an accessibility statement

An accessibility statement tells users which standard you aim for, which known issues remain and when they will be fixed, and how to report a problem or ask for content in another format. Date it, and update it after each audit.

Accessible forms

  • Every field has a visible label tied to it in code
  • Required fields are marked in text, not only with color or an asterisk
  • Errors say what went wrong and how to fix it, next to the field
  • Users can review and correct data before a legal or financial submission
  • Sign-in allows password managers and pasting, so nobody has to memorise or retype a code (Accessible Authentication, new in WCAG 2.2)

Images, video and motion

  • Informative images have alt text that says what the image means; decorative images have empty alt text
  • Videos have captions, and audio has a transcript
  • Nothing flashes more than three times a second
  • Moving, auto-playing content can be paused, stopped or hidden
  • Animations are reduced when the user has turned on reduced motion

Testing with real users

Tools and expert audits find most issues, but people who use assistive technology every day find problems nobody predicted. Even a few sessions with screen reader, magnifier or switch users on your key journeys will show where the experience breaks down in practice.

Frequently asked questions

  • Do automated tools make us compliant? — No. Automated checks find only some WCAG failures. Keyboard and screen reader testing, and ideally testing with people who use assistive technology, are needed to find the rest.
  • Is WCAG 2.2 backwards compatible with 2.1? — Yes. Content that meets WCAG 2.2 also meets 2.1 and 2.0, apart from one 2.0 and 2.1 criterion that 2.2 removed as obsolete (4.1.1 Parsing).
  • How long does an accessibility audit take? — It depends on how many pages and journeys are in scope. Auditing a few key journeys is a sensible start, followed by fixing shared components before widening the audit.

How to make it continuous

  • Add axe-core to CI
  • Keyboard checklist in PR reviews
  • Quarterly manual audit with screen readers
  • Accessibility champion on every product team
  • User testing with people who use assistive tech

Free QA spot-check

Want a QA engineer to look at your product?

Send us your website or web app address. An engineer will test one key journey, such as sign-up, search or checkout, on desktop and mobile, and email you the most important issues we find. Free, and no call needed.

Related service

QA Testing →

Automated suites, manual deep-dives, and CI guardrails that catch regressions before your users do.

Further reading

About the author

Kawsher, Founder, QA Labs →

Kawsher is the founder of Quality Assurance Labs (QA Labs), the QA-first software testing and development company in Bogura, Bangladesh, founded in 2021. Every article and case study on this site is written or reviewed by Kawsher, drawing on the team's QA testing, AI, web, mobile, video and marketing work for SaaS and AI teams worldwide.

Notes from the lab.

Testing, engineering and growth — delivered to your inbox.

Need a WCAG 2.2 audit? Book a compliance sprint

Let's talk →