Accessibility

D

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

F

Heading Hierarchy

Action

50 headings, 8 skip(s)

FIX

50 headings, 8 skip(s)

Multiple H1 headings (6 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Die Freiheit das zu tun, was Du schon immer wolltest.
H4 Willkommen beim Space der unbegrenzten Möglichkeiten skipped
H1 Neue Wege erkunden, ohne Wenn und Aber. duplicate H1
H4 Willkommen beim Space der neuen Wege skipped
H1 An die Grenze des Machbaren, und noch ein bisschen weiter. duplicate H1
H4 Willkommen beim Space der keine Grenzen kennt skipped
H3 1 GB Speicher
H3 2 Datenbanken
H3 Ticket-Support
H3 (empty)
H3 PHP 8, MySQL / MariaDB, PostgreSQLSQL-Datenbanken
H3 Zugriff mit FTP
H3 Werbefreie Webseiten
H3 8 GB Speicher
H3 16 Datenbanken
H3 PHP-Sockets für WP & Co
H3 live access Dateiverwaltung
H3 Höhere Bandbreite
H3 Kein Inaktivitätslimit & MindestlaufzeitKeine Mindestlaufzeit
H3 HTTPS / SSL für alle Seiten
H3 50 GB Speicher
H3 20 Datenbanken
H3 Direkter Zugriff via SSH
H3 10GB E-Mail viaE-Mail, IMAP & Webmail
H3 Maximale Serverleistung
H3 Domains zu günstigen Konditionen
H3 Cronjobs
H4 Kompetenter Support
H4 Umfangreiches Backend
H4 Externe Serverbindungen
H4 Verschlüsselte Verbindungen
H4 10GB E-Mail
H4 Domains zu günstigen Konditionen
H6 Jetzt alle Angebote im aktuellen bplaced Katalog vergleichen! skipped
H1 Handverlesene Domains duplicate H1
H2 umfassender Service inklusive
H4 (empty)
H4 Hilfe
H1 Anmelden duplicate H1
H1 Bestellen duplicate H1
H2 Anmelden
H2 Bestellen
H2 Hosting
H4 Hosting skipped
H2 Login
H4 Login skipped
H2 Sicherheit
H4 Sicherheit skipped
H3 Eine E-Mail mit einem Passwort haben wir an versandt!
H4 Oder gleich direkt mit der bplaced App:

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-ixgp3n

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://bplaced.net/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://bplaced.net/manifest.json

Manifest contains invalid JSON.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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

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

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)

0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

D

Lighthouse Accessibility Audits

Action

Score 50/100 — 8 failing, 7 passed

FIX

50

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.

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#nav_main_top > div.row > div.col-xs-2 > button.offcanvas-menu `div#nav_main_top > div.row > div.col-xs-2 > button.offcanvas-menu`

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
deutsch (Du) deutsch (Sie) english `div.row > div.col-xs-10 > form#i18n > select.selection`

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.row > div.col-xs-10 > div.tablestyle > a.cellstyle `div.row > div.col-xs-10 > div.tablestyle > a.cellstyle`
div.center_listing > div.main > div.hub_bullets > a#release_1 `div.center_listing > div.main > div.hub_bullets > a#release_1`
div.center_listing > div.main > div.hub_bullets > a#release_2 `div.center_listing > div.main > div.hub_bullets > a#release_2`
div.center_listing > div.main > div.hub_bullets > a#release_3 `div.center_listing > div.main > div.hub_bullets > a#release_3`
div.center_listing > div.main > div.tablestyle > a#arrowno_1 `div.center_listing > div.main > div.tablestyle > a#arrowno_1`
div.center_listing > div.main > div.tablestyle > a#arrowno_3 `div.center_listing > div.main > div.tablestyle > a#arrowno_3`
div.row > div.col-lg-12 > div > a `div.row > div.col-lg-12 > div > a`

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
PHP-Sockets für WP & Co `div.main_col_bg_side > div.main_col_bg > div.center_listing_main > h3.bigtext14`
live access Dateiverwaltung `div.main_col_bg_side > div.main_col_bg > div.center_listing_main > h3.bigtext14`
Höhere Bandbreite `div.main_col_bg_side > div.main_col_bg > div.center_listing_details > h3.mediumtext`
Keine Mindestlaufzeit `div.main_col_bg > div.center_listing_details > h3.mediumtext > span.visible-xs-inline`
HTTPS / SSL für alle Seiten `div.main_col_bg_side > div.main_col_bg > div.center_listing_details > h3.mediumtext`
EUR `div.main_col_bg > div.center_listing_fees > div > div.bside`
3. `div.main_col_bg > div.center_listing_fees > div > div.bside`
IMPRESSUM `div.main > div.row > div.col-sm-4 > a.mediumtext`
AGB `div.main > div.row > div.col-sm-4 > a.mediumtext`
VERTRÄGE KÜNDIGEN `div.main > div.row > div.col-sm-4 > a.mediumtext`
DATENSCHUTZ `div.main > div.row > div.col-sm-4 > a.mediumtext`

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
Willkommen beim Space der unbegrenzten Möglichkeiten `div.row > div.col-sm-12 > div.center_init_text > h4.boldtext`
Willkommen beim Space der neuen Wege `div.row > div.col-sm-12 > div.center_init_text > h4.boldtext`
Willkommen beim Space der keine Grenzen kennt `div.row > div.col-sm-12 > div.center_init_text > h4.boldtext`
Jetzt alle Angebote im aktuellen bplaced Katalog vergleichen! `div.main_container_cat > div.row > div.col-xs-12 > h6.whitetext`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html#main `html#main`

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#main `html#main`

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○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

