Skip to content
https://kfw.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
3
REVIEW
7
PASS
3
INFO
0
Checks
13
3 PASS 7 REVIEW 3 FIX
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 ✗
B
Alt Text Quality
2 of 43 images have issues
REVIEW
2 of 43 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with alt text over 125 characters
Info::
31 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
43 images 9 good alt text 31 decorative 2 missing
IssueCount
missing2 image(s)
too long1 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title HTTP 404 | KfW ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) 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::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search role='search' landmark
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Welche Förderung su…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Seite teilen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 KfW Stories - Das di…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unser internationale…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Karriere bei der KfW…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 KfW-Newsroom21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ihr Weg zur KfW-För…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Was möchten Sie üb…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 KfW-Konzern21.00:13.0:1
#000000
#FFFFFF
Pass
h2 KfW Services21.00:13.0:1
#000000
#FFFFFF
Pass
h2 KfW im Dialog21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Folgen Sie uns auf:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 KfW IPEX-Bank21.00:13.0:1
#000000
#FFFFFF
Pass
h3 DEG21.00:13.0:1
#000000
#FFFFFF
Pass
h3 KfW Entwicklungsbank21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Förderprodukt finde…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Förderung beantrage…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Vorhaben starten21.00:13.0:1
#000000
#FFFFFF
Pass
title Bank aus Verantwortu…5.24:14.5:1
#000000
#7F7F7F
Pass
span Zum Hauptinhalt5.24:14.5:1
#000000
#7F7F7F
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 26 passed
REVIEW
86

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.

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
figure.video > div#slidePresenterVideoTeaser > div.slide-presenter-wrapper > img.slide-presenter-thumbnail figure.video > div#slidePresenterVideoTeaser > div.slide-presenter-wrapper > img.slide-presenter-thumbnail
figure.video > div#slidePresenterVideoTeaser > div.slide-presenter-wrapper > img.slide-presenter-thumbnail figure.video > div#slidePresenterVideoTeaser > div.slide-presenter-wrapper > img.slide-presenter-thumbnail

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Als Privatperson Als Unternehmen Als öffentliche Einrichtung div.tab-navigation-dropdown > div.form-item > div.select-wrapper > select#select-form-24052956

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.

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
Stärkung des Wirtschafts- und Innovationsstandorts Deutschland div.teaser-content-text-container > div.teaser-content-text > p > a.link
KfW Stories "So stärkt die KfW den Wirtschaftsstandort Deutschland" div.teaser-content-text-container > div.teaser-content-text > p > a.link
KfW Stories "Im Namen des Klimaziels" div.teaser-content-text-container > div.teaser-content-text > p > a.link
Startseite KfW Stories div.teaser-content-text-container > div.teaser-content-text > p > a.link
Jobbörse - Stellenanzeigen div.text-image-content > div.text-image-text > p > a.link
○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
●`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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
○`[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.
○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
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "breadcrumb" SEARCH MAIN ASIDE CONTENTINFO footer

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

A
Heading Hierarchy
27 headings
PASS
27 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Welche Förderung suchen Sie?
  • H2 KfW Stories - Das digitale Magazin
  • H3 Stärkung des Wirtschafts- und Innovationsstandorts Deutschland
  • H3 Energiewende im privaten Gebäudebereich
  • H2 Unser internationales Engagement
  • H3 KfW IPEX-Bank
  • H3 DEG
  • H3 KfW Entwicklungsbank
  • H2 Karriere bei der KfW: Nachhaltig Zukunft gestalten – machen wir. Gemeinsam.
  • H2 KfW-Newsroom
  • H3 22.04.2026 | KfW KfW-Treasurer Tim Armbruster übernimmt Co-Vorsitz von deutsch-französischer Taskforce zum digitalen Finanzwesen
  • H3 21.04.2026 | KfW Research KfW-Kreditmarktausblick April 2026
  • H3 16.04.2026 | KfW Härtetest bei dritter Blockchain-Anleihe der KfW
  • H2 Ihr Weg zur KfW-Förderung
  • H3 Förderprodukt finden
  • H3 Förderung beantragen
  • H3 Vorhaben starten
  • H2 Was möchten Sie über die KfW wissen?
  • H3 KfW auf einen Blick Sie möchten mehr über die KfW erfahren? Hier finden Sie alle wich­tigen Infos.
  • H3 Karriere bei der KfW Was zeichnet die KfW als Arbeit­gebe­rin aus und welche aktuellen Stellen­angebote gibt es?
  • H3 Investor Relations Die Anleihen der KfW gelten als besonders sicher. Was zeichnet die Kredit­qualität der KfW aus?
  • H3 KfW Research Volkswirtschaftliche Analysen zu Wirtschaft, Umwelt und Gesell­schaft.
  • H2 KfW-Konzern
  • H2 KfW Services
  • H2 KfW im Dialog
  • H2 Folgen Sie uns auf:
  • H1 Seite teilen duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Form Accessibility
1 of 8 controls have issues
PASS
1 of 8 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="select-form-24052956" id="select-form-24052956">
Info::
7 control(s) properly labeled
8 controls
7 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-fieldsearchSuchbegriff eingebenaria-label
#searchfield_headsearchSuchbegriff eingebenaria-label
#i_star1radio1 Sternfor/id
#i_star2radio2 Sternefor/id
#i_star3radio3 Sternefor/id
#i_star4radio4 Sternefor/id
#i_star5radio5 Sternefor/id
#select-form-24052956select(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="select-form-24052956" id="select-form-24052956">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

Send Feedback