Website accessibility in New Zealand
Roughly a quarter of New Zealanders are disabled. Government agencies are required to meet a specific accessibility standard, private businesses are covered by the Human Rights Act more generally, and the common failures are cheap to fix if you catch them during design rather than after launch.
Accessibility is usually framed as a compliance obligation, which is the least persuasive reason to do it. The better arguments are that Statistics New Zealand's Disability Survey has found roughly a quarter of the population is disabled, that accessible sites are measurably easier for everyone to use, and that the same structural clarity which helps a screen reader also helps a search engine and an AI system extract your content.
WCAG is the standard everything else points at
The Web Content Accessibility Guidelines, published by the World Wide Web Consortium, are the international reference. WCAG 2.2 became a W3C Recommendation in October 2023 and is the current version. It defines three conformance levels: A is the minimum, AA is the level almost every regulation and policy in the world adopts, and AAA is aspirational and not expected across a whole site. When a New Zealand policy or contract refers to accessibility requirements, it is nearly always pointing at WCAG Level AA.
Who is actually required to comply in New Zealand
The New Zealand Government Web Accessibility Standard 1.2 took effect on 17 March 2025 and mandates conformance with WCAG 2.2 Level AA, which puts New Zealand ahead of most jurisdictions, since many still reference WCAG 2.1. A companion Web Usability Standard 1.4 took effect the same day. The scope is narrower than most people assume: the mandate covers Public Service departments, New Zealand Police, the New Zealand Defence Force, the Parliamentary Counsel Office, and the New Zealand Security Intelligence Service. Crown entities, state-owned enterprises, councils, schools, and universities are not mandated by it, though many adopt it voluntarily or are bound through procurement.
Private businesses are not bound by that standard at all. The often-cited alternative is the Human Rights Act 1993, section 44 of which concerns the provision of goods and services to the public, read together with the prohibition on disability discrimination. It should be described honestly: no New Zealand court has ruled on whether a private website falls within section 44, so this is untested exposure rather than settled law. The Accessibility for New Zealanders Bill, which would have created a broader framework, was discharged on 14 August 2024. The most concrete commercial reason for a private business to meet WCAG 2.2 AA is that it has become the de facto government procurement standard, so any supplier bidding for public sector work is contractually bound to it regardless of what the Human Rights Act does or does not require.
The failures that appear on almost every site
| Failure | Who it affects | Difficulty to fix |
|---|---|---|
| Insufficient colour contrast on text | Low vision, older users, anyone outdoors | Low |
| Images with missing or meaningless alt text | Screen reader users | Low |
| Form inputs without associated labels | Screen reader users, voice control users | Low |
| Links labelled only "click here" or "read more" | Screen reader users navigating by link | Low |
| No visible keyboard focus indicator | Keyboard-only users, motor impairment | Low |
| Content only reachable by mouse or hover | Keyboard and touch users | Medium |
| Video without captions | Deaf and hard of hearing users | Medium |
| Motion and parallax with no reduced-motion option | Vestibular disorders, migraine | Low |
| Heading levels skipped or used for styling | Screen reader navigation | Low |
| Text in images instead of real text | Screen readers, translation, search engines | Medium |
The pattern in that table is worth noticing: the overwhelming majority of common failures are cheap to fix and cost almost nothing to prevent if they are considered while designing. They become expensive only when a site is retrofitted after launch, which is the usual sequence and the reason accessibility gets a reputation for being costly.
The four principles behind the standard
- Perceivable. Information and interface components must be presentable in ways people can perceive, which covers text alternatives for images, captions for media, and sufficient contrast.
- Operable. Interface components and navigation must be operable, which means everything works by keyboard, people get enough time, and nothing flashes in a way that can trigger seizures.
- Understandable. Content and operation must be understandable: readable language, predictable behaviour, and errors explained in a way that helps someone recover.
- Robust. Content must be robust enough to work reliably with assistive technologies, which in practice means using correct semantic HTML rather than reinventing controls out of unlabelled elements.
How to test without specialist tools
Automated tools catch perhaps a third of real accessibility issues, so they are a starting point rather than an answer. Run one anyway, because the issues they catch are the cheap ones. Then do the manual checks, which take about twenty minutes and find the problems automation misses.
- Run an automated checker such as WAVE or the Lighthouse accessibility audit in Chrome. Fix everything it reports.
- Unplug your mouse. Navigate the whole site with Tab, Shift-Tab, Enter, and Space. If you cannot reach something, or you cannot see where you are, that is a failure.
- Zoom the browser to 200 percent. Content should reflow and remain readable without horizontal scrolling.
- Turn on your operating system's reduce-motion setting and reload. Animation should reduce or stop while the site still works.
- Turn on a screen reader for five minutes. VoiceOver on Mac and iPhone, Narrator on Windows, TalkBack on Android. It is uncomfortable the first time and extremely instructive.
- Check every form: submit it empty and see whether the errors explain what to do, and whether they are announced rather than only shown in red.
Common questions
For a specific set of government bodies, yes. The Web Accessibility Standard 1.2, effective 17 March 2025, requires WCAG 2.2 Level AA and applies to Public Service departments, New Zealand Police, the Defence Force, the Parliamentary Counsel Office, and the Security Intelligence Service. Crown entities, councils, schools, and universities are not mandated by it. Private businesses are not covered at all, and whether the Human Rights Act 1993 extends to private websites has not been tested in a New Zealand court.
Sources
Every factual claim on this page traces to one of the following. If you find something here that is out of date, we would genuinely like to know.
- Web Content Accessibility Guidelines (WCAG) 2.2. World Wide Web Consortium.
- Web Accessibility Standard 1.2. digital.govt.nz, Department of Internal Affairs, Effective 17 March 2025.
- Human Rights Act 1993. New Zealand Legislation.
- Disability Survey. Stats NZ.
- WAVE Web Accessibility Evaluation Tool. WebAIM, Utah State University.
Want this handled rather than explained?
AntCrow builds websites with all of the above built in. Tell us what you are trying to achieve and we will tell you honestly what is worth doing.
Start a project