DIGITAL
INFORMATION
TOOLS
Accessibility Report 19/11/2024
Tenancy Bond Form
Accessibility Test Report
under the
Released
Official Information Act 1982
under the
Released
Official Information Act 1982
Digital Information Tools Accessibility Report
1. INTRODUCTION
1.1. Context
Effective 01 July 2013, the New Zealand Government Web Accessibility Standard (the
Standard) replaces the Technical section of the New Zealand Government Web Standards 2.0.
While the previous NZ Government Web Standards 2.0 combined both accessibility and non-
accessibility requirements, the NZ Government Web Accessibility Standard includes only
accessibility-specific requirements. Other requirements unrelated to accessibility have been
included in the NZ Government Web Usability Standard. Having two separate standards helps
to clarify the focus and application of each, and makes it easier to update each one as
required.
1.2. What’s required
The Standard contains one principal requirement, namely that each web page within scope
must meet all five of the Web Content Accessibility Guidelines (WCAG) 2.1 conformance
requirements (Level A and AA success criteria).
1.3. Mandated organisations
under the
Based on a 2003 mandate established by Cabinet (Cabinet Minute (03)41/2B), all Public Service
departments and Non-Public Service departments in the State Services are directed to
implement the Standard.
Other State sector organisations are not required to implement the Standard, but are strongly
encouraged to do so. By virtue of the legislation (i.e. Human Rights Act 1993, Bill of Rights Act
1990) and New Zealand’s ratification of the United Nations Convention on the Rights of
Persons with Disabilities that underlie the requirement for mandated organisations to produce
accessible websites, there is a reasonable expectation that the websites of all Government
organisations will be accessible to the widest range of New Zealanders, including people with
disabilities.
Released
1.2.2 Scope
The Standard applies to two classes of web pages that are produced or maintained, in part or
in whole, by New Zealand Government organisations to which this Standard applies:
• publicly available web pages that can be accessed by individuals who are not
employed by a NZ Government organisation subject to the Standard. This includes web
pages that require users to authenticate themselves through some kind of login, e.g. a
Official Information Act 1982
Government extranet that restricts access to specific non-Government organisations.
• internally facing web pages that have been created, redesigned, or redeveloped since
01 July 2014, and that can be accessed only by individuals who are employed by a NZ
Government organisation subject to the Standard. This includes web pages that are
part of a Government organisation’s intranet.
Including internally facing web pages within the scope of the Standard is intended to help
Government organisations build a work environment that is:
• more open to the employment of people with disabilities, and
3
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
• consistent with provisions generally accepted as necessary for the fair and proper
treatment of employees, as identified in section 77A of the State Sector Act 1998 .
Note that the definition of web page used in this Standard includes what are typically referred
to as web applications, but also resources such as MS Word and PDF documents.
under the
Released
Official Information Act 1982
4
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
under the
Released
Official Information Act 1982
Digital Information Tools Accessibility Report
Testing is also done against a (free, open-source) screen reader, NVDA, so that no user
experiences a cost-related barrier to a working screen reading solutions. As of 2021 NVDA has
a large market share (60%+).
2.4. Contesting Results
Most testing of this nature provides clear-cut results: A web-page is either standards
conformant or not. However, in a dynamic format such as a web page, there may be rare
mitigating circumstances where one interpretation of the standard is inappropriate. In this
event, those receiving the report may like request reconsideration of one or more items, with
a written description of their reasoning.
under the
Released
Official Information Act 1982
6
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
3. TEST RESULTS
Note for the Developer:
Though most issues show a relevant link they may also be applicable to other pages/forms.
Please ensure when fixing issues that they are fixed on all page/forms the issue is applicable to
not just the form/page listed in the defect list below.
3.1. SortSite/aXe and general code issues
The following issues have been identified as non-conformant to WCAG2.1 AA
http://www.w3.org/TR/WCAG21. The issues below are those that have been investigated and
deemed to require attention.
Issue Number
Accessibility 1 ADO-BUG 35282
Issue
Required ARIA attributes must be provided
under the
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
ARIA widget roles require additional attributes that describe the
state of the widget. The state of the widget is not communicated to
screen reader users if a required attribute is omitted.
Certain roles act as composite user interface widgets. As such, they
typically act as containers that manage other, contained widgets.
When an object inherits from multiple ancestors and one ancestor
indicates support for one property while another ancestor indicates
that the same property is required, the property becomes required
on the inheriting object. In some cases, default values are sufficient
Released
to meet ARIA attribute requirements.
When required state and property attributes for specific roles (and
subclass roles) are not present, screen readers may not be able to
convey the definition of what the element's role is to the users.
Severity
Critical
Official Information Act 1982
Required Correction
Ensure elements with ARIA roles have all required ARIA attributes
Element Location:
.header_info
<div class="row header_info" role="heading">
To solve this problem, you need to fix the following:
Required ARIA attribute not present: aria-level
7
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
Comment
The first rule of ARIA is don’t use it unless you need to, use semantic
HTML where possible. Since the primary heading already has a H1
this role is not required.
Issue Number
Accessibility 2 ADO - BUG 35283
Issue
Certain ARIA roles must contain particular children
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
under the
Impact
For each role, WAI-ARIA explicitly defines which child and parent
roles are allowable and/or required. ARIA roles missing required
child roles will not be able to perform the accessibility functions
intended by the developer.
Assistive technology needs to convey the context to the user. For
example, in a treeitem, it is important to know the parent
(container), item, or siblings in the folder. This can be done in two
way.
Released
Code order or DOM: The necessary context is often clear from the
code order or DOM.
ARIA: ARIA (such as aria-owns) can be used provide the
relationships when the hierarchy is not the same as the code
structure or DOM tree.
Severity
Critical
Official Information Act 1982
Required Correction
Ensure elements with an ARIA role that require child roles contain
them
Element Location:
.header_nav_list
<ul class="header_nav_list list_semantic" role="menu" aria-
label="Main Menu">
To solve this problem, you need to fix the following:
8
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
Element has children which are not allowed: li
Related Nodes
<li class="header_nav_link link">
<a role="menuitem"
href="https://www.tenancy.govt.nz/starting-a-tenancy/">Starting a
tenancy</a>
</li>
This issue repeats for all menu items
Comment
The li needs a role of none. Please see
https://www.w3.org/WAI/ARIA/apg/patterns/menubar/examples/
menubar-navigation/
This issue is causing another 16 issues on the page.
under the
3.2. Contrast issues and responsive design
The following Contrast issues have been identified according to the AA specifications in
https://www.w3.org/TR/WCAG21/#distinguishable
WCAG 2.1 level AA requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text.
Released
Large text is defined as 14 point (typically 18.66px) and bold or larger, or 18 point (typically
24px) or larger.
Issue Number
Accessibility 3 BUG 35284
Issue
Red on white doesn’t meet contrast ratio standards
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Official Information Act 1982
Applies to all error red text, fields borders etc
Impact
User may not be able to read the text
Severity
Major
Required Correction
The red (DD4855) on white has a contrast ratio of 4.09:1 which fails
contrast ratio standards for normal text sizes.
Current text size 13.7px
9
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
WCAG 2.2 level AA requires a contrast ratio of at least 4.5:1 for
normal text and 3:1 for large text. WCAG 2.2 requires a contrast
ratio of at least 3:1 for graphics and user interface components
(such as form input borders).
Large text is defined as 14 point (typically 18.66px) and bold or
larger, or 18 point (typically 24px) or larger.
Correct in all locations used.
under the
3.1. Keyboard Issues
The following Keyboard navigation issues have been identified according to the AA
specifications in https://www.w3.org/TR/WCAG21/#keyboard-accessible.
Issue Number
Accessibility 4 ADO - BUG 35285
Released
Issue
Tab focus bounding box missing from elements or difficult to see
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User will lose position on screen.
Severity
Critical
Official Information Act 1982
Required Correction
Please see WCAG 2.1 2.4.7
https://www.w3.org/WAI/WCAG21/Understanding/focus-
visible.html
See screenshots in notes below:
Please ensure the focus bounding box is compliant for all focusable
elements on all pages.
10
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
I would suggest a black and white bounding box with spacing to
ensure that the criteria are met in all circumstances, this also makes
it consistent throughout for the user.
Previously activated radio buttons have no focus indicator
under the
Calendar icon has focus indicator. Since the calendar widget isn’t very accessible, please also
ensure it doesn’t appear in the tab order of the page and that a screen reader skips it. Applies
to all date’s pickers.
Released
Official Information Act 1982
The below button focus colour isn’t great enough, please apply a bounding box to all elements.
11
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
3.2. NVDA Issues
NVDA has been chosen as the standard for the testing for Screen readers. Using NVDA the
following issues have been found.
Issue Number
Accessibility 5 ADO -BUG 35286
Issue
Adding another tenant button adds it above current focus
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User won’t know where the new form fields have appeared
Severity
Major
under the
Required Correction
Please ensure that any new field which appears based on the user’s
selection appears below the current focus.
Released
Official Information Act 1982
12
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
under the
Issue Number
Accessibility 6 ADO - BUG 35287
Issue
Decorative image needlessly read to user
Released
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User read undescriptive and needless image alt text
Severity
Medium
Required Correction
Please give this image a blank alt tag so screen readers skip it.
Official Information Act 1982
13
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
Issue Number
Accessibility 7 ADO - BUG 35288
Issue
Fields not grouped
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User not read the question or section name
Severity
Critical
Required Correction
Please ensure that all controls are grouped with a fieldset and
legend tag.
https://www.w3.org/WAI/tutorials/forms/grouping/#radio-buttons
https://www.w3.org/WAI/tutorials/forms/grouping/#related-fields
Applies to all groups of radio buttons
under the
Released
Official Information Act 1982
Landlord and other section headings are not read to the user
14
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
Issue Number
Accessibility 8 ADO - BUG 35289
Issue
Date field label not read to the user
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
under the
Impact
User will not know what date they are entering
Severity
Critical
Required Correction
It has a label but its not being read to the user and doesn’t appear in
the accessibility tree, this is because the input id is wrong and so the
label isn’t being picked up.
Released
Official Information Act 1982
15
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
Issue Number
Accessibility 9 ADO - BUG 35290
Issue
Unable to remove uploaded file
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User will not be able to focus on the x remove icon
Severity
Critical
Required Correction
Only the svg is selectable for the deletion of the file but is not
under the
focusable using a keyboard.
Released
Official Information Act 1982
Issue Number
Accessibility 10 ADO - BUG 35291
Issue
Issues with field validation
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User may find it hard to find their error
16
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
Severity
Critical
Required Correction
Please ensure form error messages are summarised at the top of
the form in an ARIA live region with descriptions of the issues and
links to fields in question.
https://webaim.org/techniques/formvalidation/
Also please ensure that when a field has an inline error message it’s
read to the user when the field gets focus.
E.g.
Missing links to fields and ARIA live region, also needs to be placed at the top of the form and
focus needs to be moved to it.
under the
Released
Issue Number
Accessibility 11 ADO - BUG 35292
Issue
Footer logos not fully read to user
Official Information Act 1982
Link
https://uat.tools.tenancy.govt.nz/lodge-your-bond
Impact
User not read Māori part of logo
Severity
Medium
Required Correction
Ensure the lang tag of mi is applied to the part of the logo in the
Māori language.
17
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
Digital Information Tools Accessibility Report
See below example screenshot taken from a different website.
Applies to both logos.
NZ government logo is setup as below
Applies to both MBIE and NZ government logo
under the
Released
Official Information Act 1982
18
MINISTRY OF BUSINESS, INNOVATION & EMPLOYMENT
DOCUMENT TITLE
