Skip to content
https://benefit-estimator.netlify.app

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
favicon.ico Missing
PNG Icons Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
9 of 29 controls have issues
REVIEW
9 of 29 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="rentPeriodSelect">; <select id="disabilityAllowancePeriodSelect">; <select id="debtPeriodSelect">; <select id="workHoursPeriodSelect">; <select id="groceriesPeriod">; <select id="powerPeriod">; <select id="internetPeriod">; <select id="transportPeriod">; <select name="Estimated Breakdown Period" id="outputPeriodSelect">
Info::
20 control(s) properly labeled
29 controls
20 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
#benefitTypeContainerselectType:for/id
#numberOfChildrenInputselectDependent children:for/id
#relationshipContainerselectRelationship Status:for/id
#ageContainerselectAge:for/id
arearadionone
arearadionone
arearadionone
arearadionone
paymentTyperadionone
paymentTyperadionone
#weeklyRentnumberRent: $for/id
#disabilityAllowanceAmountnumberAmount: $for/id
#debtRepaymentnumberAmount: $for/id
#workHoursnumberHours:for/id
#workRatenumberHourly rate: $for/id
#groceriesnumberGroceries: $for/id
#powernumberPower: $for/id
#internetnumberInternet: $for/id
#transportnumberTransport: $for/id
#winterEnergyPaymentTogglecheckboxnone
#groceriesPeriodselect(none)none
#disabilityAllowancePeriodSelectselect(none)none
#powerPeriodselect(none)none
#workHoursPeriodSelectselect(none)none
#internetPeriodselect(none)none
#rentPeriodSelectselect(none)none
#transportPeriodselect(none)none
#outputPeriodSelectselect(none)none
#debtPeriodSelectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select id="rentPeriodSelect">; <select id="disabilityAllowancePeriodSelect">; <select id="debtPeriodSelect">; <select id="workHoursPeriodSelect">; <select id="groceriesPeriod">; <select id="powerPeriod">; <select id="internetPeriod">; <select id="transportPeriod">; <select name="Estimated Breakdown Period" id="outputPeriodSelect">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
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
C
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
on
#1D4533
needs 3.0:1 (large text)
32px · top of page (header area)
title Aotearoa New Zealand Benefit Estimator
1.95:1
#000000
on
#1D4533
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Aotearoa New Zealand…1.95:13.0:1
#000000
#1D4533
Fail
title Aotearoa New Zealand…1.95:14.5:1
#000000
#1D4533
Fail
strong IMPORTANT: UNOFFICIA…5.88:13.0:1
#000000
#778D7B
Pass
span This tool was made b…5.45:14.5:1
#BB3333
#FFF8E6
Pass
a 'Check what you migh…10.16:14.5:1
#1D4533
#FFF8E6
Pass
span tool for more info o…5.45:14.5:1
#BB3333
#FFF8E6
Pass
a 0800 559 00919.82:14.5:1
#000000
#FFF8E6
Pass
div 1. Benefit type19.82:14.5:1
#000000
#FFF8E6
Pass
label If you're unsure whi…19.82:14.5:1
#000000
#FFF8E6
Pass
a MyMSD19.82:14.5:1
#000000
#FFF8E6
Pass
label Type:18.82:14.5:1
#000000
#F5F2EE
Pass
option Jobseeker Support18.82:14.5:1
#000000
#F5F2EE
Pass
option Sole Parent Support18.82:14.5:1
#000000
#F5F2EE
Pass
option Supported Living Pay…18.82:14.5:1
#000000
#F5F2EE
Pass
option NZ Superannuation18.82:14.5:1
#000000
#F5F2EE
Pass
label Dependent children:18.82:14.5:1
#000000
#F5F2EE
Pass
option None18.82:14.5:1
#000000
#F5F2EE
Pass
option 1 child18.82:14.5:1
#000000
#F5F2EE
Pass
option 2+ children18.82:14.5:1
#000000
#F5F2EE
Pass
label Relationship Status:18.82:14.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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 4 failing, 9 passed
REVIEW
72

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
per week per fortnight per month div.column > div.section > div > select#rentPeriodSelect
per week per fortnight per month div.column > div.section > div > select#disabilityAllowancePeriodSelect
per week per fortnight per month div.column > div.section > div > select#debtPeriodSelect
per week per fortnight per month div.column > div.section > div > select#workHoursPeriodSelect
per week per fortnight per month div.column > div.section > div > select#groceriesPeriod
per week per fortnight per month div.column > div.section > div > select#powerPeriod
per week per fortnight per month div.column > div.section > div > select#internetPeriod
per week per fortnight per month div.column > div.section > div > select#transportPeriod
per week per fortnight per month per year div#resultsContainer > div.result-row > div > select#outputPeriodSelect

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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-hidden="true"]` is not present on the document `<body>`
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.
Document has a `<title>` element
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
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
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
Elements use only permitted ARIA attributes
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 a valid value for its `[lang]` attribute
`<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.
A+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
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
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Input Types
29 form control(s) checked, no type mismatches
PASS
29 form control(s) checked, no type mismatches
Info::
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
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
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
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback