[{"id":14066,"date":"2026-07-17T11:14:13","date_gmt":"2026-07-17T15:14:13","guid":{"rendered":"https:\/\/www.grackledocs.com\/?p=14066"},"modified":"2026-07-17T11:14:13","modified_gmt":"2026-07-17T15:14:13","slug":"new-zealands-transition-to-the-digital-accessibility-standard","status":"publish","type":"post","link":"https:\/\/www.grackledocs.com\/en\/new-zealands-transition-to-the-digital-accessibility-standard\/","title":{"rendered":"Navigating New Zealand’s Transition to the Digital Accessibility Standard (DAS)"},"content":{"rendered":"

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<\/a> (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)<\/a> that will extend accessibility requirements to mobile apps, emails, and downloadable documents as their own category, not just PDFs delivered through a web page.<\/p>\n

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.<\/p>\n

The New Frontier of Digital Inclusion in Aotearoa<\/h3>\n

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.<\/p>\n

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.<\/p>\n

True digital accessibility<\/a> in Aotearoa means ensuring no person is left behind, whether they are navigating a desktop portal or reading a consultation document on a smartphone.<\/p>\n

Shattering the “Website-Only” Illusion<\/h3>\n

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.<\/p>\n

The Mobile Exploded View<\/h4>\n

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.<\/p>\n

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.<\/p>\n

Public sector service apps, internal enterprise tools, and customer-facing mobile platforms must be reviewed through native testing methodologies. Accessibility<\/a> must be engineered into the app architecture, not patched afterward.<\/p>\n

The Document Trap<\/h4>\n

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.<\/p>\n

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.<\/p>\n

Leaving these formats unoptimised creates immediate operational friction today, and will create greater compliance exposure as DAS takes effect.<\/p>\n

What DAS Will Require – and What WAS 1.2 Requires Today<\/h3>\n

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.<\/p>\n

Scope Expansion Across Asset Types<\/h4>\n

DAS is expected to target multiple categories of digital assets:<\/p>\n