Standards summary

• content is already provided in HTML format, or
• content originates in software formats for which there are no accessible alternatives (eg, CAD, some financial and economic modelling tools), in which case you must provide a summary, file format and file size and a method by which the user can contact your agency for assistance in accessing the content, or
• content was created before 31 October 2009, in which case you must provide a summary, file format and file size and a method by which the user can contact your agency for assistance in accessing the content.

All images, form image buttons, and image map hot spots have appropriate, equivalent alternative text.

Recommended technique [W3C]

G94: Providing short text alternative

Images that do not convey content, are decorative, or with content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text

Recommended techniques [W3C]

• H67: Using null alt text 
• C9: Using CSS to include decorative images

Equivalent alternatives to complex images (eg, charts, graphs) are provided in context or on a separate (linked and/or referenced via longdesc) page.

Recommended techniques [W3C]

See Sufficient Techniques for 1.1.1 - Non-text Content, situation B

Form buttons have a descriptive value.

Recommended techniques [W3C]

See Sufficient Techniques for 1.1.1 - Non-text Content Situation C: If non-text content is a control or accepts user input

Form inputs have associated text labels or, if labels cannot be used, a descriptive title attribute.

Recommended techniques [W3C]

See Sufficient Techniques for 1.1.1 - Non-text Content Situation C: If non-text content is a control or accepts user input

Embedded multimedia is identified via accessible text.

Recommended techniques [W3C]

See Sufficient Techniques for 1.1.1 - Non-text Content Situation D: If non-text content is time-based media

A descriptive text transcript (including all relevant visual and auditory clues and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files, etc.). A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track).

Related web guides

• Time-based media under WCAG2.0 (also outlines exceptions)
• Using video on the Web (advice on captions, etc)

Synchronised captions are provided for non-live, web-based video (YouTube videos, etc.)

Related web guides

• Time-based media under WCAG2.0 (also outlines exceptions)
• Using video on the Web (advice on captions, etc)

A descriptive text transcript OR audio description audio track is provided for non-live, web-based video

Related web guides

• Time-based media under WCAG2.0 (also outlines exceptions)
• Using video on the Web (advice on captions, etc)

Synchronised captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)

Related web guides

• Time-based media under WCAG2.0 (also outlines exceptions)
• Using video on the Web (advice on captions, etc)

Audio descriptions are provided for all video content. Note: Only required if the video conveys content visually that is not available in the default audio track.

Related web guides

• Time-based media under WCAG2.0 (also outlines exceptions)
• Using video on the Web (advice on captions, etc)

Semantic markup is used to designate headings (<h1>), lists (<ul>, <ol>, and <dl>), emphasised or special text (<strong>, <code>, <blockquote>, for example), etc. Semantic markup is used appropriately.

Recommended techniques [W3C]

• G115: Using semantic elements to mark up structure and H49: Using semantic markup to mark emphasized or special text

• H48: Using ol, ul and dl for lists

• H42: Using h1-h6 to identify headings

Tables are used to markup tabular data. Where necessary, data cells are associated with their headers. Data table captions and summaries are used where appropriate.

Recommended techniques [W3C]

• H51: Using table markup to present tabular information

• H39: Using caption elements to associate data table captions with data tables

• H73: Using the summary attribute of the table element to give an overview of data tables

• H63: Using the scope attribute to associate header cells and data cells in data tables [for complex tables]

• H43: Using id and headers attributes to associate data cells with header cells in data tables [for complex tables]

Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend.

Recommended techniques [W3C]

• H44: Using label elements to associate text labels with form controls

• H65: Using the title attribute to identify form controls when the label element cannot be used

• H71: Providing a description for groups of form controls using fieldset and legend elements 

The reading and navigation order (determined by code order) is logical and intuitive.

Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column"). Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").

Color is not used as the sole method of conveying content or distinguishing visual elements.

Color alone is not used to distinguish links from surrounding text unless the luminance contrast between the link and the surrounding text is at least 3:1 and an additional differentiation (e.g., it becomes underlined) is provided when the link is hovered over or receives focus.

A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.

Text and images of text have a contrast ratio of at least 4.5:1. Large text (over 18 point or 14 point bold) has a contrast ratio of at least 3:1.

Note that providing a high-contrast stylesheet will meet this standard: G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast

The page is readable and functional when the text size is doubled.

If the same visual presentation can be made using text alone, an image is not used to present that text.

All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).

Recommended techniques [W3C]

• H91: Using HTML form controls and links

Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.

A link is provided to skip navigation and other page elements that are repeated across web pages.

If a page has a proper heading structure, this may be considered a sufficient technique instead of a "Skip to main content" link. Note that navigating by headings is not yet supported in all browsers.

The homepage must also contain the following:

• A link to the website newzealand.govt.nz
• The name and/or logo of the agency primarily responsible for the website.

Agencies must provide clear contact information. Email addresses Agency websites must create the email addresses listed below. It is at the discretion of the agency whether these email addresses are published on the site. info@<domain> postmaster@<domain> webmaster@<domain> privacy@<domain> complaints by at least one of:

