Skip to content
https://kiwislot.co.nz

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) 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::
HTML icon links detected
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ 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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found | kiwislot.co.nz ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title Free Online Slots NZ: Top New Zealand Po…
2.10:1
#000000
on
#3A4160
needs 4.5:1 (normal text)
16px · top of page (header area)
a Free Online Slot Games
2.10:1
#000000
on
#3A4160
needs 4.5:1 (normal text)
16px · top of page (header area)
a No Deposit Bonus Codes
2.75:1
#000000
on
#2E5294
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a New Online Casino
1.93:1
#000000
on
#0B3A80
needs 4.5:1 (normal text)
16px · top of page (header area)
a No Deposit Bonuses
2.91:1
#000000
on
#0A57A4
needs 4.5:1 (normal text)
16px · above the fold
a Best Online Casinos
2.79:1
#000000
on
#085698
needs 4.5:1 (normal text)
16px · above the fold
a Free Casino Games
3.29:1
#000000
on
#09639E
needs 4.5:1 (normal text)
16px · above the fold
a Mobile Casino
2.84:1
#000000
on
#085990
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Game Changer: Fr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Online Slots New Zea…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How to Play Free Slo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Play Casino Slots fr…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Best Free Slots Onli…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Advantages of Playin…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Free Slots NZ Collec…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Conclusion21.00:13.0:1
#000000
#FFFFFF
Pass
title Free Online Slots NZ…2.10:14.5:1
#000000
#3A4160
Fail
a Free Online Slot Gam…2.10:14.5:1
#000000
#3A4160
Fail
a No Deposit Bonus Cod…2.75:14.5:1
#000000
#2E5294
Fail
a New Online Casino1.93:14.5:1
#000000
#0B3A80
Fail
a No Deposit Bonuses2.91:14.5:1
#000000
#0A57A4
Fail
a Best Online Casinos2.79:14.5:1
#000000
#085698
Fail
a Free Casino Games3.29:14.5:1
#000000
#09639E
Fail
a Mobile Casino2.84:14.5:1
#000000
#085990
Fail
span All casinos10.02:14.5:1
#000000
#6BBEDC
Pass
span All casinos8.22:14.5:1
#000000
#7EA6CD
Pass
a BoVegas8.09:14.5:1
#000000
#7DA2DE
Pass
a Casumo21.00:14.5:1
#000000
#FFFFFF
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 76/100 — 6 failing, 19 passed
REVIEW
76

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Play Casino Slots from Best Casino Software Developers Your casino experience … main.HN6a-gJL_RcA > section.el7qyr > article.aJzdE-1JtFX > div#collapse-69e936e0a73ae
Undoubtedly, playing online slot games is fun, but until you truly get to play … main.HN6a-gJL_RcA > section.el7qyr > article.aJzdE-1JtFX > div#collapse-69e936e0a7d6d

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.el7qyr > article.aJzdE-1JtFX > div.G8oN4Q527 > button.rK5qH
section.el7qyr > article.aJzdE-1JtFX > div.G8oN4Q527 > button.rK5qH

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Votes ul.GkaQEzeq6 > li.YgvzthEc > div.b-cctCI0qjd > span.l5kceG

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
View All div.iza > div.gRCp-J > div.EJ6fKw2vAf6d > a.u8A31BfH
View All div.U6HxKJGipuR > div.jxLYEbS-3Bp > div.PlzDyoqL > a.u8A31BfH
Read More div.sKJkpmDFH8 > div.i3FSa > div.yDXS6AJ > a.u8A31BfH
Read More div.sKJkpmDFH8 > div.i3FSa > div.yDXS6AJ > a.u8A31BfH
Copyright © 2026 div.gdfcYex > ul.TySdfiE > li.GkaQEzeq6 > div.GT_DDC

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
T&C Applies div.mXFGreRj > div.kxqBxjZT > noindex > a.zkYj746Ka
T&C Applies div.PTH3qSUFl5j > div.i6ZA9 > noindex > a.zkYj746Ka
T&C Applies div.nTe7PL > div.wpoaulvXGEF > noindex > a.zkYj746Ka
T&C Applies div.nTe7PL > div.wpoaulvXGEF > noindex > a.zkYj746Ka
T&C Applies div.nTe7PL > div.wpoaulvXGEF > noindex > a.zkYj746Ka
T&C Applies div.nTe7PL > div.wpoaulvXGEF > noindex > a.zkYj746Ka

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
5 div.c-rating-S-2 > div.f_13zLoa > div.VV4We1tT > button.x4vQx
4 div.c-rating-S-2 > div.f_13zLoa > div.VV4We1tT > button.x4vQx
3 div.c-rating-S-2 > div.f_13zLoa > div.VV4We1tT > button.x4vQx
2 div.c-rating-S-2 > div.f_13zLoa > div.VV4We1tT > button.x4vQx
1 div.c-rating-S-2 > div.f_13zLoa > div.VV4We1tT > button.x4vQx
○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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
8 headings
PASS
8 headings
Info::
Single H1 present
  • H1 The Game Changer: Free NZ Slots Online Games
  • H2 Online Slots New Zealand: The Evolution of Gambling
  • H3 How to Play Free Slot Games: Strategy and Tips to Follow
  • H3 Play Casino Slots from Best Casino Software Developers
  • H3 Best Free Slots Online
  • H3 Advantages of Playing Free Slots
  • H3 Free Slots NZ Collection
  • H3 Conclusion
A+
Alt Text Quality
All 23 images OK
PASS
All 23 images OK
Info::
4 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
23 images 19 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback