Accessibility testing · WCAG 2.2 AA audit

Accessibility testing against WCAG 2.2 AA

Accessibility testing checks whether people using a keyboard, a screen reader, zoom or high contrast can use your product, measured against the WCAG 2.2 Level AA success criteria. I combine automated scans with manual testing of every criterion on your key screens, and give you a prioritized fix plan.

What I test

  • All WCAG 2.2 Level A and AA success criteria on your key screens
  • Keyboard-only use: every action reachable, focus visible and never hidden
  • Screen readers: NVDA with Firefox, VoiceOver on macOS and iOS
  • 200% and 400% zoom, reflow at 320 px, contrast and high-contrast mode
  • Forms, errors, custom components such as date pickers and dropdowns

What you get

  • A report with each failing criterion, where it fails, its impact and how to fix it
  • Walkthroughs of key tasks with assistive technology
  • A fix plan grouped by shared component, so fixes go further
  • Automated accessibility checks added to your Playwright suite to prevent regressions
  • A re-test after fixes, and a draft accessibility statement if you need one

Why now

The European Accessibility Act has applied to many consumer-facing digital services in the EU since 28 June 2025. Whether it applies to your product is a legal question; an audit gives you the technical picture either way, and accessibility fixes usually make the product easier for everyone.

See what you get

All sample reports →

FAQ

Isn't an automated scanner enough?

Scanners find around a third of issues. Keyboard traps, confusing screen reader output and inaccessible custom components need manual testing.

Do you provide a legal compliance certificate?

No. You get a technical audit against WCAG 2.2 AA. Legal obligations are for your lawyer to assess.

Need to know where you stand on WCAG 2.2? In 15 minutes I'll tell you how I'd check.

Book a 15-min call

Prefer writing? Use the contact form. Replies within one business day, from me.