Skip to content
https://onlinemobilecasinos.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 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
7 landmarks
REVIEW
7 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.
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 header 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
Alt Text Quality
10 of 32 images have issues
REVIEW
10 of 32 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
9 image(s) with generic alt text
Info::
2 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
32 images 20 good alt text 2 decorative 9 generic 1 missing
IssueCount
missing1 image(s)
generic9 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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 | onlinemobilecasinos.de ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
title Mobile Online Casino – überall spiele…
1.32:1
#000000
on
#202228
needs 4.5:1 (normal text)
16px · top of page (header area)
button |Menütaste
1.32:1
#000000
on
#202228
needs 4.5:1 (normal text)
16px · top of page (header area)
a Mobile Casinos
1.12:1
#000000
on
#01034C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Сasinos
1.14:1
#000000
on
#020650
needs 4.5:1 (normal text)
16px · top of page (header area)
button Сasinos
1.16:1
#000000
on
#010754
needs 4.5:1 (normal text)
16px · above the fold
a Lucky Online Casino
1.20:1
#000000
on
#030B59
needs 4.5:1 (normal text)
16px · above the fold
a Casino Dingo Online
1.18:1
#000000
on
#020A57
needs 4.5:1 (normal text)
16px · above the fold
a Betchan Casino
1.60:1
#000000
on
#1C2D62
needs 4.5:1 (normal text)
16px · above the fold
a Pelaa Casino
2.23:1
#000000
on
#174586
needs 4.5:1 (normal text)
16px · above the fold
a Justspin Casino
2.06:1
#000000
on
#204077
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Mobile Online Casino…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mobile Casino Bonus …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Das beste Tool für …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ein wahrhaft tolles …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Vorteile vom Spielen…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Einfache Anmeldung u…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Es gibt jede Menge A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Auswahl der besten O…21.00:13.0:1
#000000
#FFFFFF
Pass
title Mobile Online Casino…1.32:14.5:1
#000000
#202228
Fail
button |Menütaste1.32:14.5:1
#000000
#202228
Fail
a Mobile Casinos1.12:14.5:1
#000000
#01034C
Fail
a Сasinos1.14:14.5:1
#000000
#020650
Fail
button Сasinos1.16:14.5:1
#000000
#010754
Fail
a Lucky Online Casino1.20:14.5:1
#000000
#030B59
Fail
a Casino Dingo Online1.18:14.5:1
#000000
#020A57
Fail
a Betchan Casino1.60:14.5:1
#000000
#1C2D62
Fail
a Pelaa Casino2.23:14.5:1
#000000
#174586
Fail
a Justspin Casino2.06:14.5:1
#000000
#204077
Fail
a Gowild Casino21.00:14.5:1
#000000
#FFFFFF
Pass
a Piggy Bank Casino21.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 74/100 — 8 failing, 23 passed
REVIEW
74

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.cIVvfNR > 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
1 2 3 div.Htg5_ > div.textwidget > div.cIVvfNR > 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.cIVvfNR > 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.cIVvfNR > ul.slick-dots > li#slick-slide01
3 div.textwidget > div.cIVvfNR > 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
BONUS 100% bis zu €500 ABHOLEN AGB gültig WILLKOMMENSBONUS 100% bis zu 100 € + … div.textwidget > div.cIVvfNR > 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
ABHOLEN div.pahGV > div.Hn_Hx21 > div.b50SPyHHHvFK > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
ABHOLEN div.l5V-zE > div.sNpiscqRUGk > div.cd_WoVO > a.tzq519H53

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
AGB gültig div.b50SPyHHHvFK > div.hG8sRfMCLZ6p > noindex > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.HslLyX2kxw0 > div.JF6tg > div.hG8sRfMCLZ6p > a.Z5HNBz4VKHm
AGB gültig div.cd_WoVO > div.hG8sRfMCLZ6p > noindex > a.Z5HNBz4VKHm

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
|Menütaste header.jtUvg > div.sqB0j1Kf3S > div.c2bJnmMWvG > button#menuBtn
ABHOLEN div.pahGV > div.Hn_Hx21 > div.b50SPyHHHvFK > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
CASINO BESUCHEN div.vc-Z-CHrce > div.HslLyX2kxw0 > div.JF6tg > a.tzq519H53
○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 are distinguishable without relying on color.
●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 `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
○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 Mobile Online Casinos überall auf Ihrem Handy spielen
  • H2 Mobile Casino Bonus ohne Einzahlung – was für Angebote gibt es?
  • H2 Das beste Tool für Online-Spiele in Mobile Online Casinos
  • H2 Ein wahrhaft tolles Glücksspielerlebnis unterwegs mit einem Casino online mobil
  • H2 Vorteile vom Spielen in online Casinos auf dem Handy zum Erhalt eines Mobile Casino Bonus ohne Einzahlung
  • H2 Einfache Anmeldung und Registrierung in Mobile online Casinos – immer problemlos im losspielen
  • H2 Es gibt jede Menge Auszahlungsmethoden in Mobile Online Casinos
  • H2 Auswahl der besten Online-Spiele auf Ihrem Mobiltelefon
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