Skip to content
https://mr-bet.ca

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 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
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::
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
Back to Top
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.
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 | mr-bet.ca ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 2 pass AA only
h1 Mr Bet Casino Canada 2026
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
32px · mid-page
h2 Register a New Account with Mr Bet Canad…
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mr Bet: Deposits & Withdrawals
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mr Bet Casino Real Money Promotions In 2…
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sports Betting
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tournaments
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Games You Can Play at Mr Bet
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Review Summary
1.39:1
#000000
on
#1C224D
needs 3.0:1 (large text)
24px · bottom of viewport
title Mr Bet Casino Canada | Best Online Casin…
2.21:1
#000000
on
#343E8B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sign Up
2.21:1
#000000
on
#343E8B
needs 4.5:1 (normal text)
16px · top of page (header area)
a MR BET BETTING REVIEW
4.40:1
#000000
on
#606FB0
needs 4.5:1 (normal text)
16px · above the fold
div up to
4.03:1
#000000
on
#596B9F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span + 500 free spins
1.39:1
#000000
on
#1C224D
needs 4.5:1 (normal text)
16px · above the fold
a Register Now
1.39:1
#000000
on
#1C224D
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 Mr Bet Casino Canada…1.39:13.0:1
#000000
#1C224D
Fail
h2 Register a New Accou…1.39:13.0:1
#000000
#1C224D
Fail
h2 Mr Bet: Deposits & W…1.39:13.0:1
#000000
#1C224D
Fail
h2 Mr Bet Casino Real M…1.39:13.0:1
#000000
#1C224D
Fail
h2 Sports Betting1.39:13.0:1
#000000
#1C224D
Fail
h2 Tournaments1.39:13.0:1
#000000
#1C224D
Fail
h2 Games You Can Play a…1.39:13.0:1
#000000
#1C224D
Fail
h2 Review Summary1.39:13.0:1
#000000
#1C224D
Fail
title Mr Bet Casino Canada…2.21:14.5:1
#000000
#343E8B
Fail
a Sign Up2.21:14.5:1
#000000
#343E8B
Fail
a Login5.83:14.5:1
#000000
#6A87BF
Pass
a MR BET CASINO8.10:14.5:1
#000000
#90A1C6
Pass
a MR BET CASINO PROMOT…9.70:14.5:1
#000000
#9AB2D5
Pass
a MR BET BETTING REVIE…4.40:14.5:1
#000000
#606FB0
Fail
a PAYMENT METHODS IN M…6.69:14.5:1
#000000
#7892C2
Pass
div Winners9.55:14.5:1
#000000
#A4ADD8
Pass
span 3750 CAD8.31:14.5:1
#000000
#B790F4
Pass
div up to4.03:14.5:1
#000000
#596B9F
Fail
span + 500 free spins1.39:14.5:1
#000000
#1C224D
Fail
a Register Now1.39:14.5:1
#000000
#1C224D
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 21 passed
REVIEW
85

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
div.qhzh99Me3R > div.HVtgGKqyC2OF > div.slick-list > div.slick-track div.qhzh99Me3R > div.HVtgGKqyC2OF > 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
Sign Up div.DxSz7O6 > div.Pb0VlafE4kpV > div.zu0WcMxtMd > a.wv-M9Hx
Login div.DxSz7O6 > div.Pb0VlafE4kpV > div.zu0WcMxtMd > a.wv-M9Hx
Copyright © 2026 All rights reserved div.wD8Q > div.K5BhWue > div.DxSz7O6 > div.wLWvxv1U1

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.KPslUI3H9d > div.DxSz7O6 > div.Pb0VlafE4kpV > a.V1QoD div.KPslUI3H9d > div.DxSz7O6 > div.Pb0VlafE4kpV > a.V1QoD

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
T&C applies div.pO0fbhY6v > div.UcEzc4q-_Q > noindex > a.C3BI-

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-*]` 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]` 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 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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
8 headings
PASS
8 headings
Info::
Single H1 present
  • H1 Mr Bet Casino Canada 2026
  • H2 Register a New Account with Mr Bet Canada
  • H2 Mr Bet: Deposits & Withdrawals
  • H2 Mr Bet Casino Real Money Promotions In 2026
  • H2 Sports Betting
  • H2 Tournaments
  • H2 Games You Can Play at Mr Bet
  • H2 Review Summary
A
Alt Text Quality
2 of 17 images have issues
PASS
2 of 17 images have issues
Warning::
2 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
17 images 10 good alt text 5 decorative 2 generic
IssueCount
generic2 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchtexttype game namearia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback