Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

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.

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

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'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ 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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found | Mr Bet ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 11 pass AA only

title Mr. Bet Casino - 2026 Free Pokie Games t…

1.34:1

#000000

#1A242E

needs 4.5:1 (normal text)

16px · top of page (header area)

div WELCOME BONUS

1.34:1

#000000

#1A242E

needs 4.5:1 (normal text)

16px · top of page (header area)

div 2250 NZD

1.34:1

#000000

#161070

needs 4.5:1 (normal text)

16px · top of page (header area)

a Get bonusl

1.41:1

#000000

#201277

needs 4.5:1 (normal text)

16px · top of page (header area)

a Sign Up

1.36:1

#000000

#220B73

needs 4.5:1 (normal text)

16px · above the fold

a Login

1.45:1

#000000

#2E0E77

needs 4.5:1 (normal text)

16px · above the fold

a MrBet Casino

1.46:1

#000000

#2C1079

needs 4.5:1 (normal text)

16px · above the fold

a Online Pokies NZ

1.43:1

#000000

#2A0E77

needs 4.5:1 (normal text)

16px · above the fold

a Free Spins No Deposit

1.40:1

#000000

#1F0E7A

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 FREE POKIES 2026 ON …	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 MR BET CASINO GAMES:…	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 FREE MRBET POKIES ON…	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 No Download Free Pok…	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 How to Win at Online…	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 Mr Bet App	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 Mr Bet Login	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 Mr Bet Casino Bonus	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 Withdrawal	4.49:1	3.0:1	#000000	#656DBF	Pass
h2 FAQs	4.49:1	3.0:1	#000000	#656DBF	Pass
h3 Read Also:	4.49:1	3.0:1	#000000	#656DBF	Pass
title Mr. Bet Casino - 202…	1.34:1	4.5:1	#000000	#1A242E	Fail
div WELCOME BONUS	1.34:1	4.5:1	#000000	#1A242E	Fail
div 2250 NZD	1.34:1	4.5:1	#000000	#161070	Fail
a Get bonusl	1.41:1	4.5:1	#000000	#201277	Fail
a Sign Up	1.36:1	4.5:1	#000000	#220B73	Fail
a Login	1.45:1	4.5:1	#000000	#2E0E77	Fail
a MrBet Casino	1.46:1	4.5:1	#000000	#2C1079	Fail
a Online Pokies NZ	1.43:1	4.5:1	#000000	#2A0E77	Fail
a Free Spins No Deposi…	1.40:1	4.5:1	#000000	#1F0E7A	Fail

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.

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 31 passed

REVIEW

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

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NETENT BETSOFT NOVOMATIC ARISTOCRAT NETENT BETSOFT NOVOMATIC ARISTOCRAT `div.T3s0HSxn7m > div.AyEtDLY > div.slick-list > div.slick-track`

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
Get bonusl `div.l1VKO1 > div.yffi4zA7F > div.Qi9Jec > a.Yf76Hnpu1d`
Sign Up `div.KUAHb > div.Z6ZoshKmu > div.LUcoAE > a.Yf76Hnpu1d`
Login `div.KUAHb > div.Z6ZoshKmu > div.LUcoAE > a.Yf76Hnpu1d`
Register Now `div.KUAHb > div.A4CrgnEUnWfI > div.qo9hSpasJA > a.Yf76Hnpu1d`
Register Now `div.pmnKd8W > div.p_C7h > div.qo9hSpasJA > a.Yf76Hnpu1d`
withdrawal `div.ZzQKd > div.KUAHb > p > a`
real money `div > div > p > a`
https://news.worldcasinodirectory.com/world/oceania-casinos-news `div.mgTbu > div.ZzQKd > div.KUAHb > a`
https://www.gamblinghelpline.co.nz/ `div.mgTbu > div.ZzQKd > div.KUAHb > a`
Copyright © 2026 All rights reserved `div.W4TrVw > div.YH5FNO9JY > div.KUAHb > div.efiJuenv`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.W4FhH58oxjOG > div.KUAHb > div.Z6ZoshKmu > a.InlPjjKyTI `div.W4FhH58oxjOG > div.KUAHb > div.Z6ZoshKmu > a.InlPjjKyTI`

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

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
5 `div.c-vote > div.c-vote__text > div.c-vote__box > button.c-vote__btn`
4 `div.c-vote > div.c-vote__text > div.c-vote__box > button.c-vote__btn`

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-*]` attributes match their roles

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

●`[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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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.

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

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

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

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

●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.

●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

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

●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.

●Elements with visible text labels have matching accessible names.

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

○`[accesskey]` values are unique

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

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○`<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.

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

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 FREE POKIES 2026 ON MR. BET: PLAY 3500+ FREE POKIE GAMES AND WIN TODAY!
H2 MR BET CASINO GAMES: WHY PLAY FREE POKIES?
H2 FREE MRBET POKIES ON MOBILE AND TABLET
H2 No Download Free Pokies
H2 How to Win at Online Pokies
H2 Mr Bet App
H2 Mr Bet Login
H2 Mr Bet Casino Bonus
H2 Withdrawal
H2 FAQs
H3 Read Also:

Alt Text Quality

2 of 45 images have issues

PASS

2 of 45 images have issues

2 image(s) with generic alt text

1 decorative image(s) correctly marked

42 image(s) with good alt text

45 images 42 good alt text 1 decorative 2 generic

Issue	Count
generic	2 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	text	type game name	aria-label

Link & Button Quality

1 issue(s) across 121 links and 10 buttons

PASS

1 issue(s) across 121 links and 10 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://mrbetgames.com/

120 link(s) with descriptive text

121 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://mrbetgames.com/	(empty)	empty	Add link text or aria-label

130 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://mrbetgames.com/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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