Skip to content
https://bundesgesundheitsministerium.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 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::
6 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 6 <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
22 landmarks
REVIEW
22 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No contentinfo (footer) landmark
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 "Sprunglinks" MAIN CONTENTINFO (missing!)

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
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | BMG ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA 2 pass AA only
span Leichte Sprache
1.30:1
#000000
on
#232020
needs 4.5:1 (normal text)
16px · above the fold
span Suche
1.15:1
#000000
on
#0B1624
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span English
1.46:1
#000000
on
#022C48
needs 4.5:1 (normal text)
16px · above the fold
span Logo Bundesministerium für Gesundheit (…
1.46:1
#000000
on
#022C48
needs 4.5:1 (normal text)
16px · above the fold
span Suche
1.46:1
#000000
on
#022C48
needs 4.5:1 (normal text)
16px · above the fold
span English
1.46:1
#000000
on
#022C48
needs 4.5:1 (normal text)
16px · above the fold
span Menu
1.46:1
#000000
on
#022C48
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Bundesministerium f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Warken: Wir schaffen…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gesetze und Verordnu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Publikationen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Arbeiten im BMG21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aktuelle Forschung, …21.00:13.0:1
#000000
#FFFFFF
Pass
title Bundesministerium f…21.00:14.5:1
#000000
#FFFFFF
Pass
a Zum Hauptinhalt spri…21.00:14.5:1
#000000
#FFFFFF
Pass
a Zur Hauptnavigation …17.05:14.5:1
#000000
#E5E8E9
Pass
a Zum Seitenende sprin…10.64:14.5:1
#000000
#B9B8BB
Pass
span Gesetze6.78:14.5:1
#000000
#7A96AB
Pass
span Gesundheit A-Z10.22:14.5:1
#000000
#B4B5B5
Pass
span Gebärdensprache5.71:14.5:1
#000000
#748897
Pass
span Leichte Sprache1.30:14.5:1
#000000
#232020
Fail
span Suche1.15:14.5:1
#000000
#0B1624
Fail
span English1.46:14.5:1
#000000
#022C48
Fail
span Logo Bundesministeri…1.46:14.5:1
#000000
#022C48
Fail
span Suche1.46:14.5:1
#000000
#022C48
Fail
span English1.46:14.5:1
#000000
#022C48
Fail
span Menu1.46:14.5:1
#000000
#022C48
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
66 headings
PASS
66 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Bundes-Klinik-Atlas
  • H2 Gesundheitsportal
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Krankenhausreform
  • H2 Gesundheitsportal
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Ratgeber Pflege
  • H2 Ratgeber Demenz
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 E-Rezept
  • H2 Gesundheitsportal
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Krankenhausreform
  • H2 Gesundheitsportal
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Online-Ratgeber Krankenversicherung
  • H2 Arzneimittelversorgung
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Internationale Organisationen
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Gesundheitsrisiko Hitze
  • H2 Antibiotika-Resistenzen
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Gesetze & Verordnungen
  • H2 Besuch im BMG
  • H3 Das könnte Sie auch interessieren
  • H2 Aktuelle Meldungen
  • H2 Gesetze & Verordnungen
  • H2 Besuch im BMG
  • H3 Staatssekretäre im BMG
  • H2 Katja Kohfeld
  • H2 Christian Luft
  • H3 Das könnte Sie auch interessieren
  • H2 Berufe & Laufbahnen
  • H2 Praktikum & Referendariat
  • H3 Das könnte Sie auch interessieren
  • H2 Pressefotos
  • H2 Termine
  • H3 Das könnte Sie auch interessieren
  • H2 Online-Ratgeber Pflege
  • H2 Online-Ratgeber Demenz
  • H2 Online-Ratgeber Krankenversicherung
  • H1 (empty)
  • H1 Suche duplicate H1
  • H1 Bundesministerium für Gesundheit (BMG) duplicate H1
  • H2 Warken: Wir schaffen die Grundlage für eine vernetzte, digitale und standardisierte Notfallversorgung
  • H2 Warken: „Nur ein finanziell stabiles System ist zukunftsfähig und kann eine gute Versorgung garantieren!“
  • H2 Warken: "Diese Reform ist das Gegenteil von einseitig."
  • H2 Gesetze und Verordnungen
  • H2 Publikationen
  • H2 Arbeiten im BMG
  • H2 Aktuelle Forschung, Aufgaben und Organisation
  • H3 Aufgaben und Organisation
  • H3 Ressortforschung
  • H3 Kontakt & Anschrift
  • H3 Pressekontakt

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
Alt Text Quality
All 83 images OK
PASS
All 83 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
80 image(s) with good alt text
83 images 80 good alt text
IssueCount
too long3 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchtext(Suchen nach Freitext)placeholder only

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

<input type="text" name="q" id="search">

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

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

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.

○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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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
○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.
○`<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