Resync Independent QA
Independent Accessibility Testing
for NZ Digital Products.
WCAG 2.1 AA compliance, manual screen reader testing, and NZ Government Web Accessibility Standard 1.1 — independently verified.
Accessibility Programmes Fail Quietly — Until Go-Live
These are the failure modes that reach production when quality assurance is left to the delivery team.
Legal and Regulatory Exposure
NZ government agencies are required to meet the Web Accessibility Standard 1.1 (based on WCAG 2.1 AA). Private sector organisations face Human Rights Act obligations. Inaccessible digital products are not just poor UX — they are a compliance and legal risk.
Manual Screen Reader Testing Is Skipped
Automated accessibility scanners catch approximately 30-40% of WCAG issues. The remaining issues — keyboard navigation, screen reader behaviour, focus management, and dynamic content — require manual specialist testing. Most QA teams run the scanner and call it done.
Mobile Accessibility Is Overlooked
A web product that passes WCAG testing on desktop may fail on mobile. Touch target sizes, gesture navigation, and VoiceOver/TalkBack behaviour are distinct failure modes that automated tools don’t test.
The Resync Approach
Resync provides independent WCAG 2.1 AA accessibility testing as part of your QA lifecycle. We combine automated scanning (axe, Lighthouse, WAVE) with manual specialist testing — keyboard navigation, screen reader validation (JAWS, NVDA, VoiceOver, TalkBack), and mobile accessibility testing on iOS and Android. Our accessibility testing is structured against the NZ Government Web Accessibility Standard 1.1 for government programmes, and WCAG 2.1 AA for private sector clients. We deliver clear, actionable reports with POUR criterion mapping, severity ratings, and developer remediation guidance.

What We Test
Independent QA across all components — end to end.
WCAG 2.1/2.2 AA Testing
Manual and automated testing against WCAG 2.1 and 2.2 Level AA success criteria — the standard required by the NZ Government Web Accessibility Standard 1.1.
Keyboard & Screen Reader Testing
Full keyboard navigation testing plus manual screen reader validation using JAWS and NVDA (Windows) and VoiceOver (Mac/iOS) — the screen readers most commonly used by disabled users in New Zealand.
Mobile Accessibility Testing
Accessibility validation on iOS (VoiceOver) and Android (TalkBack) — gestures, touch targets, dynamic content, and orientation change behaviour tested against mobile-specific WCAG criteria.
Automated Accessibility Scanning
Axe, Lighthouse, and WAVE integration into your CI/CD pipeline. Automated scanning catches 30-40% of WCAG issues — we add the manual specialist testing for the rest.
NZ Government Web Accessibility Standard
Testing and reporting structured against the NZ Government Web Usability Standard and Web Accessibility Standard 1.1 — mandatory for NZ government agencies and recommended for all public-sector digital products.
Audit & Remediation Reporting
Structured WCAG audit reports with POUR criterion mapping, severity ratings (critical/serious/moderate/minor), and developer remediation guidance. Ready for stakeholder review and legal due diligence.
We Don’t Sell Tools. We Don’t Have Delivery Targets.
Resync has no financial relationship with any tool vendor. We recommend whichever approach best fits your technology landscape and programme context — full stop.
Why Resync for Accessibility?
Common Questions about Accessibility Testing
Everything you need to know before engaging Resync.
Is WCAG 2.1 or 2.2 required for NZ government?
The NZ Government Web Accessibility Standard 1.1 is based on WCAG 2.1 Level AA. While WCAG 2.2 has been published, the NZ standard mandates 2.1 AA as its baseline. Resync tests against 2.1 AA as the required standard and flags 2.2 enhancements as advisory.
Can automated tools replace manual accessibility testing?
No. Automated scanners (axe, Lighthouse, WAVE) reliably identify approximately 30-40% of WCAG 2.1 AA issues — primarily structural failures like missing alt text, insufficient colour contrast, and missing form labels. The remaining issues — keyboard navigation, screen reader UX, focus management, and dynamic content behaviour — require manual specialist testing.
What screen readers does Resync test with?
JAWS (Windows, most common in enterprise and government), NVDA (Windows, open source), VoiceOver on macOS and iOS, and TalkBack on Android. Browser and screen reader combinations tested reflect those most commonly used by disabled users in New Zealand.
How long does an accessibility audit take?
A structured WCAG 2.1 AA audit of a web application typically takes 3-10 days depending on scope — number of templates, interactive components, and dynamic states to be tested. Resync provides a comprehensive report with criterion-level findings, severity ratings, and developer guidance.
Ready to Protect Your Accessibility Programme?
Talk to a Resync specialist. We’ll give you an honest assessment of where your quality risks sit — no obligation, no sales pitch.
