Skip to content
https://bmwi.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ 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::
5 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 5 <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
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="templateQueryStringListen" id="f62b30d2a-739e-4c31-b356-c9304ece5336d44c2f420-9d28-4a00-af2f-fe687b2e8016">; <input type="text" name="templateQueryStringListen" id="f61d602aa-09a5-4553-8c2d-1e15679d8c37d44c2f420-9d28-4a00-af2f-fe687b2e8016">
Info::
3 control(s) properly labeled
5 controls
3 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#chbxCookieConsentcheckboxTracking-Einwilligungfor/id
#cookiebanner-checkbox-obligatorycheckboxTechnisch notwendig (nicht abwählbar)for/id
#cookiebanner-checkbox-jwplayercheckboxEinwilligung zum Videodienst JW-Playerfor/id
#f62b30d2a-739e-4c31-b356-c9304ece5336d44c2f420-9d28-4a00-af2f-fe687b2e8016text(Suchbegriff eingeben)placeholder only
#f61d602aa-09a5-4553-8c2d-1e15679d8c37d44c2f420-9d28-4a00-af2f-fe687b2e8016text(Suchbegriff eingeben)placeholder only

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

<input type="text" name="templateQueryStringListen" id="f62b30d2a-739e-4c31-b356-c9304ece5336d44c2f420-9d28-4a00-af2f-fe687b2e8016">; <input type="text" name="templateQueryStringListen" id="f61d602aa-09a5-4553-8c2d-1e15679d8c37d44c2f420-9d28-4a00-af2f-fe687b2e8016">

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

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.

A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Skiplinks" MAIN 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
44 headings
PASS
44 headings
Info::
Single H1 present
  • H2 Einwilligung zum Videodienst JW-Player
  • H2 Suche
  • H2 Themen
  • H3 Schwerpunkte
  • H3 Wirtschaft
  • H3 Energie
  • H3 Industrie
  • H3 Mittelstand
  • H3 Außenwirtschaft
  • H3 Europa
  • H3 Digitale Welt und Innovation
  • H3 Ausbildung & Beruf
  • H2 Service
  • H3 Presse
  • H3 Gesetzesvorhaben
  • H3 Informationsdienste
  • H3 Hilfe und Support
  • H2 Ministerium
  • H3 Willkommen im Ministerium
  • H3 Das Bundeswirtschaftsministerium als Arbeitgeber
  • H3 Geschichte
  • H2 Medienraum
  • H2 Kontakt
  • H1 Bundesministerium für Wirtschaft und Klimaschutz
  • H2 Frühjahrsprojektion der Bundesregierung 2026
  • H2 Treffen mit Branche zum Thema Kerosin-Versorgung
  • H2 Gegen hohe Spritpreise: Unser Kraftstoffmaßnahmenpaket im Überblick
  • H2 Zitat
  • H2 Aus den sozialen Netzwerken
  • H2 Pressemitteilungen
  • H2 Im Fokus
  • H3 Für Wachstum und Wettbewerbsfähigkeit – Leitlinien für eine zeitgemäße Ordnungspolitik
  • H3 Sichere Gasversorgung in Deutschland
  • H3 Tourismusstrategie: Kurs auf Wachstum und Wettbewerbsfähigkeit
  • H3 Solidarität mit der Ukraine
  • H2 Einblicke.
  • H3 Menschen im Ministerium.
  • H2 Ausbildung beim Bundeswirtschaftsministerium
  • H3 Ministerium
  • H3 Arbeiten im Bundesministerium für Wirtschaft und Energie
  • H2 Häufig gesuchte Themen
  • H2 Einwilligung
  • H3 Technisch notwendig (nicht abwählbar)
  • H3 Einwilligung zum Videodienst JW-Player
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
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 Bundesministerium f…14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Einwilligung zum Vid…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Suche21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Medienraum14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Kontakt14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Zitat14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Aus den sozialen Net…14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Pressemitteilungen14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Im Fokus14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Häufig gesuchte The…14.59:13.0:1
#000000
#D7D7D7
Pass
h2 Einwilligung14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Schwerpunkte14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Wirtschaft14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Energie14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Industrie14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Mittelstand14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Außenwirtschaft14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Europa14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Digitale Welt und In…14.59:13.0:1
#000000
#D7D7D7
Pass
h3 Ausbildung & Beruf14.59:13.0:1
#000000
#D7D7D7
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.

A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 28 passed
PASS
95

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.welcome > header.header > div.navbar-header > button.main-navbar-link body.welcome > header.header > div.navbar-header > button.main-navbar-link

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.

○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
●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
●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 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.
●`[lang]` attributes have a valid value
●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
○`button`, `link`, and `menuitem` elements have accessible names
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`<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.
○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.

Send Feedback