| Website accessibility means making website information and functions usable by disabled people, including people who use a keyboard, screen reader, magnification or other assistive technology. It affects whether someone can find information, request a quote, book or buy. |
Here is a hypothetical. A trade supplier adds a quote request form to its website. The office manager tests it with a mouse, the enquiry arrives, and the form goes live.
A long-standing customer with arthritis moves through pages with the keyboard instead of a mouse. Tab does not reach the send button, so he phones the counter, as do a handful of other customers each week. Nobody connects the calls to the form.
When someone finally checks the page, four ordinary faults turn up. The send button cannot be reached from the keyboard, the theme has hidden the focus indicator, three fields have no programmatic label, and the grey helper text falls below the contrast minimum. The supplier had also paid for an overlay widget after being told it would handle compliance, and the widget fixed none of the four.
New Zealand’s Government Web Accessibility Standard applies to specified government organisations. A private business is not automatically subject to that same mandate, but anti-discrimination obligations, contracts and overseas market rules can still be relevant. WCAG 2.2 Level AA provides a practical target for improving a site. Start with the checks below, then scope further testing around the pages and tasks people need to use.
Does a New Zealand Business Have to Meet Website Accessibility Rules?
Not under the government standard, but that does not make website accessibility optional. The standard directs specified government organisations, while discrimination duties, contracts and overseas rules can still apply to a private business.
What is the Government Web Accessibility Standard?
The Web Accessibility Standard 1.2 took effect on 17 March 2025. It directs Public Service departments, along with the Police, the Defence Force, the Parliamentary Counsel Office and the Security Intelligence Service, to meet WCAG 2.2 Level AA for in-scope public and internal pages, subject to defined exceptions. Other public sector and local government organisations are encouraged to apply it, and our local government IT support page covers that sector.
The exceptions carry specific conditions for maps, media and inactive pages. They are not general permission to skip accessibility, so read the conditions on the standard itself before relying on one.
A draft Digital Accessibility Standard went to consultation in 2026 and is expected to replace version 1.2 in early 2027. Until it is published, version 1.2 is the current standard.
Could an inaccessible website breach the Human Rights Act?
It depends on the facts. Section 44 of the Human Rights Act 1993 covers discrimination in the provision of goods, facilities and services to the public, disability is a prohibited ground under section 21, and the Act also addresses indirect discrimination.
Whether a particular barrier breaches the Act depends on the circumstances and the exceptions that apply. A WCAG failure does not automatically prove a breach, and the absence of a private sector WCAG mandate does not rule one out. Establish your customers’ needs, the scope of any assessment and your actual obligations before deciding what to fix first.
Do overseas rules reach a New Zealand website?
They can. The European Accessibility Act has applied through national laws since 28 June 2025 to specified products and consumer services, including e-commerce. It is not a blanket rule for every overseas sale: scope, transitions and exemptions matter, including a microenterprise exemption for service providers. Check the market and business model you actually sell into.
Why Does Website Accessibility Matter to a Business?
Because a share of your customers meet barriers that a careful site removes. Stats NZ reported in its Household Disability Survey 2023 that 17 percent of people in New Zealand households were disabled, about 851,000 people, and that the rate for adults aged 65 and over was 35 percent.
Those figures do not mean the same share cannot use a website, or that every disabled person meets the same barrier. Read them as a reason to check the tasks your customers need to complete, particularly if your customer base is older than the national average.
Temporary and situational limits matter too. A broken wrist, a cracked phone screen or bright sun on a job site can make the same page hard to use.
Which impairments change how somebody uses a website?
Sight, hearing, movement, and cognition or memory each bring different needs.
A person with low vision may enlarge text or use a screen reader. A person with arthritis or a healing wrist may drive the site from the keyboard. A deaf customer needs accurate captions on video and a way to make contact without phoning. Someone whose concentration is affected needs clear instructions, enough time to finish a form and an error message naming the field that needs attention.
What Does WCAG Require for Website Accessibility?
WCAG sets out testable success criteria for web content, grouped into three conformance levels. The Web Content Accessibility Guidelines come from the World Wide Web Consortium.
WCAG 2.2 was first published as a W3C Recommendation on 5 October 2023, and an updated Recommendation followed on 12 December 2024. WCAG 3 is still a draft, so WCAG 2.2 remains the practical target.
What do WCAG levels A, AA and AAA mean?
Level A covers the basic requirements, Level AA adds further criteria, and Level AAA is the strictest. Level AA conformance requires every applicable Level A and AA criterion to be met, on full pages and across complete processes such as a whole checkout, along with the other conformance conditions. It is not a scanner score or a pass on a few checks.
W3C does not recommend requiring Level AAA as a general policy for whole sites, because some content cannot meet it. When you commission work, name the WCAG version, the level, the pages and processes in scope, and the acceptance criteria.
Does WCAG apply to a PDF or an embedded booking system?
Yes. WCAG covers web content, including documents you publish and tools you embed.
An image-only scanned PDF creates a serious barrier. A scan may already contain an OCR text layer, so being able to select text is a clue, not proof of accessibility: the accuracy of the OCR, structure, reading order and alternatives still need checking. Provide the content as accessible web text where practical.
An embedded booking or payment widget carries its supplier’s accessibility into your site. Include it in testing and ask the supplier what they have assessed.
What Does Semantic Markup Do for a Screen Reader?
Semantic markup tells assistive technology what each part of a page is. A screen reader uses information the browser exposes through its accessibility interfaces, including names, roles, states and structure, so it can announce a heading as a heading and a button as a button.
Screen reader users navigate in different ways, such as moving by headings, landmarks, links or form fields, rather than hearing every page in raw source order. A customer looking for your phone number may open a list of headings and jump straight to the contact section.
Visual cues need a programmatic equivalent. The word Required in bold red may be available to software, but colour and styling alone do not reliably tell a screen reader user which field is required. Associate labels and instructions with the field and mark the required state in the markup.
What does a sound heading structure look like?
One clear main heading for the page, then section headings in a logical hierarchy. A heading is a structural element, not a font size, so text that only looks like a heading does not appear in a screen reader’s list of headings.
Moving back up to a new section can legitimately skip levels; a confused hierarchy is the problem. W3C’s headings tutorial explains the difference.
When is an ARIA label needed?
Prefer native HTML controls and meaningful visible link text. ARIA supplies accessible semantics where native elements cannot, but it does not add keyboard operation by itself, and the W3C authoring practices warn that misused ARIA can make a page harder to use.
An icon-only button with no visible text needs an accessible name. Where a control has a visible label, keep the accessible name consistent with it, because an aria-label can override a useful visible name. Repeated Read more links are better fixed with descriptive link text.
How Do You Check Website Accessibility on Your Own Site?
Start with four manual checks as a first review. A pass shows that these checks found no fault; it does not establish WCAG conformance. W3C’s Easy Checks describe a similar first review.
- Keyboard operation. Every interactive control reachable and usable, with visible focus
- Text contrast. Text readable against its actual background
- Form labels and feedback. Instructions, required fields and errors tied to each field
- Images. Alternatives chosen by purpose, in context
Automated scanners such as WAVE, axe DevTools and the Lighthouse audit in Chrome find some problems and miss those that need judgement. None can tell you whether an alternative describes an image well or whether a task makes sense.
How do you test keyboard navigation?
Put the mouse aside and use Tab and Shift+Tab to move between interactive controls. Then use the keys each control expects, such as arrows, Enter, Space and Escape.
Check that focus stays visible, follows a sensible order and does not get trapped. Open and close menus and dialogs and confirm that focus returns to a sensible place. Keyboard checks cover interactive controls; content such as paragraphs does not need to take focus. A visible focus indicator can take forms other than the CSS outline. See W3C’s keyboard guidance, and use an agreed test route for form submissions rather than sending real enquiries.
What colour contrast does text need?
Level AA asks for a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text. Large means at least 18 point, or 14 point bold, roughly 24 or 18.7 CSS pixels.
Check text in its actual states and backgrounds, including hover, focus and text over images. Controls and focus indicators have related requirements, and some text, such as logos, has exceptions. A darker shade of a brand colour is one possible fix.
Which website accessibility checks live in your own content?
Image alternatives and form wording are two checks that site editors control directly. Choose image alternatives by purpose: an informative image needs its meaning, a functional image needs the action or destination, a decorative image needs an empty alternative, and a complex diagram may need a longer explanation beside it. Review each image where it is placed, because media library text can be wrong for a particular page.
For forms, check visible instructions, programmatic labels, required fields, error messages and the confirmation. A placeholder vanishes once someone types, while a proper label stays visible and is announced.
What does a fuller website accessibility review cover?
A comprehensive review also considers zoom and reflow, focus hidden by sticky headers, pointer target size, alternatives to dragging, authentication, error handling, time limits, documents and any third-party widgets. WCAG 2.2 Level AA sets a target size minimum of 24 by 24 CSS pixels, with exceptions such as spacing and links within text. These items shape the scope of an assessment; a short checklist does not cover them.
What Does Fixing Website Accessibility Cost a Small Business?
Website accessibility costs depend on the site, the journeys in scope, content, documents, media, integrations and the target. Time, skills, custom controls, third-party systems and regression testing all affect the scope, so assess before quoting, and count staff time as a cost.
| What to check | How to test it | Who fixes it |
|---|---|---|
| Keyboard operation | Tab and Shift+Tab, then the keys each control expects | Developer or theme owner |
| Text contrast | A contrast checker on actual states and backgrounds | Whoever controls the theme styles |
| Form labels and feedback | Instructions, labels, required fields, errors and confirmation | Developer, or settings in the form builder |
| Image alternatives | Each image reviewed by purpose, in its page context | Whoever edits the content |
| Heading structure | The page outline or headings list | Content editor, or developer for template headings |
| Video captions | Caption accuracy and meaningful sounds | Whoever publishes the video |
| Overlay widget | The site tested with the widget enabled | Decide after testing what it supplies |
Some of this is content work for whoever already edits the site. Other items sit in templates, form builders or third-party systems, and content work is not automatically cheap, just as developer work is not automatically expensive. Separate the two in any findings so each goes to the right person.
What can you start on without a developer?
Image alternatives, link wording, headings in your own content and video captions are within reach of anyone who edits the site. Start with the pages that carry enquiries, bookings or sales, because a barrier there stops a customer completing the task.
You do not need every page assessed before the first fix goes live. Retest each change, including on a phone.
Do Website Accessibility Overlay Widgets Work?
An accessibility overlay may change presentation or attempt selected repairs, but installing one does not demonstrate WCAG conformance. Assess the actual site with the tool enabled, test the important journeys and check for interference with assistive technology. Fix underlying design, content and code where possible, and verify the result.
What can an overlay change?
A script can change the live page, including some accessibility semantics, so an overlay can alter text size, contrast or spacing and attempt some repairs. Whether a particular change is correct and reliable needs testing. A product cannot infer meaning that the page does not provide, repair every interaction or prove conformance.
In April 2025 the US Federal Trade Commission finalised an order against accessiBe over deceptive claims that its tool could make any website compliant. That supports scrutiny of compliance claims. It is not a New Zealand ruling, and not a verdict that every overlay is useless.
Why do some disabled users object to overlays?
Many people arrive with assistive technology and settings already configured, and an injected toolbar or reading mode can interfere with them. Browsers and operating systems also carry their own text size and contrast controls.
If your site carries an overlay, make a planned decision. Check what it supplies, arrange replacement fixes and support where needed, and remove it once the effect has been tested, rather than removing a function people rely on overnight.
How Do You Build Website Accessibility Into Your Next Site?
Write website accessibility into the brief, test it at acceptance and keep it in the maintenance routine.
Name the target
State WCAG 2.2 Level AA, the pages and processes in scope, and the acceptance criteria in the brief.
Ask how they test
Ask agencies how they test with a keyboard and assistive technology, and whether disabled users take part where practical.
Test before sign-off
Add the first-review checks and agreed testing to acceptance, so sign-off does not rest on the builder’s word.
Write the content rules
Give editors rules for image alternatives, headings, link text, documents and captions.
Retest after changes
Retest key tasks after theme, plugin or form changes, because a template change can remove a focus indicator.
Record decisions
Record what was fixed, known limitations and warranty terms, so the next person keeps the work in place.
A commissioned application carries the same requirement, and our guide to software built to order covers how to specify it. Who holds the hosting login and applies updates is a separate layer, covered by our website hosting and maintenance service. Charities serve many of the people affected, and our not-for-profit IT support page covers that sector.
Get Help With Website Accessibility
Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide. Our IT consulting team runs a manual first review of the pages and tasks your customers rely on, checking keyboard use, focus, contrast, labels, images and headings.
We agree the pages, target and limits first. Findings are prioritised by whether a customer can complete an important task, how many people and pages each issue affects, and your applicable obligations, with content changes separated from developer or specialist work. Full WCAG audits and assistive technology testing are scoped separately, and we coordinate fixes and retesting with your developer. A first review is not a conformance certificate.
NEXT STEP
Can every customer finish what they came to your site to do?
Talk to Exodesk about a first accessibility review. We check the pages and tasks your customers rely on, prioritise what stops them, and agree who fixes and retests each issue.
Or read more about our website hosting and maintenance.
Frequently Asked Questions
What is website accessibility?
It means making website information and functions usable by disabled people, including people using keyboards, screen readers and magnification. Check whether people can complete tasks such as finding information, requesting a quote or buying.
Does a private business in New Zealand have to be WCAG compliant?
The Government standard does not automatically mandate every private business. Anti-discrimination duties, contracts and overseas rules can still matter. WCAG 2.2 AA is a practical target, so establish your obligations and assessment scope rather than treating accessibility as optional.
What is WCAG 2.2?
It is a W3C web accessibility standard, first published in October 2023 and updated in December 2024. AA conformance includes the applicable A and AA criteria and other conditions. A short checklist or scanner score cannot establish it.
Is an accessibility overlay worth the subscription?
A widget may offer selected adjustments or repairs, but its presence does not prove conformance. Test customer journeys and assistive technology compatibility with it enabled. Prioritise durable fixes and check the effect before removing a function people rely on.
How much does it cost to make a website accessible?
It depends on the site, journeys, content, documents, integrations and target. Scope the assessment, remediation and retesting before quoting. Some content fixes need little more than editing time, while custom controls and third-party systems may need specialist work. Staff time is still a cost.
What is a screen reader?
It is assistive software that presents interface and content information through speech or braille. It uses information supplied through the browser or platform and supports different navigation methods. Meaningful headings, labels, roles, states and reading order help people use the page.
How do I check my own website using only a keyboard?
Use Tab and Shift+Tab to move between controls, and the keys each control expects, such as arrows, Enter, Space or Escape. Check visible focus, menus, dialogs and forms, including errors and where focus returns. Use a controlled test route for submissions, and treat this as an initial check.
What is an accessibility statement and do we need one?
It explains the accessibility of a site, known limitations, support contacts and how to request an alternative. Base it on assessed facts and keep it current. Whether a statement is required depends on applicable rules and contracts, and publishing one does not itself demonstrate conformance.
Do accessibility rules apply if we sell to customers overseas?
They may. Check the market, service and applicable national rules. The European Accessibility Act covers specified products and services from June 2025, with exemptions and transitions, including a microenterprise exemption for service providers. Selling overseas alone does not settle the scope.
Does website accessibility help SEO?
Clear structure, meaningful links and text alternatives can help users and make content easier to understand. Accessibility work does not assure rankings, rich results or AI citations. Measure task completion and customer access alongside relevant search performance.
Who is responsible if a web developer built an inaccessible site?
Agree responsibilities, the target, testing and remediation in the contract. The business must address barriers affecting its customers, but supplier duties, warranties and possible remedies do not necessarily disappear after launch. Ownership alone does not decide who pays for every fix.
Can Exodesk check our website accessibility?
Yes. Exodesk runs a manual first review of the pages and tasks your customers rely on, covering keyboard use, focus, contrast, labels, images and headings. We agree the pages, target and limits first, along with who fixes and retests issues. A first review is not proof of WCAG conformance, and fuller audits and assistive technology testing are scoped separately.
Contact us or call 0800 396 337 to talk about your website accessibility.
