Advertisement

Web accessibility is becoming a business requirement in New Zealand, not a nice to have

Every few years a piece of web craft that lived on the margins moves to the centre. Mobile-friendly design did it a decade ago. Page speed did it more recently. The next one is already here, and most New Zealand business owners have not noticed it yet. Web accessibility, the practice of building sites that people with impaired vision, hearing, movement or attention can actually use, has stopped being a charitable extra and started becoming a commercial and legal expectation.

The clearest signal came out of Europe. The European Accessibility Act became enforceable on 28 June 2025, and it does not care where a business is based. If you sell a digital product or service to a consumer in any of the 27 member states, the law reaches you. That covers an online store shipping merino to Berlin, a software tool with a handful of German subscribers, a booking engine used by a European traveller. The penalties are not symbolic, running up to 100,000 euros or four percent of annual revenue depending on the country. Within days of the deadline, French disability groups had served formal legal notices on major retailers, and enforcement is widely expected to intensify across 2026 as national monitoring bodies build their auditing capacity.

Advertisement
Lead Source Pro ad. Google says it was Google, Meta says it was Meta. Lead Source Pro shows where each WordPress lead really came from.

New Zealand has its own quieter version of the same shift. Since 17 March 2025 every public service department has been required to meet the Government Web Accessibility Standard, which now adopts the international Web Content Accessibility Guidelines version 2.2 at level AA. The Government Chief Digital Officer is already working to replace that with a broader Digital Accessibility Standard that will cover mobile apps and digital services, not just web pages. If your business sells to a government agency, or hopes to, that standard flows down to you through procurement long before any law makes it universal.

For private companies the legal picture here is softer than in Europe, and worth being honest about. The Government standard does not bind private firms directly, and the Accessibility for New Zealanders Bill, which was meant to create a wider framework, has stalled and not progressed beyond a holding pattern. What remains is the Human Rights Act 1993, which prohibits discrimination in the supply of goods and services. No court has yet defined a Kiwi business’s website obligations under it, but the direction of travel overseas, where similar anti-discrimination law has been used to pursue inaccessible sites, is not encouraging for anyone hoping the question simply goes away.

The honest reason to care, though, is not the threat of a fine. It is that roughly one in six New Zealanders is disabled, around 851,000 people according to Stats NZ. Mobility, hearing and agility impairments are the most common, and the numbers climb steeply with age in a country that is ageing. The new New Zealand Disability Strategy for 2026 to 2030, published late last year, frames accessibility as a mainstream design responsibility rather than a special accommodation. When a checkout cannot be completed with a keyboard, when colour contrast is too weak to read in daylight, when form fields have no labels that a screen reader can announce, a large slice of the population is quietly turned away. They rarely complain. They simply buy somewhere else.

Advertisement

Here is the part I find most encouraging, and it connects to themes this column has returned to before. Almost everything that makes a website accessible also makes it better for everyone. Proper heading structure and semantic HTML, the unglamorous scaffolding underneath a page, is exactly what screen readers depend on and exactly what search engines reward. Captions on video help deaf users and the far larger group watching with the sound off. Sufficient colour contrast helps a low-vision user and the person squinting at a phone in the sun. Keyboard navigation that works cleanly tends to mean a site that is fast and logically built, the same qualities that drive the perceived speed I wrote about a fortnight ago. Accessibility is not a separate project bolted onto a finished site. It is what good web craft looks like when you take it seriously.

The trap to avoid is the overlay. A small industry has grown up selling a single line of JavaScript that promises instant compliance, usually a floating accessibility button. These tools are widely discredited by the disability community, have been named in a wave of overseas lawsuits rather than preventing them, and tend to break the very assistive technology they claim to help. There is no shortcut. Real accessibility is done in the markup and the design decisions, not papered over at the end.

Advertisement

For a business owner the sensible first move is modest. Run your site through a free automated checker such as WAVE or Google’s Lighthouse to get a rough baseline, understanding that automation catches perhaps a third of real problems. Then have someone actually try to use the site with a keyboard alone, and if you can, with a screen reader. The gap between what passes an automated scan and what a blind customer experiences is usually where the real work sits. When you next redesign, write accessibility into the brief from the start, because retrofitting it is far more expensive than building it in.

None of this requires treating accessibility as a moral crusade. It is closer to plumbing. You would not open a building that a wheelchair could not enter, and the digital storefront where most New Zealand commerce now happens deserves the same baseline. The businesses that understand this early will not just avoid a future legal headache. They will quietly capture the customers their competitors are turning away without realising it.

Roger McSaveney is General Manager of Forge Creative, an Auckland web design and development agency.

Have you hit accessibility barriers on New Zealand websites, or wrestled with getting your own site compliant? Share your experience in the comments below.

This article was written by AI, briefed to report the facts, hopefully without some of the bias people bring to the job 🙂

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *