Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 2 REVIEW 10 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

Alt Text Quality

Action

8 of 40 images have issues

FIX

8 of 40 images have issues

8 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

An image inside a link with no alt creates an empty link.

18 decorative image(s) correctly marked

14 image(s) with good alt text

40 images 14 good alt text 18 decorative 8 missing

Issue	Count
missing	8 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Form Accessibility

Action

6 of 6 controls have issues

FIX

6 of 6 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" id="search_submit">; <input type="submit">

4 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="s" id="s">; <textarea name="comment" id="comment">; <input type="text" name="author" id="author">; <input type="text" name="email" id="email">

6 controls

0 labeled

4 placeholder only

2 unlabeled

Control	Type	Label	Method
#s	text	(Spiele suchen...)	placeholder only
#comment	textarea	(einen Kommentar hinterlassen...)	placeholder only
#author	text	(Name)	placeholder only
#email	text	(e-mail)	placeholder only
#search_submit	submit	(none)	none
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

46 issue(s) across 153 links and 12 buttons

FIX

46 issue(s) across 153 links and 12 buttons

36 link(s) with no accessible text

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

Got: #; #; #; /; https://bookofra-play.com/bgo-casino-verlost-e-2-000-als-urlaubsgutschein/; https://bookofra-play.com/casino-uebersicht/; #; #; #; a (#797 on page) (+26 more)

3 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/wp-content/uploads/2020/02/1_Screen_800x6001.jpg"]; a[href="/wp-content/uploads/2020/02/2_Screen_800x6001.jpg"]; a[href="/wp-content/uploads/2020/02/3_Screen_800x6001.jpg"]

10 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: input[type="submit"]#search_submit; button.box_faq__btn (#495 on page); button.box_faq__btn (#503 on page); button.box_faq__btn (#520 on page); button.box_faq__btn (#529 on page); button.box_faq__btn (#539 on page); button.box_faq__btn (#548 on page); button.box_faq__btn (#557 on page); button.box_faq__btn (#566 on page); button.box_faq__btn (#576 on page)

114 link(s) with descriptive text

153 links

36 empty

0 generic text

0 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/wp-content/uploads/2020/02/1_Screen_800…	<img src="/wp-content/uploads/…	img no alt	Add alt attribute to the image
/wp-content/uploads/2020/02/2_Screen_800…	<img src="/wp-content/uploads/…	img no alt	Add alt attribute to the image
/wp-content/uploads/2020/02/3_Screen_800…	<img src="/wp-content/uploads/…	img no alt	Add alt attribute to the image
https://bookofra-play.com/bgo-casino-ver…	(empty)	empty	Add link text or aria-label
https://bookofra-play.com/casino-uebersi…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<input>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

116 links and buttons have descriptive text

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

#; #; #; /; https://bookofra-play.com/bgo-casino-verlost-e-2-000-als-urlaubsgutschein/; https://bookofra-play.com/casino-uebersicht/; #; #; #; a (#797 on page) (+26 more)

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/wp-content/uploads/2020/02/1_Screen_800x6001.jpg"]; a[href="/wp-content/uploads/2020/02/2_Screen_800x6001.jpg"]; a[href="/wp-content/uploads/2020/02/3_Screen_800x6001.jpg"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

input[type="submit"]#search_submit; button.box_faq__btn (#495 on page); button.box_faq__btn (#503 on page); button.box_faq__btn (#520 on page); button.box_faq__btn (#529 on page); button.box_faq__btn (#539 on page); button.box_faq__btn (#548 on page); button.box_faq__btn (#557 on page); button.box_faq__btn (#566 on page); button.box_faq__btn (#576 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

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

Lighthouse Accessibility Audits

Action

Score 63/100 — 9 failing, 15 passed

FIX

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
INHALTSVERZEICHNIS `div.content > div#js-move-contents-out > div.c-tb-content > div.c-tb-content__title`

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`
div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > button.box_faq__btn`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.one_item > div.img > a.fancybox-media > img.lazy `div.one_item > div.img > a.fancybox-media > img.lazy`
div.one_item > div.img > a.fancybox-media > img.lazy `div.one_item > div.img > a.fancybox-media > img.lazy`
div.one_item > div.img > a.fancybox-media > img.lazy `div.one_item > div.img > a.fancybox-media > img.lazy`
div.one_box > div.cell_detail > div.logo > img.data-original `div.one_box > div.cell_detail > div.logo > img.data-original`
div.one_box > div.cell_detail > div.logo > img.data-original `div.one_box > div.cell_detail > div.logo > img.data-original`
div.one_box > div.cell_detail > div.logo > img.data-original `div.one_box > div.cell_detail > div.logo > img.data-original`
div.one_box > div.cell_detail > div.logo > img.data-original `div.one_box > div.cell_detail > div.logo > img.data-original`
div.one_box > div.cell_detail > div.logo > img.data-original `div.one_box > div.cell_detail > div.logo > img.data-original`

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.box_iframe_1 > div.box_game > div.game_container > a.home `div.box_iframe_1 > div.box_game > div.game_container > a.home`
div.owl-item > div.one_item > div.img > a.fancybox-media `div.owl-item > div.one_item > div.img > a.fancybox-media`
div.owl-item > div.one_item > div.img > a.fancybox-media `div.owl-item > div.one_item > div.img > a.fancybox-media`
div.owl-item > div.one_item > div.img > a.fancybox-media `div.owl-item > div.one_item > div.img > a.fancybox-media`
div.c-blog-box > div.c-blog-box__item > div.c-one-blog > a.c-one-blog__img `div.c-blog-box > div.c-blog-box__item > div.c-one-blog > a.c-one-blog__img`
div.c-blog-box > div.c-blog-box__item > div.c-one-blog > a.c-one-blog__img `div.c-blog-box > div.c-blog-box__item > div.c-one-blog > a.c-one-blog__img`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.foot_comment > div.one_it > div.ssk-group > a.ssk `div.foot_comment > div.one_it > div.ssk-group > a.ssk`
div.textwidget > div.one_box > div.cell_detail > a.btn_paly `div.textwidget > div.one_box > div.cell_detail > a.btn_paly`
div.textwidget > div.one_box > div.cell_detail > a.btn_paly `div.textwidget > div.one_box > div.cell_detail > a.btn_paly`
div.textwidget > div.one_box > div.cell_detail > a.btn_paly `div.textwidget > div.one_box > div.cell_detail > a.btn_paly`
div.textwidget > div.one_box > div.cell_detail > a.btn_paly `div.textwidget > div.one_box > div.cell_detail > a.btn_paly`
div.textwidget > div.one_box > div.cell_detail > a.btn_paly `div.textwidget > div.one_box > div.cell_detail > a.btn_paly`

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.

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
Wo kann man Book of Ra Online spielen? `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > h4.box_faq__title`
Bietet Book of Ra einen Jackpot? `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > h4.box_faq__title`
Kann man Book of Ra in Deutschland um Echtgeld spielen? `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > h4.box_faq__title`
Worin unterscheidet sich Book of Ra Deluxe vom Klassiker? `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > h4.box_faq__title`
Kann ich Book of Ra Online Software zum Herunterladen finden? `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > h4.box_faq__title`
div.input_group > div.section_1 > div.col_60 > input#author `div.input_group > div.section_1 > div.col_60 > input#author`
div.input_group > div.section_2 > div.col_60 > input#email `div.input_group > div.section_2 > div.col_60 > input#email`
Gor `div.container_comments > div.comment > div.head_comment > div.one_it`
Jun 28, 2023 `div.container_comments > div.comment > div.head_comment > div.one_it`
cat333 `div.container_comments > div.comment > div.head_comment > div.one_it`
Apr 17, 2023 `div.container_comments > div.comment > div.head_comment > div.one_it`
Mint `div.container_comments > div.comment > div.head_comment > div.one_it`
Mrz 15, 2023 `div.container_comments > div.comment > div.head_comment > div.one_it`
Ruth `div.container_comments > div.comment > div.head_comment > div.one_it`
Feb 11, 2023 `div.container_comments > div.comment > div.head_comment > div.one_it`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wo kann man Book of Ra Online spielen? `div.box_faq__item > div.box_faq__item-inner > div.box_faq__head > h4.box_faq__title`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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]` values are valid

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

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

●Input buttons have discernible text.

●Form elements have associated labels

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

○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

○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 a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○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

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

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

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 | bookofra-play.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Book Of Ra Spielen Ohne Anmeldung

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Wie kann man im Book of Ra Online viel g…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Um einen großen Gewinn im Spiel zu erzi…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Casinoboni für Book of Ra

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ein faszinierendes Sujet in perfekter Sl…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Gute Kenntnis der Spielregeln ist das ha…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Gewinnversprechende Symbole von Book of …

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Die Book of Ra-Spielreihe: mehrere Varia…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Book of ra online spielen

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Book of Ra Slot: Scatter & Wild Symbole

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Gewinnbringende Freispiele für die Eins…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Rund um die Hauptbegriffe von Book of Ra

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tipps & Tricks

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Book of Ra Mobile Version

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Die Varianten von Book of Ra

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Book of Ra FAQ

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Was man bei den Einsätzen beachten muss…

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Eventuelle Gewinne

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Gamble-Funktion: Das Kartenrisiko

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Die Autoplay-Funktion

1.10:1

#000000

#1E0717

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Book Of Ra Spielen O…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Wie kann man im Book…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Um einen großen Gew…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Casinoboni für Book…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Ein faszinierendes S…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Gute Kenntnis der Sp…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Gewinnversprechende …	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Die Book of Ra-Spiel…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Book of ra online sp…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Book of Ra Slot: Sca…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Gewinnbringende Frei…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Rund um die Hauptbeg…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Tipps & Tricks	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Book of Ra Mobile Ve…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Die Varianten von Bo…	1.10:1	3.0:1	#000000	#1E0717	Fail
h2 Book of Ra FAQ	1.10:1	3.0:1	#000000	#1E0717	Fail
h3 Was man bei den Eins…	1.10:1	3.0:1	#000000	#1E0717	Fail
h3 Eventuelle Gewinne	1.10:1	3.0:1	#000000	#1E0717	Fail
h3 Gamble-Funktion: Das…	1.10:1	3.0:1	#000000	#1E0717	Fail
h3 Die Autoplay-Funktio…	1.10:1	3.0:1	#000000	#1E0717	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.

Heading Hierarchy

38 headings, 1 skip(s)

PASS

38 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Book Of Ra Spielen Ohne Anmeldung
H2 Wie kann man im Book of Ra Online viel gewinnen?
H2 Um einen großen Gewinn im Spiel zu erzielen, kann man die angeführten Tipps befolgen:
H2 Casinoboni für Book of Ra
H2 Ein faszinierendes Sujet in perfekter Slot-Ausführung
H2 Gute Kenntnis der Spielregeln ist das halbe Werk
H2 Gewinnversprechende Symbole von Book of Ra Slot bestimmen den Spielverlauf
H2 Die Book of Ra-Spielreihe: mehrere Varianten – gemeinsamer Charme
H2 Book of ra online spielen
H2 Book of Ra Slot: Scatter & Wild Symbole
H2 Gewinnbringende Freispiele für die Einsteiger
H2 Rund um die Hauptbegriffe von Book of Ra
H3 Was man bei den Einsätzen beachten muss?
H3 Eventuelle Gewinne
H3 Gamble-Funktion: Das Kartenrisiko
H3 Die Autoplay-Funktion
H3 Auszahlungsquote
H3 Volatilität
H3 RTP Wert
H2 Tipps & Tricks
H3 Sich anmelden & die Testversion spielen
H3 Das Budget festlegen
H3 Das Bonusprogramm nutzen
H2 Book of Ra Mobile Version
H2 Die Varianten von Book of Ra
H3 Book of Ra Deluxe
H3 Book of Ra Magic
H3 Book of Ra – Temple of Gold
H2 Book of Ra FAQ
H4 Wo kann man Book of Ra Online spielen? skipped
H4 Welche Varianten von Book of Ra gibt es?
H4 Bietet Book of Ra einen Jackpot?
H4 Gibt es Spielautomaten, die dem Book of Ra Slot ähneln?
H4 Kann man Book of Ra in Deutschland um Echtgeld spielen?
H4 Kann man Book of Ra kostenlos auf einem Mobilgerät spielen?
H4 Worin unterscheidet sich Book of Ra Deluxe vom Klassiker?
H4 Kann man den Klassiker Book of Ra offline kostenlos spielen ohne Anmeldung?
H4 Kann ich Book of Ra Online Software zum Herunterladen finden?

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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