Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 28 -1-on-focusable

FIX

0 positive, 28 -1-on-focusable

tabindex="-1" on naturally-focusable <a id="sm-17944582612053445-1">

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

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

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

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

tabindex="-1" on naturally-focusable <a id="sm-17944582612053445-3">

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

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

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

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

tabindex="-1" on naturally-focusable <a id="sm-17944582612053445-5">

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

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

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

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

tabindex="-1" on naturally-focusable <a id="sm-17944582612053445-7">

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

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

D

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.

D

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.

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

2 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

Search

Skip Link

Labeled Navigation 2 <nav> element(s)

Back to Top

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.

B

Landmark Structure

17 landmarks

REVIEW

17 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 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

C

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 Webdesign, das Ihr Unternehmen sichtbar …

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Was Sie von uns erwarten dürfen

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Erkennen Sie sich wieder?

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Unsere Leistungen

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Wie gut ist Ihre aktuelle Website?

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 In vier Schritten zu Ihrer neuen Website

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Diese Unternehmen vertrauen uns bereits

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Das sagen unsere Kunden auf Google

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Geprüft und zertifiziert

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Häufige Fragen

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h2 In Langen zu Hause, im ganzen Rhein-Main…

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

24px · bottom of viewport

h3 MCS Entrümpelung & Dienstleistung GmbH

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 BLK Haustechnik

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Elektro Avan

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 FITACON GmbH

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Otto Kuntz GmbH

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Leoci Consulting

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 „Unsere Website bringt kaum Anfragen.�…

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Klar geführt zur Anfrage

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

h3 „Bei Google findet uns niemand.“

1.11:1

#000000

on

#0F1113

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Webdesign, das Ihr U…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Was Sie von uns erwa…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Erkennen Sie sich wi…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Unsere Leistungen	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Wie gut ist Ihre akt…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 In vier Schritten zu…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Diese Unternehmen ve…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Das sagen unsere Kun…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Geprüft und zertifi…	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 Häufige Fragen	1.11:1	3.0:1	#000000	#0F1113	Fail
h2 In Langen zu Hause, …	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 MCS Entrümpelung & …	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 BLK Haustechnik	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 Elektro Avan	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 FITACON GmbH	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 Otto Kuntz GmbH	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 Leoci Consulting	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 „Unsere Website br…	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 Klar geführt zur An…	1.11:1	3.0:1	#000000	#0F1113	Fail
h3 „Bei Google findet…	1.11:1	3.0:1	#000000	#0F1113	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

57 headings

PASS

57 headings

Single H1 present

H1 Webdesign, das Ihr Unternehmen sichtbar macht.
H2 Was Sie von uns erwarten dürfen
H3 Schnell online
H3 Ein fester Ansprechpartner
H3 Rechtssicher von Anfang an
H3 Betreuung nach dem Launch
H2 Websites, die für unsere Kunden arbeiten
H3 MCS Entrümpelung & Dienstleistung GmbH
H3 BLK Haustechnik
H3 Elektro Avan
H3 FITACON GmbH
H3 Otto Kuntz GmbH
H3 Leoci Consulting
H2 Erkennen Sie sich wieder?
H3 „Unsere Website bringt kaum Anfragen.“
H3 Klar geführt zur Anfrage
H3 „Bei Google findet uns niemand.“
H3 Sichtbar bei Google, auch vor Ort
H3 „Auf dem Handy wirkt alles veraltet.“
H3 Mobil zuerst gedacht
H3 „Wir wissen nicht, ob rechtlich alles passt.“
H3 Rechtlich sauber umgesetzt
H2 Unsere Leistungen
H3 Webdesign & WordPress
H3 Onlineshops mit WooCommerce
H3 Website-Relaunch
H3 SEO & Local SEO
H3 KI-Suche & GEO
H3 Branding & Logodesign
H3 Wartung & Hosting
H2 Wie gut ist Ihre aktuelle Website?
H2 In vier Schritten zu Ihrer neuen Website
H3 Erstgespräch
H3 Konzept & Angebot
H3 Design & Umsetzung
H3 Launch & Betreuung
H2 Diese Unternehmen vertrauen uns bereits
H2 Das sagen unsere Kunden auf Google
H2 Der Unterschied, den Sie spüren
H3 Viele Agenturen
H3 UniQue Conception
H2 Geprüft und zertifiziert
H3 Geprüfter Webdesigner (OfG)
H3 Google Ads: Suchmaschinenwerbung
H3 Google Ads: Leistungsanalyse
H3 Google Analytics
H2 Häufige Fragen
H3 Was kostet eine Website bei UniQue Conception?
H3 Wie lange dauert es, bis meine Website online ist?
H3 Kann ich meine Website später selbst bearbeiten?
H3 Arbeiten Sie nur mit Unternehmen aus dem Rhein-Main-Gebiet?
H3 Ist meine Website DSGVO-konform und barrierefrei?
H3 Kümmern Sie sich auch darum, dass ich bei Google gefunden werde?
H3 Was passiert nach dem Launch?
H3 Welche Rechte habe ich an meiner Website?
H2 In Langen zu Hause, im ganzen Rhein-Main-Gebiet für Sie da
H2 Lassen Sie uns über Ihr Projekt Ihre Website Ihre Marke sprechen

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 80 images OK