○Elements use only permitted ARIA attributes

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

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

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

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

C

Form Accessibility

Action

4 of 4 controls have issues

REVIEW

4 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" name="credentials">

3 control(s) rely on placeholder only

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

Got: <input type="text" name="domain">; <input type="text" name="email">; <input type="text" name="code">

4 controls

0 labeled

3 placeholder only

1 unlabeled

Control	Type	Label	Method
domain	text	(meinewunschdomain.com)	placeholder only
email	text	(E-Mail)	placeholder only
code	text	(Code eingeben)	placeholder only
credentials	text	(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

C

Link & Button Quality

Action

18 issue(s) across 76 links and 13 buttons

REVIEW

18 issue(s) across 76 links and 13 buttons

17 link(s) with no accessible text

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

Got: https://www.bplaced.net/; https://www.bplaced.net/; ./#freestyle; ./#pro; ./#max; ./#freestyle; ./#max; https://my.bplaced.net/tour; https://www.linkedin.com/company/bplaced/; https://x.com/bplaced (+7 more)

1 button(s) with no accessible text

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

Got: button.offcanvas-menu (#54 on page)

59 link(s) with descriptive text

76 links

17 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.bplaced.net/	(empty)	empty	Add link text or aria-label
https://www.bplaced.net/	(empty)	empty	Add link text or aria-label
./#freestyle	(empty)	empty	Add link text or aria-label
./#pro	(empty)	empty	Add link text or aria-label
./#max	(empty)	empty	Add link text or aria-label
./#freestyle	(empty)	empty	Add link text or aria-label
./#max	(empty)	empty	Add link text or aria-label
https://my.bplaced.net/tour	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/bplaced…	(empty)	empty	Add link text or aria-label
https://x.com/bplaced	(empty)	empty	Add link text or aria-label
https://inside.bplaced.net	(empty)	empty	Add link text or aria-label
https://inside.bplaced.net/bplaced-app/	(empty)	empty	Add link text or aria-label
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
https://appgallery.huawei.com/#/app/C102…	(empty)	empty	Add link text or aria-label
./	(empty)	empty	Add link text or aria-label
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
https://appgallery.huawei.com/#/app/C102…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

71 links and buttons have descriptive text

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

https://www.bplaced.net/; https://www.bplaced.net/; ./#freestyle; ./#pro; ./#max; ./#freestyle; ./#max; https://my.bplaced.net/tour; https://www.linkedin.com/company/bplaced/; https://x.com/bplaced (+7 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

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

button.offcanvas-menu (#54 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

B

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Die Freiheit das zu …	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 was Du schon immer w…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 Neue Wege erkunden,	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 ohne Wenn und Aber.	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 An die Grenze des Ma…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 und noch ein bissche…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 Anmelden	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h1 Bestellen	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h2 umfassender Service …	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h2 Anmelden	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h2 Bestellen	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h2 Hosting	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h2 Login	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h2 Sicherheit	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h3 1 GB Speicher	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h3 2 Datenbanken	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h3 Ticket-Support	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h3 PHP 8,	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h3 Zugriff mit FTP	5.83:1	3.0:1	#000000	#0F8ED3	Pass
h3 Werbefreie Webseiten	5.83:1	3.0:1	#000000	#0F8ED3	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.