Accessibility testing services Australia — WCAG 2.2 audit KiwiQA
Accessibility Testing · Australia & USA

Accessibility Testing
and WCAG 2.2 Audits.

KiwiQA's accessibility testing practice combines automated scanning with expert manual testing by users with disabilities — the only approach that achieves genuine WCAG 2.2 conformance for Australian government and enterprise.

Accessibility Coverage
WCAG 2.2
AA conformance standard
DDA
Compliant audit reports
5+
Screen readers tested
100%
Keyboard navigation
4.5:1
Colour contrast AA ratio
78
WCAG success criteria
What We Test
Manual Expert TestingWCAG 2.2 complete
Automated Scanningaxe-core + WAVE
Screen Reader TestingJAWS/NVDA/VoiceOver
Government Procurement ReadyACR/VPAT 2.5
The Problem

Accessibility failures are legal
and commercial risk.

The Australian Disability Discrimination Act makes inaccessible digital products a legal liability. Australian government agencies require WCAG 2.1 AA minimum for procurement. US Section 508 and ADA Title III expose US-market products to litigation.

Why Accessibility Testing Fails Without Experts
Automated tools find only 30% of issues
Scanners like axe and WAVE reliably identify colour contrast and missing alt text — but they cannot evaluate screen reader announcement quality, focus order logic or cognitive load. Manual expert testing finds the remaining 70%.
Government procurement requires documented WCAG conformance
A scan report is not an Accessibility Conformance Report. Federal and state agencies require a VPAT 2.5 or ACR documenting conformance against each success criterion — a document only a human audit can produce.
Screen reader testing requires experts who use them daily
Meaningful screen reader testing requires testers who navigate the web with JAWS, NVDA or VoiceOver as their primary interface. Engineers running scripts against a screen reader produce false confidence, not real coverage.
Colour contrast and focus failures are the most expensive to retrofit
Colour and focus issues embedded across a design system affect hundreds of components. Catching them at design review costs a fraction of fixing them post-launch — especially when a government audit flags them.
Accessibility overlays do not achieve conformance
Products like AudioEye and UserWay add a JavaScript layer over an inaccessible site. They do not fix the underlying DOM — meaning the site still fails a real audit and users with assistive technology still encounter barriers. Regulators are increasingly aware of this.
Australian Regulatory Landscape
Disability Discrimination Act 1992 (DDA)
Legal liability for inaccessible digital services
Australian Government Digital Service Standard
WCAG 2.1 AA required for federal procurement
AGIMO Web Accessibility Guidance
Applies to all Australian Government websites
NDIS Digital Services
Accessibility required for NDIS-funded services
US Market Exposure
ADA Title III
Federal courts have ruled that websites are 'places of public accommodation' — more than 4,600 ADA web accessibility lawsuits were filed in the US in 2023 alone.
Section 508
Required for all US federal agencies and their technology suppliers — including Australian SaaS vendors selling into the US federal market.
DOJ Web Guidance (2024)
The Department of Justice published binding web accessibility guidance in April 2024, explicitly citing WCAG 2.1 AA as the compliance standard.
Accessibility Services

Every accessibility discipline.
One integrated practice.

From full WCAG 2.2 conformance audits to CI/CD regression automation — KiwiQA covers the complete accessibility testing lifecycle.

01
WCAG 2.2 Conformance Audit
Full manual and automated audit across all 78 WCAG 2.2 success criteria — Levels A, AA and AAA where required. Produces a documented Accessibility Conformance Report (ACR/VPAT) suitable for government procurement and legal review.
78 criteria covered
02
Screen Reader Testing
Expert testing with JAWS, NVDA, VoiceOver (macOS/iOS) and TalkBack (Android) conducted by testers who use screen readers as their primary interface — not engineers running scripts against a checklist.
JAWS · NVDA · VoiceOver · TalkBack
03
Keyboard Navigation Testing
Full tab order validation, focus indicator visibility, keyboard trap detection and shortcut key conflict analysis. Keyboard accessibility is the second most common failure category in Australian government audits.
Zero keyboard traps
04
Colour Contrast & Visual Design
Automated and manual colour contrast analysis against WCAG 2.2 SC 1.4.3 (minimum) and SC 1.4.6 (enhanced), plus non-text contrast, focus indicator contrast and reflow at 400% zoom.
4.5:1 AA · 7:1 AAA
05
Government Procurement Statement
Production of a formal Accessibility Conformance Statement and VPAT aligned with the Australian Government's Digital Service Standard (DSS) and AGIMO guidance — required for federal and state procurement.
Procurement-ready ACR
06
Accessibility Regression in CI/CD
axe-core and WAVE integration into your Jenkins, Azure DevOps or GitHub Actions pipeline — catching new accessibility regressions on every pull request, before they reach production.
axe-core · WAVE · CI/CD
Our Approach

