Skip to main content

About the Web Accessibility Guidance project

Find out about the purpose and scope of the web accessibility guidance, who it’s for and how you can give feedback on its early drafts.

Join the Guidance Review Group

If you’re a digital practitioner who designs, builds, tests or publishes content on web pages, we’d love your feedback on early drafts of the new web accessibility guidance.

If you’d like to be involved, email web.standards@dia.govt.nz and let us know the roles or skillsets you can help with.

Purpose of the guidance

The guidance aims to help build accessibility capability across the public sector and New Zealand web community in order to improve the accessibility of government online information and services.

This means helping practitioners understand what’s involved in producing content that meets the Web Content Accessibility Guidelines (WCAG) 2.1 as per the NZ Government Web Accessibility Standard.

It will be useful to anyone delivering digital content in New Zealand, whether they’re in the public or private sector.

What’s in the guidance

There are 2 categories of guidance:

Web content types (A–Z) that practitioners typically build

Note:

This list is subject to change without notice during the development of the guidance.

Items with an asterisk (*) are next on the list to be published.

See the topics that have been published or are in the final stages of being reviewed by the Guidance Review Group by following the links below.

  • Accordions*
  • Abbreviations
  • Addresses*
  • Alerts
  • Animations and motion
  • Audio
  • Breadcrumbs
  • Buttons
  • CAPTCHA
  • Cards / tiles*
  • Carousels / slideshows
  • Data visualisations
  • Dialogs (modal and non-modal)
  • EPUB3
  • Feeds
  • Footnotes
  • Forms and form controls
  • Glossaries
  • Grids
  • Headers and footers
  • Headings
  • Iframes
  • Images
  • Links
  • Lists
  • “Load more” buttons 
  • Maps
  • Maths (MathML)
  • Media players
  • Menus
  • PDF and Office documents (Word, Excel, PowerPoint)*
  • Page loading
  • Page titles*
  • Quotations and citations
  • Search
  • Sidebars / asides
  • Site maps
  • Skip links
  • Sliders
  • Status messages
  • Switch
  • Tab panels
  • Tables
  • Tables of contents
  • Text content
  • Tooltips
  • Tree views
  • Videos

For each web content type, the guidance explains:

  • how to make it accessible
  • what good looks like (examples)
  • who benefits from this work
  • which WCAG success criteria this work meets
  • how to test that the work has been done right.

Knowledge areas

Note:

This list is subject to change without notice during the development of the guidance.

Items with an asterisk (*) are next on the list to be published.

See the topics that have been published or are in the final stages of being reviewed by the Guidance Review Group by following the links below.

Fundamental concepts in web accessibility

How disabled people use the web

Accessible UX best practices

Delivering accessible web content

Embedding accessibility in your organisation

  • Accessibility in your policies
  • Accessibility in tenders and contracts*
  • Accessibility training
  • Accessible authoring tools and Content Management Systems
  • Commitment and responsibility
  • Monitoring, assurance and accountability
  • Procurement and accessibility

When the guidance will be published

The guidance will be delivered in several phases as batches of related content.

The first set of guidance topics was published in December 2021.

See a list of the most recently added guidance.

Who the guidance is for

The guidance is being written from the perspectives of 7 typical roles or functions that affect the accessibility of a digital product or service.

Each of these roles will have its own web page with links to the guidance that’s directly relevant to it.

There are 2 types of roles: roles with direct impact on the accessibility of web content, and roles with influence.

Roles with direct impact

People in these roles make sure that the user interface, content and web technologies (for example, HTML, CSS and JavaScript) are implemented in ways that work for disabled people and their devices.

Roles with influence

People performing these roles make sure that accessibility work is:

  • supported with expertise, tools and training
  • baked into the product lifecycle
  • validated through user research with people of diverse abilities
  • included as part of quality assurance.

More information

If you have any questions about this project, email web.standards@dia.govt.nz.

Blog posts about this project

Utility links and page information

Was this page helpful?
Thanks, do you want to tell us more?

Do not enter personal information. All fields are optional.

Last updated