• enquiries@<domain>, or enquiry@<domain>
• complaints@<domain> abuse@<domain> general enquiries by at least one of:

Agency websites must provide any publicly available reports that the agency is statutorily required to produce. This includes, but is not limited to, annual reports, statements of intent, service charters and budget statements.

Note: only corporate (or "main" sites) are required to supply publicly available reports.

Minimum requirements Every website under ownership of an agency must contain a copyright statement which states (as a minimum) that: 

• the material on the website is protected by copyright; and
• anyone can utilise any of the material available on the website free of charge and without permission of the agency provided that the source and copyright status of the material is acknowledged.

Any agency that has a website containing third party copyright material must have permission from the copyright owner(s) to reproduce that material. The source and copyright status of such material must be stated in an appropriate place on the agency's website so as to avoid ambiguity as to which content items are subject to third party copyright.

The agency's website must also contain a statement (eg, in its copyright statement) that permission to utilise such material cannot be given by the agency.

Note The copyright of third parties statement, or a link to it, must be placed on the About this site page. The copyright of third parties statement may be combined with the copyright statement, or exist separately.

All agency sites must carry a privacy statement. The statement must cover (as a minimum):

• the scope of the statement (eg, "This privacy notice applies to personal and other information collected on [the agency’s] website: www.agency.govt.nz")
• the circumstances in which personal information is collected, by whom it is held (eg, your agency and/or third party agencies or web services) and any choices users may have as to whether such information is collected in the first place;
• the uses to which collected personal information may be put by the collecting agency and the circumstances in which it may be disclosed;
• the collection and use of statistical information, including users’ IP addresses;
• a statement that cookies are used if that is the case and relevant implications of that (if any);
• users’ rights to request access to or correction of personal information held by the website’s owning agency;
• contact details for such purposes.

Note also that the only requirements concerning cookies are that their use be advertised in the privacy statement, as above, and that a site works without relying on their use (as per "Technologies which may be used but not relied on").

Agencies should consider whether it is desirable or otherwise appropriate to include a content disclaimer on their websites. Whether to include a content disclaimer depends on a risk/benefit analysis, by reference to the kinds of content on the site, which takes into account the risk of claims against the agency for content which may prove to be inaccurate, as against the potentially negative message that a content disclaimer may send to users of the site, bearing in mind that members of the public may reasonably expect a government agency to stand behind what it says online and that all-embracing disclaimers may detract from public trust and confidence in the agency concerned.

Minimum requirements

Where a disclaimer is included, it should state as a minimum that the information to which it relates is true and accurate to the best of the agency's knowledge (if that is the case) but that the agency cannot accept any liability for its accuracy or content.

If the agency has not considered the accuracy of the information (eg, because it is user-generated content which the agency cannot reasonably be expected to check) then it should not say that the information is true and accurate to the best of its knowledge.

Note If it is required, the disclaimer statement, or a link to it, must be placed on the About this site page.

Agencies must provide terms of use on interactive websites and on websites that require authenticated access. Agencies are encouraged to consult their legal teams when developing such terms of use.

Placement of terms of use

Terms of use must be available on, or linked to from, both of the following: the About this site page, and the point of registration (if applicable).

1. Interactive websites An interactive website is one which enables users to contribute content which may be published on the website. Examples of interactive websites are blogs, wikis, online fora, social networking sites, photo-sharing sites and video-sharing sites. Depending on the nature of an agency's site, terms of use may need to deal with some or all of the following:

• registration and credential obligations if there is be registration and authentication of users (see further below);
• warranties on the part of site users contributing third party copyright content that they have the right to use such material;
•  indemnities in favour of the agency to protect it against loss if such warranties are breached (note, however, that thought should be given to whether inclusion of such an indemnity is appropriate by reference to the likely audience of the website and the potentially adverse message it could send to users of government services);
• ownership or licensing of users' contributions; unacceptable use and the agency's right to remove offending material;
• moderation of user-generated content; how the agency deals with instances of repeat copyright infringement by users;
• banning of abusive commenters; co-operation with authorities in the event that material breaching other parties' rights, or that is otherwise unlawful, is posted to the site; to the extent that State Services staff may contribute content to the site, a reminder of, or a term requiring compliance with, the Standards of Integrity and Conduct for the State Services;
• if the website will allow users to sign up to email notifications and if such notifications may include commercial messages (which may or may not appear on the site itself), a term dealing with such a prospect (drawn to users' attention at the time of their subscribing for email the right to amend the terms of use.

2. Websites requiring authenticated access The terms of use for an agency website that requires authenticated access must contain terms dealing with the following:

• protection of the customer's computing environment; any lifecycle requirements for the authentication key (password, token, etc);
• user responsibilities;
• processes and procedures relating to compromise or suspected compromise of the authentication key; and
• the agency's responsibilities to its online service customers.