How KiwiQA delivers
genuine WCAG conformance.

01
Scope & Baseline Assessment
We audit your site's technology stack, component library and user journeys to define the representative page sample and testing scope. We identify the highest-risk areas — forms, tables, dynamic content, modal dialogs — and prioritise them for manual testing.
02
Automated Scanning Baseline
We run axe-core, WAVE and Lighthouse across the full site to establish a baseline of automatically detectable issues. This surfaces colour contrast failures, missing ARIA labels and structural issues before manual testing begins.
03
Expert Manual Audit
Certified accessibility specialists audit each page against all 78 WCAG 2.2 success criteria. Focus order, reading order, announcement quality, cognitive load and context changes are evaluated — none of which automated tools can detect.
04
Screen Reader Testing
Testers using JAWS (Windows), NVDA (Windows), VoiceOver (macOS and iOS) and TalkBack (Android) navigate every key user journey. We document announcement failures, navigation barriers and AT-specific rendering bugs.
05
Findings Report & ACR Production
We produce a prioritised findings report with WCAG criterion reference, severity rating, remediation guidance and developer-ready fix instructions. We then produce the Accessibility Conformance Report (VPAT 2.5) for procurement submission.
06
Remediation Verification & Retest
KiwiQA retests all fixed issues and updates the ACR. For clients embedding accessibility in CI/CD, we configure axe-core pipeline integration and set automated quality gates to prevent regression.
Tools & Standards We Apply
axe-core
WAVE
Lighthouse
JAWS
NVDA
VoiceOver
TalkBack
VPAT 2.5
WCAG 2.2
AGIMO Guidance
Section 508
ADA Title III
CriterionStandard
Colour Contrast (text)4.5:1 AA · 7:1 AAA
Colour Contrast (UI)3:1 WCAG 2.2 SC 1.4.11
Touch Target Size24×24px SC 2.5.8
Focus IndicatorWCAG 2.2 SC 2.4.11/12
Success Criteria Coverage78 (all AA + AAA where required)
VPAT FormatVPAT 2.5 WCAG Edition
Automation Coverageaxe-core + WAVE + Lighthouse
Screen ReadersJAWS · NVDA · VoiceOver · TalkBack
Client Results

What government and enterprise
clients say about KiwiQA.

Case Study
"We had an AudioEye overlay on our government portal for two years and still failed the accessibility audit when we went to tender. KiwiQA ran a manual audit with real screen reader users and found 47 issues the automated tool had never flagged. We achieved WCAG 2.1 AA within 8 weeks."
🏛
Digital Accessibility Lead
Australian Federal Government Agency
47
Issues found (automated missed all)
8 wks
To WCAG 2.1 AA conformance
100%
ACR accepted at procurement

It was a pleasure to work with Niranjan and his team of dedicated and comprehensive testers. A great experience full of support and passion to deliver a great service.

R
Rebecca VanZutphen
Project Lead, UK

Niranjan & the KiwiQA team have been excellent. They have demonstrated great ownership, hustle and maintained a high quality bar akin to top tech companies like Flipkart.

N
Nikhil Goenka
Director, Technology

KiwiQA provide high quality support at a very reasonable price. Their penetration testing on our platform was very thorough and provided us confidence in the cyber security.

F
Founder, AirSmile
Avenue Dental Kawana, AU
Accessibility Insights

Expert guides on
digital accessibility.

