Accessibility Testing (WCAG)
Our accessibility testing services check your website or app against WCAG 2.2 AA and give your developers a clear, prioritized list of what to fix. We combine automated tools such as axe and Lighthouse with manual testing, as part of our QA testing services. Accessibility issues often surface alongside functional ones, which we cover in website QA testing.
Quick answer
What is Accessibility Testing?
Accessibility testing services evaluate whether people with disabilities can use a website or app, usually measured against WCAG 2.2 Level AA. A thorough test combines automated scans with manual checks using a keyboard, screen readers, zoom and color contrast tools, then documents each issue with the affected criterion and a recommended fix.
What you get with accessibility testing.
- Automated scans with axe and Lighthouse across key templates
- Manual keyboard-only testing of navigation, forms and interactive components
- Screen reader testing with VoiceOver and NVDA
- Color contrast, zoom, reflow and text spacing checks
- Issue log mapped to WCAG 2.2 success criteria with severity and fixes
- Retesting after fixes
- Guidance on keeping new content and components accessible
Who it's for
- Organizations that need to meet WCAG 2.2 AA in policy, contracts or procurement
- Teams that received an accessibility complaint and need a clear remediation plan
- Product teams that want accessibility built into their release process
How we deliver accessibility testing.
- 1
Scope
We select representative pages, templates and user journeys, such as navigation, forms, checkout and account areas.
- 2
Scan
Automated tools flag issues such as missing alt text, contrast failures and missing form labels across many pages quickly.
- 3
Test manually
We work through each journey with a keyboard, screen readers and zoom, finding the issues automated tools cannot judge.
- 4
Report and retest
You get a prioritized fix list your developers can act on, and we verify the fixes. Ongoing checks can run in your automated testing pipeline.
What is WCAG 2.2 AA?
WCAG 2.2 AA is a level of conformance with the Web Content Accessibility Guidelines version 2.2, published by the W3C. The guidelines are organized under four principles (perceivable, operable, understandable and robust) and each success criterion is rated A, AA or AAA. Level AA means meeting all A and AA criteria, and it is the level most commonly referenced in accessibility policies and standards.
Compared with WCAG 2.1, version 2.2 adds criteria such as focus not being hidden behind other content, minimum target sizes for controls, alternatives to dragging movements, consistent placement of help, and less reliance on memory tests during authentication.
Are automated accessibility checkers enough?
No. Automated tools like axe and Lighthouse are useful for catching common, clear-cut issues at scale, but many WCAG criteria require human judgment. A tool can detect that an image has no alt text, but not whether the alt text that exists is meaningful.
Manual testing finds problems such as illogical focus order, keyboard traps, unclear error messages, custom components that screen readers announce incorrectly and content that breaks when zoomed. That is why every audit we run includes both.
Accessibility is easiest and cheapest when it is built in from the start. If you are planning a new site, our business website development team designs with WCAG in mind. Testing reduces risk but is not a legal certification; for questions about your obligations, consult legal counsel, and contact us to scope an audit.
More QA & Testing services
QA & Testing overview- Website QA TestingStructured testing of forms, checkout, tracking and layouts across browsers and devices before and after you launch.
- Mobile App TestingFunctional, usability and compatibility testing of iOS and Android apps on real devices before every release.
- Automated Testing (Playwright & Cypress)End-to-end test suites in Playwright or Cypress that run in your CI pipeline and catch regressions before release.
- Performance & Load TestingLoad, stress and spike testing with k6 or JMeter to find bottlenecks before a launch or campaign does.
Accessibility testing questions.
Testing against WCAG 2.2 AA and fixing the issues found is the generally accepted way to make a site accessible, but we do not provide legal advice or certification. For questions about your specific legal obligations, speak with qualified counsel.
Overlay widgets do not fix underlying issues in code, and they can interfere with assistive technology users rely on. Fixing the site itself is the reliable approach.
Yes. We test iOS and Android apps with VoiceOver and TalkBack, dynamic text sizes and other platform accessibility settings, using WCAG principles as the reference.
Cost depends on the number of templates and journeys, whether apps are included and how many retest rounds you need. Our pricing page explains how we scope audits.
Run a full audit before major launches or redesigns, and add automated checks to every release so new issues are caught early. Periodic manual reviews keep new content and components on track.
Ready to talk about accessibility testing?
Get a free, manual review of your marketing from a senior strategist, with prioritized recommendations you can act on, whether or not you hire us.