1. Home
  2. Accessibility testing
  3. Australia & New Zealand

StrongAccess · Australia · New Zealand

Accessibility testing for Australia and New Zealand, to WCAG 2.2 AA

Australian and New Zealand guidance now set WCAG 2.2 Level AA as the benchmark. StrongAccess provides enterprise-grade audits, remediation support and continuous monitoring for government, financial services, healthcare and regulated industries.

CommitBuildAccessibilitygateWCAG 2.2 AAReleaseNEW IN WCAG 2.2 · RELEASE 4.122.4.11Focus not obscured (minimum)2.5.7Dragging movements2.5.8Target size (minimum)3.3.8Accessible authentication (minimum)
Standard
WCAG 2.2 Level AA
Australia
DDA 1992, AHRC guidance, AS EN 301 549
New Zealand
Web Accessibility Standard 1.2
Integration
CI/CD, release gates, issue tracker sync

Why act now

Four drivers making accessibility a priority

Compliance

Clear legal and policy expectations

The DDA applies to digital goods and services, and both Australian and NZ guidance now set WCAG 2.2 AA as the benchmark.

Customer experience

Accessible journeys convert better

Forms, payments and service requests that work for everyone mean fewer abandoned transactions and better search visibility.

Procurement and risk

Faster tenders, less exposure

Accessibility evidence speeds up government and enterprise procurement and reduces complaint and legal risk.

Reputation and inclusion

Trust and social responsibility

Showing leadership in inclusion strengthens your brand with customers, staff and regulators.

ANZ policy reality

What applies in Australia and New Zealand

A summary, not legal advice. Your obligations depend on your sector and customers.

Australia and New Zealand accessibility policy overview
DimensionAustraliaNew Zealand
Legal frameworkDisability Discrimination Act 1992Human Rights Act 1993
Technical benchmarkWCAG 2.2 Level AA, per Australian Human Rights Commission guidance (April 2025)WCAG 2.2 Level AA, required by the Web Accessibility Standard 1.2 from 17 March 2025
Government policyDigital Experience Policy (from 1 January 2025) for Australian Government agenciesWeb Accessibility Standard 1.2 for mandated public service agencies and Crown entities
ProcurementAS EN 301 549 for ICT procurementAccessibility built into government web standards
Additional requirementsAHRC guidance covers apps, SaaS, CAPTCHAs, biometrics and AI toolsLive captions and audio description required for high-stakes content
Who's affectedGovernment, and private-sector organisations providing goods and servicesPublic service departments, Crown entities and their suppliers

Sources: Australian Human Rights Commission; NZ Web Accessibility Standard 1.2.

Where organisations struggle

Six common pain points

Siloed ownership

Design, development, QA and content teams aren't aligned on who owns which WCAG requirements.

Automation-only testing

Scanners miss complex and assistive technology issues and create false confidence.

WCAG 2.2 readiness

The new criteria aren't yet built into the SDLC or design system.

Mobile and apps

Screen reader, keyboard and gesture gaps in native apps.

Documents and PDFs

Large backlogs of untested documents create ongoing compliance risk.

Governance and evidence

No clear reporting, accessibility statement or procurement pack.

Built into how you deliver

Accessibility in your SDLC, not beside it

Release-aligned testing means accessibility is checked continuously rather than discovered in a yearly audit.

  • CI/CD integrationAutomated accessibility checks in your build pipeline.
  • Release gatesClear pass criteria before a release goes live.
  • Issue tracker syncFindings land in Jira or your tracker with fix guidance.
  • Design system alignmentAccessible patterns built into your components.
  • Developer enablementCode samples, pattern libraries and hands-on training.
  • Audit trailA record of testing, fixes and decisions for regulators and procurement.

How we engage

Assess, fix, sustain

  1. Stage 01 · Assess

    Baseline your digital estate

    2–4 weeks

    • Baseline audit of your digital estate
    • Critical journey analysis
    • Assistive technology testing (NVDA, JAWS, VoiceOver, TalkBack)
    • Prioritised issue backlog and risk assessment
  2. Stage 02 · Fix

    Remediate and enable

    4–12 weeks

    • Remediation sprints with code samples
    • Design and content updates
    • Developer enablement and training
    • Re-testing and validation
  3. Stage 03 · Sustain

    Keep it compliant

    12 months+

    • Continuous monitoring
    • Release-gate checks
    • Quarterly re-tests
    • Governance reporting and dashboards