PASS

All 80 images OK

80 image(s) with good alt text

80 images 80 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A

Link & Button Quality

147 links, 1 buttons — all OK

PASS

147 links, 1 buttons — all OK

16 link(s) open in new tab without warning

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

Got: https://wa.me/491727119601?text=Hallo%20Mehmet%2C%20ich%20interessiere%20mich…; https://calendar.app.google/J4ypw2C2796yBnh79; https://maps.google.com/?cid=11607783521632792773; https://unqc.de/wp-content/uploads/zertifikat-geprufter-webdesigner-ofg.jpg; https://unqc.de/wp-content/uploads/zertifikat-google-ads-suchmaschinenwerbung…; https://unqc.de/wp-content/uploads/zertifikat-google-ads-leistungsanalyse.pdf; https://unqc.de/wp-content/uploads/zertifikat-google-analytics.pdf; https://maps.google.com/?cid=11607783521632792773; https://maps.google.com/?cid=11607783521632792773; https://calendar.app.google/J4ypw2C2796yBnh79 (+6 more)

131 link(s) with descriptive text

147 links

0 empty

0 generic text

16 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/491727119601?text=Hallo%20…	Per WhatsApp schreiben (öffne…	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/J4ypw2C2796y…	Termin online buchen (öffnet …	new tab	Add '(opens in new tab)' to text
https://maps.google.com/?cid=11607783521…	Alle Bewertungen auf Google	new tab	Add '(opens in new tab)' to text
https://unqc.de/wp-content/uploads/zerti…	Zertifikat Geprüfter Webdesig…	new tab	Add '(opens in new tab)' to text
https://unqc.de/wp-content/uploads/zerti…	Google-Zertifizierung Google A…	new tab	Add '(opens in new tab)' to text
https://unqc.de/wp-content/uploads/zerti…	Google-Zertifizierung Google A…	new tab	Add '(opens in new tab)' to text
https://unqc.de/wp-content/uploads/zerti…	Google-Zertifizierung Google A…	new tab	Add '(opens in new tab)' to text
https://maps.google.com/?cid=11607783521…	Otto-Hahn-Straße 863225 Lange…	new tab	Add '(opens in new tab)' to text
https://maps.google.com/?cid=11607783521…	Route planen	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/J4ypw2C2796y…	Termin online buchen (öffnet …	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/unqc.de	Facebook-f	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/unqc.de/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@unqc_de	Tiktok	new tab	Add '(opens in new tab)' to text
https://de.linkedin.com/in/mehmet-sait-%…	Linkedin-in	new tab	Add '(opens in new tab)' to text
https://maps.google.com/?cid=11607783521…	Otto-Hahn-Straße 863225 Lange…	new tab	Add '(opens in new tab)' to text
https://calendar.app.google/J4ypw2C2796y…	Termin online buchen	new tab	Add '(opens in new tab)' to text

132 links and buttons have descriptive text

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

https://wa.me/491727119601?text=Hallo%20Mehmet%2C%20ich%20interessiere%20mich…; https://calendar.app.google/J4ypw2C2796yBnh79; https://maps.google.com/?cid=11607783521632792773; https://unqc.de/wp-content/uploads/zertifikat-geprufter-webdesigner-ofg.jpg; https://unqc.de/wp-content/uploads/zertifikat-google-ads-suchmaschinenwerbung…; https://unqc.de/wp-content/uploads/zertifikat-google-ads-leistungsanalyse.pdf; https://unqc.de/wp-content/uploads/zertifikat-google-analytics.pdf; https://maps.google.com/?cid=11607783521632792773; https://maps.google.com/?cid=11607783521632792773; https://calendar.app.google/J4ypw2C2796yBnh79 (+6 more)

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+

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+

Mobile-Readable Font Sizes

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

PASS

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

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

A

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Seite wurde nicht gefunden. - UniQue Conception ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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.

A+

Lighthouse Accessibility Audits

Score 99/100 — 2 failing, 28 passed

PASS

99

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.

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
Webdesign & WordPress `div.elementor-element > a.elementor-element > div.elementor-element > h3.elementor-heading-title`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Fragen? `div.kia > button.launcher`

○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

●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

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

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

●Buttons have an accessible name

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

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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 have a discernible name

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

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

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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