Skip to content
https://Webnetz.de

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
6
REVIEW
7
PASS
11
INFO
0
Checks
24
11 PASS 7 REVIEW 6 FIX
F
Alt Text Quality
Action
14 of 135 images have issues
FIX
14 of 135 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
14 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
107 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
135 images 14 good alt text 107 decorative 14 missing
IssueCount
missing14 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
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'>.
Critical::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
4 navigation landmark(s) detected
Info::
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 4 <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
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV "Hauptnavigation" MAIN CONTENTINFO footer

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
Form Accessibility
6 of 6 controls have issues
REVIEW
6 of 6 controls have issues
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">; <input type="text" name="q">; <input type="text" name="q">; <input type="text">; <input type="text">
6 controls
0 labeled
6 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(E-Mail)placeholder only
inputtext(E-Mail)placeholder only
qtext(Suchbegriff eingeben)placeholder only
qtext(Suchbegriff)placeholder only
inputtext(E-Mail)placeholder only
inputtext(E-Mail)placeholder only

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

<input type="text">; <input type="text">; <input type="text" name="q">; <input type="text" name="q">; <input type="text">; <input type="text">

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

B
Iframe Accessibility
3/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://web.cmp.usercentrics.eu/cdcs/v/1.0.0/index.html")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://6237475.fls.doubleclick.net/activityi;src=6237475;type=gener0;cat=web-n…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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
BLOG div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > span.mb-4
WEBINARE div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > span.mb-4
Jobs div.relative > div.headlines > div.pretitle > span.pretitle--text
Alle offenen Stellen section#lieljzzn > div.mx-auto > a.button > span
Akzeptieren footer#uc-cmp-footer > div.buttons > div.buttons-row > button#accept

These are opportunities to improve the legibility of your content.

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
a.flex > div.aspect-[3/2] > div.@container > img.absolute a.flex > div.aspect-[3/2] > div.@container > img.absolute
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img
a.flex > div.aspect-[3/2] > div.@container > img.absolute a.flex > div.aspect-[3/2] > div.@container > img.absolute
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img
div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img div.@container > div.absolute > div.tile-hosts > img.tile-hosts-img

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jetzt Artikel lesen div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > button.button
Jetzt anmelden div#swiper-wrapper-410d0a491032bdbe96 > div.swiper-slide > a.flex > button.button

These items highlight common accessibility best practices.

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
Jetzt kontaktieren div.relative > div.flex > div > a.button
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●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
○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
○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
○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.
○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
39 headings
PASS
39 headings
Info::
Single H1 present
  • H1 besser digital Wir entwickeln, gestalten & vermarkten Ihr Online-Geschäft
  • H2 Wir sind Experten für Ihren digitalen Durchbruch
  • H3 Strategie & Beratung
  • H3 Online-Marketing
  • H3 Content & Kampagnen
  • H3 Design & Video
  • H3 Web-Entwicklung
  • H2 Wir entwerfen digitale Lösungen und zielgenaue Kommunikation.
  • H2 Immer das passende Team für Ihr Projekt.
  • H2 Das sagen unsere Kunden
  • H2 Neues aus der digitalen Welt: Wir liefern Insights und Trends
  • H3 Umfirmierung bei Amazon: Mit diesen 6 Tipps vermeiden Seller die Account-Sperrung
  • H3 E-Mail Marketing: Höhere Öffnungsraten & mehr Sales
  • H3 Server-Side-Tracking: Mehr Kontrolle, weniger Verluste
  • H3 W&V veröffentlicht webnetz KI-Check auf mehreren Kanälen
  • H3 Vom Stadion-Screen aufs Smartphone: Digitale Sponsoring-Verlängerung als Gamechanger für Vereine und Partner
  • H3 Influencer Marketing: Follower ≠ Erfolg: Vermeide diese Fehler
  • H3 OpenAI baut Werbung bei ChatGPT aus
  • H3 W&V und BuchMarkt vermarkten webnetz Social-Check der Publikumsverlage
  • H3 Krombacher, Astra, Bitburger, Beck‘s & Co.: Welchen Biermarken gelingt es, relevante Social Media Resonanz zu erzeugen?
  • H3 Content Marketing Guide: Sichtbar ohne Werbebudget
  • H3 Google Ads im Wandel: Dynamic Search Ads werden durch AI-Max ersetzt
  • H3 Das Magazin Politik & Kommunikation veröffentlicht webnetz Social-Check
  • H3 Umfirmierung bei Amazon: Mit diesen 6 Tipps vermeiden Seller die Account-Sperrung
  • H3 Vom Stadion-Screen aufs Smartphone: Digitale Sponsoring-Verlängerung als Gamechanger für Vereine und Partner
  • H3 Krombacher, Astra, Bitburger, Beck‘s & Co.: Welchen Biermarken gelingt es, relevante Social Media Resonanz zu erzeugen?
  • H3 E-Mail Marketing: Höhere Öffnungsraten & mehr Sales
  • H3 Influencer Marketing: Follower ≠ Erfolg: Vermeide diese Fehler
  • H3 Content Marketing Guide: Sichtbar ohne Werbebudget
  • H3 Server-Side-Tracking: Mehr Kontrolle, weniger Verluste
  • H3 OpenAI baut Werbung bei ChatGPT aus
  • H3 Google Ads im Wandel: Dynamic Search Ads werden durch AI-Max ersetzt
  • H3 W&V veröffentlicht webnetz KI-Check auf mehreren Kanälen
  • H3 W&V und BuchMarkt vermarkten webnetz Social-Check der Publikumsverlage
  • H3 Das Magazin Politik & Kommunikation veröffentlicht webnetz Social-Check
  • H2 Wir lieben Leute, die leidenschaftlich agieren.
  • H3 Offene Stellen
  • H2 Online-Marketing-News direkt ins Postfach
  • H2 Warum Sie sich für webnetz entscheiden sollten?
A+
Heading Text Quality
All 39 heading(s) have substantive, well-formed text
PASS
All 39 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "de"
PASS
Lang attribute set to "de"
Info::
<html lang="de"> is set and valid
Got: de
A+
Tabindex Anti-Patterns
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Mobile-Readable Font Sizes
No visible text nodes measured on the page
PASS
No visible text nodes measured on the page
Info::
No visible text nodes measured on the page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
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.
Info::
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)
ElementRatioRequiredFGBGResult
h1 besser digital21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wir sind Experten f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wir entwerfen digita…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Immer das passende T…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Das sagen unsere Kun…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Neues aus der digita…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wir lieben Leute, di…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Online-Marketing-New…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Warum Sie sich für …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Strategie & Beratung21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Online-Marketing21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Content & Kampagnen21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Design & Video21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Web-Entwicklung21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Umfirmierung bei Ama…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 E-Mail Marketing: H…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Server-Side-Tracking…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 W&V veröffentlicht …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Vom Stadion-Screen a…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Influencer Marketing…21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback