If you think your organisation is digitally accessible just because your website passes a standard WCAG browser scan, you are missing half the picture. Right now, mandated New Zealand government agencies must meet the Web Accessibility Standard 1.2 (WCAG 2.2 at Level AA) for every web page, including Word and PDF documents published as web content. That bar is about to move further: the Government Chief Digital Officer is developing a Digital Accessibility Standard (DAS) that will extend accessibility requirements to mobile apps, emails, and downloadable documents as their own category, not just PDFs delivered through a web page.
New Zealand has long demonstrated a commitment to accessibility and public sector inclusion. However, for years, digital compliance was largely treated as a website-only checklist focused on browser-based WCAG conformance. The Digital Accessibility Standard marks a coming paradigm shift. It recognises that the modern citizen’s digital life spans mobile apps, dynamic portals, downloadable documents, and service platforms. Compliance is not confined to an IT web team. It is an omni-channel organisational responsibility, and one New Zealand is actively building toward.
The New Frontier of Digital Inclusion in Aotearoa
New Zealand’s accessibility requirements are in the middle of a structural evolution. The current mandated standard (Web Accessibility Standard 1.2) already requires WCAG 2.2 Level AA conformance, a step up from the WCAG 2.1 baseline used before March 2025. Historically, though, accessibility efforts centred on web pages tested through browser extensions and automated WCAG scans, and the next phase of that evolution, the Digital Accessibility Standard, is being built specifically to close the gaps browser-only testing leaves behind.
People interact with government and enterprise systems across multiple touchpoints. They download policy documents on mobile devices, complete forms within SaaS platforms, and use native mobile applications to access essential services. The DAS framework, once finalized, will acknowledge this reality directly, expanding the compliance mandate to encompass the entire digital ecosystem.
True digital accessibility in Aotearoa means ensuring no person is left behind, whether they are navigating a desktop portal or reading a consultation document on a smartphone.
Shattering the “Website-Only” Illusion
The most significant impact of this shift, both what’s already in effect and what’s coming, is the dismantling of the browser-only mindset. organisations that equate accessibility with passing a web scan risk overlooking substantial gaps, today and as the standard expands.
The Mobile Exploded View
Native mobile applications operate differently from web pages. iOS and Android platforms rely on their own accessibility APIs, including Apple’s VoiceOver and Android’s TalkBack. These systems interpret interface components through native code structures, not HTML tags.
Testing a mobile app with a browser-based WCAG scanner does not reveal whether focus order works correctly within a native interface. It does not confirm that interactive elements are labeled properly for screen reader users. As DAS brings native mobile apps formally into scope, organisations will need to evaluate against native accessibility frameworks, not just web standards, and getting ahead of that now is far cheaper than remediating later.
Public sector service apps, internal enterprise tools, and customer-facing mobile platforms must be reviewed through native testing methodologies. Accessibility must be engineered into the app architecture, not patched afterward.
The Document Trap
PDFs and Word documents represent one of the largest hidden accessibility barriers in New Zealand’s public sector. Consultation papers, policy updates, financial disclosures, and official announcements are frequently distributed as downloadable files. These documents often contain improper tagging, inconsistent heading structures, poor color contrast, and unreadable tables.
An accessible website does not compensate for an inaccessible PDF. If a person downloads a document and cannot navigate it using assistive technology, the digital experience fails. Under Web Accessibility Standard 1.2, Word and PDF documents delivered as web content are already in scope, and DAS is expected to strengthen and broaden that requirement further. Accessible PDF and Word documents in New Zealand must be created correctly at the source, with proper structure and reading order embedded during authoring.
Leaving these formats unoptimised creates immediate operational friction today, and will create greater compliance exposure as DAS takes effect.
What DAS Will Require – and What WAS 1.2 Requires Today
Today, mandated agencies must meet Web Accessibility Standard 1.2: WCAG 2.2 Level AA across every web page, including Word and PDF files delivered as web content. The Digital Accessibility Standard, once finalised, is expected to broaden that further by pulling native mobile apps, emails, and standalone documents into one unified standard. Organisations that start rethinking their digital asset inventory now, ahead of DAS taking effect, will have far less remediation to do later.
Scope Expansion Across Asset Types
DAS is expected to target multiple categories of digital assets:
- Native mobile applications
- Dynamic portals and dashboards
- Software-as-a-service platforms
- Downloadable PDFs and Word documents
- Internal documentation systems
Beyond WCAG browser accessibility, the coming standard acknowledges that accessibility must follow the user across devices and formats. Government digital inclusion standards in Aotearoa are moving toward this holistic view.
From Checklist to Strategy
DAS is designed to push organisations away from reactive patching, such as deploying superficial overlays or relying solely on automated scans. Instead, it emphasises accessible-by-design engineering. Accessibility must be embedded into product development, content creation, and procurement processes from the very beginning, and organisations that build this discipline now, under WAS 1.2, will be well positioned when DAS arrives.
This transition requires moving from technical fixes to strategic governance. Accessibility is a cross-functional responsibility, not an isolated remediation project.
Native Testing vs Browser Testing
One of the most critical shifts involves testing methodology. Standard web-crawling tools cannot evaluate native mobile applications or standalone PDFs effectively. Browser scanners detect HTML-based issues but do not assess mobile gesture navigation, native control labeling, or document tag trees.
Internal QA teams must expand their toolkit. Mobile app testing must involve native screen readers. Document testing must include structural validation and logical reading order analysis. organisations that rely exclusively on browser testing risk underestimating their compliance exposure, both under current WAS 1.2 obligations and the broader scope DAS will bring.
Practical Steps for Kiwi organisations to Adapt
The transition to the Digital Accessibility Standard requires structured action, starting now, ahead of the standard’s finalisation. The following steps provide a pragmatic roadmap for adaptation.
Audit Beyond the URL
Begin by mapping your entire digital ecosystem. Identify every public or internal asset:
- Corporate websites
- Native mobile applications
- Third-party SaaS tools
- Downloadable PDFs and Word templates
- Internal employee portals
This baseline audit must extend beyond the homepage. It should reveal where accessibility gaps exist across formats and platforms against today’s WAS 1.2 requirements and DAS’s anticipated scope. Only then can remediation efforts be prioritised effectively.
Upskill Content Creators at the Source
Accessibility cannot remain the sole responsibility of developers. HR teams create onboarding documents. Communications teams publish announcements. Policy teams draft consultation papers. Each of these groups must understand how to create accessible Word and PDF documents from the outset.
Embedding accessibility into authoring environments reduces downstream remediation. Tools such as Grackle Workspace for Google environments and Grackle Office for Microsoft 365 support accessible document creation directly within familiar workflows. By validating structure, headings, and alternative text during drafting, organisations prevent inaccessible files from entering circulation.
Align Procurement With DAS Principles
Procurement policies should start evolving alongside regulatory expectations, even ahead of DAS’s formal arrival. When selecting third-party apps or digital tools, organisations should require explicit alignment with DAS’s anticipated principles. Vendor documentation should demonstrate native accessibility testing, compliance roadmaps, and transparent issue tracking.
Procurement alignment ensures that new systems do not introduce hidden accessibility liabilities. It transforms compliance from reactive correction to preventative governance.
Embracing the Future of Accessibility
New Zealand’s move from Web Accessibility Standard 1.2 toward the forthcoming Digital Accessibility Standard represents an opportunity to build a more inclusive, frictionless digital ecosystem. Organisations that meet WCAG 2.2 today and start building mobile, document, and email accessibility into their workflows now, ahead of DAS, will lead tomorrow’s digital economy.
Accessibility improves user experience for everyone. Structured documents enhance readability. Clear mobile navigation reduces friction. Inclusive design fosters trust and engagement. By preparing for the DAS framework now, Kiwi organisations strengthen both compliance posture and public confidence.
The future of digital inclusion in Aotearoa depends on proactive adaptation. Compliance already goes beyond a website audit under WAS 1.2, and it will go further still once DAS takes effect.
Organisations that embrace this transition will set the benchmark for inclusive service delivery.
Book a consultation with our digital inclusion specialists to audit your mobile applications against native iOS and Android accessibility frameworks. Ensure your organisation’s digital ecosystem aligns with both today’s Web Accessibility Standard 1.2 and New Zealand’s evolving Digital Accessibility Standard.
