Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

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

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) 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

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

Mobile-Readable Font Sizes

Action

77% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

77% of visible text renders at >= 12 CSS px (7 below threshold)

7 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 11.5px ("Was wir bieten"); <span> 10.9px ("01"); <span> 10.9px ("02"); <span> 10.9px ("03"); <span> 10.9px ("04").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓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 Sauberkeit,

2.64:1

#000000

#4F5156

needs 3.0:1 (large text)

32px · above the fold

h1 die überzeugt.

1.88:1

#000000

#3B3B3C

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

h2 Unsere Dienstleistungen

2.24:1

#000000

#42474E

needs 3.0:1 (large text)

24px · above the fold

h2 Qualität, die man spürt.

1.41:1

#000000

#1F2835

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Haushaltsreinigung

2.36:1

#000000

#464A52

needs 3.0:1 (large text)

19px · mid-page

h3 Büroreinigung

2.23:1

#000000

#464649

needs 3.0:1 (large text)

19px · mid-page

h3 Baureinigung

1.83:1

#000000

#333A43

needs 3.0:1 (large text)

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

h3 Tiefenreinigung

1.46:1

#000000

#232A36

needs 3.0:1 (large text)

19px · mid-page

h3 Fensterreinigung

1.43:1

#000000

#212935

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Umzugsreinigung

1.41:1

#000000

#1F2834

needs 3.0:1 (large text)

19px · bottom of viewport

title Clean Space – Professionelle Reinigung

1.22:1

#000000

#0F1C2B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Clean Space

1.22:1

#000000

#0F1C2B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Startseite

1.79:1

#000000

#313942

needs 4.5:1 (normal text)

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

a Dienstleistungen

2.44:1

#000000

#494C51

needs 4.5:1 (normal text)

16px · top of page (header area)

a Kontakt

2.47:1

#000000

#4A4D52

needs 4.5:1 (normal text)

16px · above the fold

p Professionelle Reinigungsdienste

2.59:1

#000000

#4D5055

needs 4.5:1 (normal text)

16px · above the fold

p Maßgeschneiderte Reinigungslösungen f�…

2.81:1

#000000

#535559

needs 4.5:1 (normal text)

16px · above the fold

a Kontakt aufnehmen →

2.81:1

#000000

#535559

needs 4.5:1 (normal text)

16px · above the fold

p Was wir bieten

2.56:1

#000000

#4C4F55

needs 4.5:1 (normal text)

16px · above the fold

p Gründliche Reinigung Ihrer Wohnräume �…

2.27:1

#000000

#42484E

needs 4.5:1 (normal text)

16px · mid-page

3 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 Sauberkeit,	2.64:1	3.0:1	#000000	#4F5156	Fail
h1 die überzeugt.	1.88:1	3.0:1	#000000	#3B3B3C	Fail
h2 Unsere Dienstleistun…	2.24:1	3.0:1	#000000	#42474E	Fail
h2 Qualität, die man s…	1.41:1	3.0:1	#000000	#1F2835	Fail
h3 Haushaltsreinigung	2.36:1	3.0:1	#000000	#464A52	Fail
h3 Büroreinigung	2.23:1	3.0:1	#000000	#464649	Fail
h3 Baureinigung	1.83:1	3.0:1	#000000	#333A43	Fail
h3 Tiefenreinigung	1.46:1	3.0:1	#000000	#232A36	Fail
h3 Fensterreinigung	1.43:1	3.0:1	#000000	#212935	Fail
h3 Umzugsreinigung	1.41:1	3.0:1	#000000	#1F2834	Fail
title Clean Space – Prof…	1.22:1	4.5:1	#000000	#0F1C2B	Fail
span Clean Space	1.22:1	4.5:1	#000000	#0F1C2B	Fail
a Startseite	1.79:1	4.5:1	#000000	#313942	Fail
a Dienstleistungen	2.44:1	4.5:1	#000000	#494C51	Fail
a Kontakt	2.47:1	4.5:1	#000000	#4A4D52	Fail
p Professionelle Reini…	2.59:1	4.5:1	#000000	#4D5055	Fail
p Maßgeschneiderte Re…	2.81:1	4.5:1	#000000	#535559	Fail
a Kontakt aufnehmen �…	2.81:1	4.5:1	#000000	#535559	Fail
p Was wir bieten	2.56:1	4.5:1	#000000	#4C4F55	Fail
p Gründliche Reinigun…	2.27:1	4.5:1	#000000	#42484E	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

9 headings

PASS

9 headings

Single H1 present

H1 Sauberkeit,die überzeugt.
H2 Unsere Dienstleistungen
H3 Haushaltsreinigung
H3 Büroreinigung
H3 Baureinigung
H3 Tiefenreinigung
H3 Fensterreinigung
H3 Umzugsreinigung
H2 Qualität, die man spürt.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

1 of 14 images have issues

PASS

1 of 14 images have issues

1 image(s) with generic alt text

13 image(s) with good alt text

14 images 13 good alt text 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

7 links, 0 buttons — all OK

PASS

7 links, 0 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://wa.me/+41793719626; https://www.instagram.com/cleanspace1818

5 link(s) with descriptive text

7 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/+41793719626	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/cleanspace1818	Instagram	new tab	Add '(opens in new tab)' to text

5 links and buttons have descriptive text

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

https://wa.me/+41793719626; https://www.instagram.com/cleanspace1818

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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

Score 91/100 — 1 failing, 10 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 Clean Space · Alle Rechte vorbehalten `body > footer > p`

These are opportunities to improve the legibility of your content.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

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

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

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

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