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 5 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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.

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

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

20 landmarks

REVIEW

20 landmarks

<main> landmark present

6 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) 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.

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

Mobile Keyboard & Autofill

Action

1/3 eligible field(s) missing autocomplete or inputmode

REVIEW

1/3 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="_R_aclf7ivb_-email">

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #f9444b ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 Wir machen Social Media zum

1.60:1

#000000

#2D3227

needs 3.0:1 (large text)

32px · bottom of viewport

h1 für Marken.

1.61:1

#000000

#303229

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Unsere

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Growth

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dein Weg zu uns.

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kundenstimmen

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 liegt in unserer DNA. Wachstum ist unser…

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Unser Team. Verstärkt durch ein ganzes …

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Die richtigen Antworten vorab.

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let’s Talk

1.61:1

#000000

#303229

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Social Strategy

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Content & Creative

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Creator & Influencer

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Social Channel Management

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Paid Social & Performance

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Data & Insights

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Lass uns dein Setup ansehen.

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unverbindliches Kennenlerngespräch

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Potenzialanalyse und Strategiegespräch

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Passgenaues Angebot

1.61:1

#000000

#303229

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Wir machen Social Me…	1.60:1	3.0:1	#000000	#2D3227	Fail
h1 für Marken.	1.61:1	3.0:1	#000000	#303229	Fail
h2 Unsere	1.61:1	3.0:1	#000000	#303229	Fail
h2 Growth	1.61:1	3.0:1	#000000	#303229	Fail
h2 Dein Weg zu uns.	1.61:1	3.0:1	#000000	#303229	Fail
h2 Kundenstimmen	1.61:1	3.0:1	#000000	#303229	Fail
h2 liegt in unserer DNA…	1.61:1	3.0:1	#000000	#303229	Fail
h2 Unser Team. Verstär…	1.61:1	3.0:1	#000000	#303229	Fail
h2 Die richtigen Antwor…	1.61:1	3.0:1	#000000	#303229	Fail
h2 Let’s Talk	1.61:1	3.0:1	#000000	#303229	Fail
h3 Social Strategy	1.61:1	3.0:1	#000000	#303229	Fail
h3 Content & Creative	1.61:1	3.0:1	#000000	#303229	Fail
h3 Creator & Influencer	1.61:1	3.0:1	#000000	#303229	Fail
h3 Social Channel Manag…	1.61:1	3.0:1	#000000	#303229	Fail
h3 Paid Social & Perfor…	1.61:1	3.0:1	#000000	#303229	Fail
h3 Data & Insights	1.61:1	3.0:1	#000000	#303229	Fail
h3 Lass uns dein Setup …	1.61:1	3.0:1	#000000	#303229	Fail
h3 Unverbindliches Kenn…	1.61:1	3.0:1	#000000	#303229	Fail
h3 Potenzialanalyse und…	1.61:1	3.0:1	#000000	#303229	Fail
h3 Passgenaues Angebot	1.61:1	3.0:1	#000000	#303229	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

29 headings

PASS

29 headings

Single H1 present

H1 Wir machen Social Media zum Wachstumssystem für Marken.
H2 Unsere Leistungen
H3 Social Strategy
H3 Content & Creative
H3 Creator & Influencer
H3 Social Channel Management
H3 Paid Social & Performance
H3 Data & Insights
H3 Lass uns dein Setup ansehen.
H2 Growth Cases
H2 Dein Weg zu uns.
H3 Unverbindliches Kennenlerngespräch
H3 Potenzialanalyse und Strategiegespräch
H3 Passgenaues Angebot
H2 Kundenstimmen
H2 Social Media liegt in unserer DNA. Wachstum ist unser Anspruch.
H3 Eingespieltes Spezialist:innen-Team
H3 Lisa Kalkkuhl
H3 Robert Rabe
H3 Sebastian Wagner
H3 Marco Schmid
H3 Fabian Weigele
H3 Ivonne Hofmeister
H3 Unser Office
H3 Eigenes In-House Ad-Studio
H3 Partnerschaften & Auszeichnungen
H2 Unser Team. Verstärkt durch ein ganzes Netzwerk.
H2 Die richtigen Antworten vorab.
H2 Let’s Talk

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 95 images OK

PASS

All 95 images OK

31 decorative image(s) correctly marked

64 image(s) with good alt text

95 images 64 good alt text 31 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#_R_aclf7ivb_-name	text	Name	for/id
#_R_aclf7ivb_-company	text	Unternehmen	for/id
#_R_aclf7ivb_-email	email	E-Mail	for/id
#_R_aclf7ivb_-goal	textarea	Dein Ziel	for/id
#_R_aclf7ivb_-privacy	checkbox		none

Link & Button Quality

47 links, 10 buttons — all OK

PASS

47 links, 10 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://www.instagram.com/teamhappygang/; https://www.linkedin.com/company/happygang/; https://www.xing.com/pages/happygang

44 link(s) with descriptive text

47 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/teamhappygang/	HAPPYGANG auf Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/happyga…	HAPPYGANG auf LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.xing.com/pages/happygang	HAPPYGANG auf Xing	new tab	Add '(opens in new tab)' to text

54 links and buttons have descriptive text

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

https://www.instagram.com/teamhappygang/; https://www.linkedin.com/company/happygang/; https://www.xing.com/pages/happygang

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

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

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, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

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

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

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 168 visible text node(s) render at >= 12 CSS pixels

PASS

All 168 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

1 mobile-depth signal(s) detected

PASS

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

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 30 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
Erfahre mehr `div.hg-container > div.hero-inner > div.hero-cta > a#hero-primary-cta`
Kostenlosen Audit anfragen `div.hg-container > div.cta-split > a.card > span.btn`
Let's talk `section#cases > div.hg-container > div.v4-case-grid-followup > a.btn`
Kennenlerngespräch vereinbaren `div.process-grid > div.process-intro > div.v4-process-actions > a.btn`
Name `div.contact-stage > form.form-card > div.field > label.field-label`
Unternehmen `div.contact-stage > form.form-card > div.field > label.field-label`
E-Mail `div.contact-stage > form.form-card > div.field > label.field-label`
Dein Ziel `div.contact-stage > form.form-card > div.field > label.field-label`
Ich stimme zu, dass meine Daten für die Sicherheitsprüfung verarbeitet werden. … `div.contact-stage > form.form-card > label.checkbox-field > span.checkbox-label`
Datenschutzerklärung `form.form-card > label.checkbox-field > span.checkbox-label > a`
Aktiviere zuerst die Einwilligung zur Sicherheitsprüfung. `div.contact-stage > form.form-card > div.turnstile-gate > p.turnstile-gate-status`

These are opportunities to improve the legibility of your content.

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
Social Media als Wachstumstreiber für Europas führenden Reiseanbieter `div.hg-container > div.v4-case-grid > article.v4-case-grid-item > a.v4-case-grid-card`
Datenbasierte Content Engine mit über 1.800 Assets pro Quartal `div.hg-container > div.v4-case-grid > article.v4-case-grid-item > a.v4-case-grid-card`
0 auf 13 Mio Follower - rein organisch! Vom eigenen Publisher zum strategischen… `div.hg-container > div.v4-case-grid > article.v4-case-grid-item > a.v4-case-grid-card`

○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

●Form elements have associated labels

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

●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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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

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