Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 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 ✗

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 Page not found - trino-casino.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h1 Trinocasino Deutschland: Fließendes Spi…

2.42:1

#000000

#354B77

needs 3.0:1 (large text)

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

h2 Trinocasino Registrierung: Wie geht es w…

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trinocasino Casino Deutschland: Nehmen o…

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Spielesammlung

2.01:1

#000000

#2E3F63

needs 3.0:1 (large text)

19px · mid-page · over background image/gradient

h3 Bonussystem

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Live-Dealer-Spiele in Deutschland

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Datenschutz der Nutzer

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Richten Sie Ihr Konto ein

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Finden Sie Ihr Konto auf

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Starten Sie das Gameplay

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Intelligente Benutzeroberfläche

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Zugänglicher Kundenservice

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Verantwortungsbewusstes Glücksspiel: We…

1.31:1

#000000

#1D1E41

needs 3.0:1 (large text)

19px · bottom of viewport

title Trinocasino Deutschland: Fair Play für …

1.10:1

#000000

#060D2A

needs 4.5:1 (normal text)

16px · top of page (header area)

p Trinocasino Deutschland ist ein neues, a…

1.92:1

#000000

#373B56

needs 4.5:1 (normal text)

16px · top of page (header area)

b Mindesteinzahlung erforderlich

2.28:1

#000000

#41475B

needs 3.0:1 (large text)

16px · top of page (header area)

td 20 EUR

2.28:1

#000000

#45465A

needs 4.5:1 (normal text)

16px · above the fold

b Einzahlungs- und Auszahlungsmöglichkeit…

1.39:1

#000000

#212441

needs 3.0:1 (large text)

16px · above the fold

td Visa, Mastercard, Neteller, Mifinity, Sk…

1.25:1

#000000

#171B39

needs 4.5:1 (normal text)

16px · above the fold

2 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 Trinocasino Deutschl…	2.42:1	3.0:1	#000000	#354B77	Fail
h2 Trinocasino beitrete…	3.10:1	3.0:1	#000000	#5B577C	Pass
h2 Trinocasino Registri…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h2 Trinocasino Casino D…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Spielesammlung	2.01:1	3.0:1	#000000	#2E3F63	Fail
h3 Bonussystem	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Live-Dealer-Spiele i…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Datenschutz der Nutz…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Richten Sie Ihr Kont…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Finden Sie Ihr Konto…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Starten Sie das Game…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Intelligente Benutze…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Zugänglicher Kunden…	1.31:1	3.0:1	#000000	#1D1E41	Fail
h3 Verantwortungsbewuss…	1.31:1	3.0:1	#000000	#1D1E41	Fail
title Trinocasino Deutschl…	1.10:1	4.5:1	#000000	#060D2A	Fail
p Trinocasino Deutschl…	1.92:1	4.5:1	#000000	#373B56	Fail
b Mindesteinzahlung er…	2.28:1	3.0:1	#000000	#41475B	Fail
td 20 EUR	2.28:1	4.5:1	#000000	#45465A	Fail
b Einzahlungs- und Aus…	1.39:1	3.0:1	#000000	#212441	Fail
td Visa, Mastercard, Ne…	1.25:1	4.5:1	#000000	#171B39	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.

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 Trinocasino Deutschland: Fließendes Spiel mit Top-Funktionen
H2 Trinocasino beitreten – Neues Glücksspielziel für Deutschland Spieler
H3 Spielesammlung
H3 Bonussystem
H3 Live-Dealer-Spiele in Deutschland
H3 Datenschutz der Nutzer
H2 Trinocasino Registrierung: Wie geht es weiter?
H3 Richten Sie Ihr Konto ein
H3 Finden Sie Ihr Konto auf
H3 Starten Sie das Gameplay
H2 Trinocasino Casino Deutschland: Nehmen oder brechen?
H3 Intelligente Benutzeroberfläche
H3 Zugänglicher Kundenservice
H3 Verantwortungsbewusstes Glücksspiel: Welche sind die wichtigsten Tools?

A+

Alt Text Quality

All 26 images OK

PASS

All 26 images OK

22 decorative image(s) correctly marked

4 image(s) with good alt text

26 images 4 good alt text 22 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

33 links, 0 buttons — all OK

PASS

33 links, 0 buttons — all OK

33 link(s) with descriptive text

33 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

33 links and buttons have descriptive text

Lighthouse Accessibility Audits

Score 93/100 — 4 failing, 20 passed

PASS

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.

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
2026 © trino-casino.com `div.c-footer > div.w-center > div.c-footer__row > div.c-footer__copyright-text`
Die Website trino-casino.com ist nicht mit der Marke verbunden. Alle Bilder und… `div.w-inner > div.c-footer > div.w-center > div.c-footer__copyright`

These are opportunities to improve the legibility of your content.

Best practices

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.

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
Jetzt spielen `div.w-center > div.w-section > div.w-btn > a.c-btn`
Jetzt spielen `div.w-center > div.w-section > div.w-btn > a.c-btn`
Jetzt spielen `div.w-center > div.w-section > div.w-btn > a.c-btn`
trino-casino.com `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
App `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Bonus `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Login `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Privacy Policy `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Responsible Gaming `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`
Support `div.w-center > ul.c-footer__list > li.c-footer__item > a.c-footer__link`

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Einzahlungsbonus Freispiele Bonusumsatz 1. Einzahlung 110% des Einzahlungsbetr… `div.w-inner > div.w-center > div.w-section > table`

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

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

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

●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

●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

●Touch targets have sufficient size and spacing.

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Identical links have the same purpose.

●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

○Deprecated ARIA roles were not used

○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

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

○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

○Buttons have an accessible name

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

○No element has a `[tabindex]` value greater than 0

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

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

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