Accessibility

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

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: white

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.

B

Landmark Structure

21 landmarks

REVIEW

21 landmarks

<main> landmark present

No <nav> landmark found

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

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Die Seite ist leider nicht vorhanden ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Knuddels Chat: Freunde finden

No 192x192 icon

A 192px icon is required for PWA installation.

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Knuddels Chat: Freunde finden ✓192×192 icon ✗512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Knuddels Chat: Freunde finden Display Mode standalone Theme Color #5d4265 Background Color #5d4265 Icons 1 icon(s)

B

Lighthouse Accessibility Audits

Score 89/100 — 2 failing, 24 passed

REVIEW

89

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

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.mx-large > section.flex > div.flex > img.w-[24px] `div.mx-large > section.flex > div.flex > img.w-[24px]`

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.

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`

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-*]` attributes match their 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

●Buttons have an accessible name

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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 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

○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

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

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

A+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

H1 Unser Chat bringt Menschen zusammen.
H2 Dein Flirt-Chat Du willst jemanden kennenlernen?
H2 Deine Online-Spiele Einfach online mit deinen Freunden spielen.
H2 Schon überzeugt? Jetzt den Knuddels-Chat ausprobieren!
H2 Dein kostenloser Chat Freunde fürs Leben finden.
H2 DEINE THEMEN Über Themen chatten, die dich bewegen.
H2 Werde jetzt Teil der Community. 🌟
H2 Häufige Fragen zum Knuddels Chat
H2 Was versteht man unter einem Chat? 🤔
H2 Wie funktioniert die Knuddels Chat Community? 🎯
H2 Kann ich bei Knuddels kostenlos chatten? 💰
H2 Gibt es auch eine Chat-App von Knuddels? 📲
H2 Ist Knuddels ein Live-Chat? ⚡
H2 Ist Knuddels ein cooler Chat? 😎
H2 Wie kann ich bei Knuddels neue Freunde finden? 👯
H2 Kann ich bei Knuddels chatten und online spielen? 🎯
H2 Ist der Knuddels Chatroom anonym? 🕶️
H2 Ist Knuddels ein Chatroom ohne Anmeldung? 📝
H2 Ist Knuddels der bekannte Chatroom aus den 2000ern? 📅
H2 Ist Knuddels ein Deutscher Chat? 🇩🇪
H2 Wie unterscheidet sich Knuddels von anderen Chats? 🤔
H2 Kann man auf Knuddels mit anderen Menschen Nachrichten austauschen und Unterhaltungen führen? 💌
H2 Ist Knuddels eine Plattform, um mit Teammitgliedern am Arbeitsplatz zusammenzuarbeiten? 💼
H2 Ist Knuddels ein Sex Chat? 🍆
H2 Werde jetzt Teil der Community!

A+

Heading Text Quality

All 25 heading(s) have substantive, well-formed text

PASS

All 25 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A

Alt Text Quality

1 of 48 images have issues

PASS

1 of 48 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

44 decorative image(s) correctly marked

3 image(s) with good alt text

48 images 3 good alt text 44 decorative 1 missing

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A

Link & Button Quality

127 links, 22 buttons — all OK

PASS

127 links, 22 buttons — all OK

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /agb; /datenschutz; https://www.hcaptcha.com/privacy; https://www.hcaptcha.com/terms; https://play.google.com/store/apps/details?id=com.knuddels.android; https://apps.apple.com/de/app/knuddels-chat-freunde-finden/id369409839; https://apps.apple.com/de/app/knuddels-chat-freunde-finden/id369409839?ign-mp…; https://play.google.com/store/apps/details?id=com.knuddels.android&referrer=u…

119 link(s) with descriptive text

127 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/agb	AGB	new tab	Add '(opens in new tab)' to text
/datenschutz	Datenschutzerklärung	new tab	Add '(opens in new tab)' to text
https://www.hcaptcha.com/privacy	Datenschutzerklärung	new tab	Add '(opens in new tab)' to text
https://www.hcaptcha.com/terms	AGB	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Android	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/de/app/knuddels-c…	iOS	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/de/app/knuddels-c…	Für iOS Herunterladen	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Für Android Herunterladen	new tab	Add '(opens in new tab)' to text

141 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/agb; /datenschutz; https://www.hcaptcha.com/privacy; https://www.hcaptcha.com/terms; https://play.google.com/store/apps/details?id=com.knuddels.android; https://apps.apple.com/de/app/knuddels-chat-freunde-finden/id369409839; https://apps.apple.com/de/app/knuddels-chat-freunde-finden/id369409839?ign-mp…; https://play.google.com/store/apps/details?id=com.knuddels.android&referrer=u…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "de"

PASS

Lang attribute set to "de"

<html lang="de"> is set and valid

Got: de

A

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

A+

Iframe Accessibility

All 4 iframe(s) have descriptive titles

PASS

All 4 iframe(s) have descriptive titles

All 4 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 317 visible text node(s) render at >= 12 CSS pixels

PASS

All 317 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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 Unser Chat bringt Me…	18.15:1	3.0:1	#000000	#EFEEEF	Pass
h2 Häufige Fragen zum …	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Was versteht man unt…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Wie funktioniert die…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Kann ich bei Knuddel…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Gibt es auch eine Ch…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels ein Liv…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels ein coo…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Wie kann ich bei Knu…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Kann ich bei Knuddel…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist der Knuddels Cha…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels ein Cha…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels der bek…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels ein Deu…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Wie unterscheidet si…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Kann man auf Knuddel…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels eine Pl…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
h2 Ist Knuddels ein Sex…	19.43:1	3.0:1	#000000	#F6F6F6	Pass
title Knuddels Chat - Im C…	18.59:1	4.5:1	#000000	#F1F1F1	Pass
span Akzeptieren & schlie…	18.43:1	4.5:1	#000000	#F0F0F0	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.