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

4 landmarks

FIX

4 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

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

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

2 navigation landmark(s) detected

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 2 <nav> element(s)

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.

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 | realmoneygaming.ca ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA

title Real Money Online Casino Canada | RealMo…

2.10:1

#000000

#3A4160

needs 4.5:1 (normal text)

16px · top of page (header area)

a Real Money Casino

2.10:1

#000000

#3A4160

needs 4.5:1 (normal text)

16px · top of page (header area)

span Payment Options

2.44:1

#000000

#7B1C94

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Payment Options

2.85:1

#000000

#9400AB

needs 4.5:1 (normal text)

16px · top of page (header area)

a Trustly Casinos

2.43:1

#000000

#8000A1

needs 4.5:1 (normal text)

16px · above the fold

a Zimpler Casinos

2.32:1

#000000

#7B009C

needs 4.5:1 (normal text)

16px · above the fold

a Neteller Casinos

2.29:1

#000000

#7A009A

needs 4.5:1 (normal text)

16px · above the fold

a iDebit Casinos

2.16:1

#000000

#730094

needs 4.5:1 (normal text)

16px · above the fold

a EcoPayz Casinos

2.18:1

#000000

#750094

needs 4.5:1 (normal text)

16px · above the fold

a PayPal Casinos

2.22:1

#000000

#780093

needs 4.5:1 (normal text)

16px · above the fold

a eCheck Casinos

2.15:1

#000000

#75008E

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)

Element	Ratio	Required	FG	BG	Result
h1 Real Money Online Ca…	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 The Best Real Money …	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 How to Play at Canad…	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 Real Money Bonuses a…	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 The Best Real Money …	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 How we Rank Real Mon…	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 Real Money Gaming Ba…	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h2 Real Money Mobile Ca…	18.47:1	3.0:1	#000000	#ECF0FF	Pass
h3 FAQ	18.47:1	3.0:1	#000000	#ECF0FF	Pass
title Real Money Online Ca…	2.10:1	4.5:1	#000000	#3A4160	Fail
a Real Money Casino	2.10:1	4.5:1	#000000	#3A4160	Fail
span Payment Options	2.44:1	4.5:1	#000000	#7B1C94	Fail
span Payment Options	2.85:1	4.5:1	#000000	#9400AB	Fail
a Trustly Casinos	2.43:1	4.5:1	#000000	#8000A1	Fail
a Zimpler Casinos	2.32:1	4.5:1	#000000	#7B009C	Fail
a Neteller Casinos	2.29:1	4.5:1	#000000	#7A009A	Fail
a iDebit Casinos	2.16:1	4.5:1	#000000	#730094	Fail
a EcoPayz Casinos	2.18:1	4.5:1	#000000	#750094	Fail
a PayPal Casinos	2.22:1	4.5:1	#000000	#780093	Fail
a eCheck Casinos	2.15:1	4.5:1	#000000	#75008E	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

Action

Score 72/100 — 8 failing, 21 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

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
1 `div.textwidget > div.Y3JS > ul.slick-dots > li#slick-slide00`

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
123 `div.LWq6bHs7 > div.textwidget > div.Y3JS > ul.slick-dots`

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
1 `div.textwidget > div.Y3JS > ul.slick-dots > li#slick-slide00`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
2 `div.textwidget > div.Y3JS > ul.slick-dots > li#slick-slide01`
3 `div.textwidget > div.Y3JS > ul.slick-dots > li#slick-slide02`

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
WELCOME BONUS UP TO 2250 CAD + 250 FREE SPINS CLAIM BONUS T&C Applies WELCOME B… `div.textwidget > div.Y3JS > 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
Copyright © 2026 `div.o-POm0Ardd0P > ul.n1a6QmCejR > li.AOTOBn > div.wra5Ga8VX`

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.H4N6Mjlo-yZ > div.COL3rPbruq1 > noindex > a.dF5qKSBPS`
T&C Applies `div.Riq7l > div.GGtNx > noindex > a.dF5qKSBPS`

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

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

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

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

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

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○Identical links have the same purpose.

○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

12 headings

PASS

12 headings

Single H1 present

H1 Real Money Online Casino Canada
H2 The Best Real Money Casinos Canada 2026
H2 How to Play at Canadian Casinos Online for Real Money
H2 Real Money Bonuses and Promotions
H2 The Best Real Money Casino Games
H2 How we Rank Real Money Casinos
H2 Real Money Gaming Banking Options
H2 Real Money Mobile Casinos
H3 FAQ
H4 Which games are the best to play?
H4 Do the prizes have taxes?
H4 Is it expensive?

Alt Text Quality

3 of 50 images have issues

PASS

3 of 50 images have issues

3 image(s) with generic alt text

47 image(s) with good alt text

50 images 47 good alt text 3 generic

Issue	Count
generic	3 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

1 issue(s) across 122 links and 6 buttons

PASS

1 issue(s) across 122 links and 6 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://realmoneygaming.ca/halloween/ ("Read More")

121 link(s) with descriptive text

122 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://realmoneygaming.ca/halloween/	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Halloween

127 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://realmoneygaming.ca/halloween/ ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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