Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

18 pass 2 fail WCAG AA 2 pass AA only

h1 Aotearoa New Zealand Benefit Estimator

1.95:1

#000000

#1D4533

needs 3.0:1 (large text)

32px · top of page (header area)

title Benefit Estimator

1.95:1

#000000

#1D4533

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Aotearoa New Zealand…	1.95:1	3.0:1	#000000	#1D4533	Fail
title Benefit Estimator	1.95:1	4.5:1	#000000	#1D4533	Fail
strong This is a rough esti…	19.82:1	3.0:1	#000000	#FFF8E6	Pass
span Use MSD's	5.45:1	4.5:1	#BB3333	#FFF8E6	Pass
a 'Check what you migh…	10.16:1	4.5:1	#1D4533	#FFF8E6	Pass
span tool for more info o…	5.45:1	4.5:1	#BB3333	#FFF8E6	Pass
a 0800 559 009	19.82:1	4.5:1	#000000	#FFF8E6	Pass
div 1. Benefit type	19.46:1	4.5:1	#000000	#FBF6E9	Pass
label If you're unsure whi…	18.82:1	4.5:1	#000000	#F5F2EE	Pass
a MyMSD	18.82:1	4.5:1	#000000	#F5F2EE	Pass
label Type:	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option Jobseeker Support	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option Sole Parent Support	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option Supported Living Pay…	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option NZ Superannuation	18.82:1	4.5:1	#000000	#F5F2EE	Pass
label Dependent children:	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option None	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option 1 child	18.82:1	4.5:1	#000000	#F5F2EE	Pass
option 2+ children	18.82:1	4.5:1	#000000	#F5F2EE	Pass
label Relationship Status:	18.82:1	4.5:1	#000000	#F5F2EE	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Aotearoa New Zealand Benefit Estimator

A+

Heading Text Quality

All 1 heading(s) have substantive, well-formed text

PASS

All 1 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

All 29 controls labeled

PASS

All 29 controls labeled

29 control(s) properly labeled

29 controls

29 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#benefitTypeContainer	select	Type:	for/id
#numberOfChildrenInput	select	Dependent children:	for/id
#relationshipContainer	select	Relationship Status:	for/id
#ageContainer	select	Age:	for/id
area	radio		none
area	radio		none
area	radio		none
area	radio		none
paymentType	radio		none
paymentType	radio		none
#weeklyRent	number	Rent: $	for/id
#rentPeriodSelect	select	Rent payment period	aria-label
#disabilityAllowanceAmount	number	Amount: $	for/id
#disabilityAllowancePeriodSelect	select	Disability allowance payment period	aria-label
#debtRepayment	number	Amount: $	for/id
#debtPeriodSelect	select	Debt repayment payment period	aria-label
#workHours	number	Hours:	for/id
#workHoursPeriodSelect	select	Work hours period	aria-label
#workRate	number	Hourly rate: $	for/id
#groceries	number	Groceries: $	for/id
#groceriesPeriod	select	Groceries cost period	aria-label
#power	number	Power: $	for/id
#powerPeriod	select	Power cost period	aria-label
#internet	number	Internet: $	for/id
#internetPeriod	select	Internet cost period	aria-label
#transport	number	Transport: $	for/id
#transportPeriod	select	Transport cost period	aria-label
#outputPeriodSelect	select	Breakdown display period	aria-label
#winterEnergyPaymentToggle	checkbox		none

Link & Button Quality

6 links, 1 buttons — all OK

PASS

6 links, 1 buttons — all OK

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://check.msd.govt.nz/; https://my.msd.govt.nz/login; https://www.workandincome.govt.nz/map/deskfile/extra-help-information/accommo…; https://my.msd.govt.nz/login; https://my.msd.govt.nz/login

1 link(s) with descriptive text

6 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://check.msd.govt.nz/	'Check what you might get'	new tab	Add '(opens in new tab)' to text
https://my.msd.govt.nz/login	MyMSD	new tab	Add '(opens in new tab)' to text
https://www.workandincome.govt.nz/map/de…	Find your area here.	new tab	Add '(opens in new tab)' to text
https://my.msd.govt.nz/login	MyMSD	new tab	Add '(opens in new tab)' to text
https://my.msd.govt.nz/login	MyMSD	new tab	Add '(opens in new tab)' to text

2 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://check.msd.govt.nz/; https://my.msd.govt.nz/login; https://www.workandincome.govt.nz/map/deskfile/extra-help-information/accommo…; https://my.msd.govt.nz/login; https://my.msd.govt.nz/login

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

29 form control(s) checked, no type mismatches

PASS

29 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

29 form control(s) checked, no input-semantic issues

PASS

29 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 63 visible text node(s) render at >= 12 CSS pixels

PASS

All 63 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 18 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accommodation Supplement `div.column > div#resultsContainer > div#accomodationSupplementRow > span#accomodationSupplementAreaLabel`
+$0.00 `div.column > div#resultsContainer > div#accomodationSupplementRow > span#accomodationSupplementFnResult`

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.