WCAG 2.1 Accessibility Testing: Australian Business
Accessibility
WCAG 2.1 Accessibility Testing: Australian Business
Accessibility is both a legal obligation and a commercial opportunity. A practical guide to WCAG 2.1 compliance testing for Australian businesses in 2025.
12 Dec 20249 min read →
GenAI Application Testing: Enterprise Validation
AI Testing
GenAI Application Testing: Enterprise Validation
Enterprise GenAI fails differently to traditional software. Covers hallucination testing, OWASP LLM security and EU AI Act compliance for LLM integrations.
22 Jul 202612 min read →
Cloud Migration Testing: AWS, Azure & GCP Strategy
Enterprise Testing
Cloud Migration Testing: AWS, Azure & GCP Strategy
Migrations succeed or fail on testing quality. Full AWS, Azure and GCP testing framework for Australian enterprises migrating to the cloud in 2026.
21 Jul 202611 min read →
SAP S/4HANA Migration Testing: AU Playbook
Enterprise Testing
SAP S/4HANA Migration Testing: AU Playbook
SAP ECC ends 2027. Complete S/4HANA migration testing programme for Australian enterprises — what to test, how to automate and how to manage cutover.
20 Jul 202613 min read →
FAQ

Frequently asked questions

Everything you need to know — answered.

What is WCAG 2.2 and how is it different from WCAG 2.1?
+

WCAG 2.2, published by the W3C in October 2023, adds nine new success criteria to WCAG 2.1. The most impactful additions for Australian organisations are Focus Appearance (2.4.11/2.4.12), which tightens focus indicator visibility requirements, and Target Size Minimum (2.5.8), which mandates 24×24 CSS pixel minimum touch targets. Australian government guidance references WCAG 2.1 AA, but auditors increasingly flag WCAG 2.2 gaps as future risk.

Does the Australian DDA require WCAG compliance for websites?
+

The Disability Discrimination Act 1992 does not name WCAG explicitly, but the Australian Human Rights Commission (AHRC) has made clear that inaccessible websites can constitute unlawful discrimination. Federal and state government procurement mandates require WCAG 2.1 AA as a minimum. Private organisations — particularly e-commerce, finance and healthcare — face complaint risk if their digital services exclude users with disabilities.

How long does a WCAG 2.2 accessibility audit take?
+

A typical WCAG 2.2 AA conformance audit of a medium-complexity website (20–50 representative pages/components) takes 10–15 business days including manual screen reader testing, automated scanning, issue documentation and ACR production. Larger enterprise applications or complex single-page apps may require 3–6 weeks. KiwiQA provides a scoped estimate within 24 hours of receiving a site brief.

Can automated tools like axe fully test accessibility?
+

No. Automated tools such as axe-core and WAVE reliably detect only 20–35% of WCAG issues. Criteria such as focus order logic, screen reader announcement quality, meaningful image alt text, form instruction clarity and cognitive load cannot be evaluated by automated scanning alone. KiwiQA's audits combine automated scanning with expert manual testing — including real screen reader users — to achieve genuine conformance, not just a passing tool score.

What is Section 508 and does it apply to Australian companies?
+

Section 508 of the US Rehabilitation Act requires US federal agencies and their suppliers to ensure ICT products are accessible. Australian companies that sell software or services to US federal agencies — including SaaS vendors, IT services firms and defence contractors — must comply. Section 508 references WCAG 2.0 Level AA as its technical standard, meaning WCAG 2.1/2.2 AA conformance provides strong coverage. KiwiQA produces Section 508 VPATs alongside Australian ACRs for clients in both markets.

What is an accessibility conformance report (ACR/VPAT)?
+

An Accessibility Conformance Report (ACR), produced from the Voluntary Product Accessibility Template (VPAT), is a structured document declaring how a product meets each WCAG success criterion. ACRs are required by US federal procurement (Section 508) and increasingly by Australian government agencies under the Digital Service Standard. KiwiQA produces VPAT 2.5 (WCAG 2.1/2.2) and ITI-format ACRs suitable for both AU and US procurement submissions.

WCAG 2.2 Accessibility Testing

Need a WCAG 2.2 audit?
Get a scoped accessibility assessment.

Manual expert testing, screen reader coverage, government-ready ACR/VPAT production — KiwiQA delivers genuine WCAG conformance, not just a passing axe score. Available across Australia and the US.

78
WCAG success criteria
covered in every audit
DDA · WCAG 2.2 · Section 508 · VPAT 2.5