Packages

Three engagement models

All packages include WCAG 2.2 AA testing.

Package 01

Rapid Pilot

2–4 weeks

Prove value quickly on your most important journeys or flagship channel.

  • 1–5 critical journeys tested (web or mobile)
  • Assistive technology testing
  • Arabic / RTL validation where relevant
  • Risk-ranked findings and issue backlog
  • Executive readout and remediation roadmap

Best for Fast proof, a board-grade baseline and early procurement evidence.

Package 02

Accessibility Program

3–6 months

Audit, remediation and sign-off across your main digital channels.

  • Full WCAG audit: web, mobile and documents
  • Remediation advisory and pair-fix sessions
  • Re-test and confirmation of fixed journeys
  • Accessibility statement
  • Role-based team training

Best for Organisations preparing for a procurement or audit cycle.

Package 03

Managed Assurance

12 months+

Year-round accessibility assurance across your digital estate.

  • Continuous monitoring and release-gate testing
  • Quarterly governance reviews and executive dashboards
  • Standing remediation advisory
  • Procurement evidence pack, kept current
  • Annual training refresh

Best for Public sector and regulated enterprises running accessibility as a programme.

Every package is scoped to your channels, languages and regulatory context. You'll receive a fixed quote after a short scoping session. Each package is designed to lead into the next.

12-month roadmap

From baseline to sustained compliance

12-month StrongAccess roadmap
QuarterFocusWhat happens
Q1 · Months 1–3Baseline and mobiliseStakeholder kickoff, baseline audit of flagship channels, risk register, quick wins
Q2 · Months 4–6Remediate and enableFix patterns in sprints, re-test journeys, accessibility statement, developer and design training
Q3 · Months 7–9Extend and operationaliseMobile apps, PDFs and media, release-aligned testing, CI/CD checks, design system patterns
Q4 · Months 10–12Assure and evidenceExecutive scorecard, procurement evidence pack, quarterly business review, Year 2 roadmap

Next steps

Three ways to begin

30–45 minutes

Executive accessibility briefing

A tailored session on your digital estate, risks and timelines, with prioritised recommendations.

Schedule a briefing

Fixed fee · kickoff in 2 weeks

Rapid Pilot

3–5 critical journeys tested with assistive technology, a prioritised backlog and a remediation roadmap.

Start a pilot

Cross-functional

Stakeholder alignment workshop

Align design, development, QA, content and compliance on roles, responsibilities and workflow.

Book a workshop

FAQ

Australia and NZ accessibility questions

Is website accessibility a legal requirement in Australia?

The Disability Discrimination Act 1992 makes disability discrimination in providing goods and services unlawful, and that includes digital services. The Australian Human Rights Commission's 2025 guidance treats WCAG 2.2 Level AA as the minimum benchmark. We're not lawyers, but an audit shows where you stand and what to fix.

What does the NZ Web Accessibility Standard 1.2 require?

Since 17 March 2025, mandated New Zealand government organisations must meet WCAG 2.2 Level AA for their websites. The standard also strengthens requirements for live captions and audio description on high-stakes content.

We sell to government. What evidence will procurement ask for?

Typically an accessibility statement, a recent audit against WCAG 2.2 AA and, for ICT products, conformance with AS EN 301 549. Our packages produce these as standard deliverables.

Can you work with our development pipeline?

Yes. We integrate with CI/CD pipelines, set up release gates and sync findings to your issue tracker, so accessibility is checked with every release rather than once a year.

How do you work across time zones from the UAE?

Our working hours overlap with Australian and New Zealand mornings, and briefings, readouts and governance meetings are scheduled to suit you. Testing itself doesn't depend on time zones.

Get to WCAG 2.2 AA, and stay there.

Tell us which services and journeys matter most. We'll recommend an entry point and give you a fixed quote.

Book an accessibility briefing