Skip to content
https://destatis.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 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.

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.
C
Form Accessibility
Action
3 of 7 controls have issues
REVIEW
3 of 7 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="image" name="submit" id="f2414d2372">; <input type="image" name="submit" id="f2414d2372">; <input type="image" name="submit" id="f2416d263458">
Info::
4 control(s) properly labeled
7 controls
4 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#_ire3jwf87checkboxStatistik-Trackerfor/id
#f2414d2410textSuchbegriff eingebenfor/id
#f2414d2410textSuchbegriff eingebenfor/id
#f2416d2410textSuchbegriff eingebenfor/id
#f2414d2372image(none)none
#f2414d2372image(none)none
#f2416d263458image(none)none

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

<input type="image" name="submit" id="f2414d2372">; <input type="image" name="submit" id="f2414d2372">; <input type="image" name="submit" id="f2416d263458">

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

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 - Statistisches Bundesamt ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
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 Menü
1.90:1
#000000
on
#3C3C3C
needs 3.0:1 (large text)
32px · top of page (header area)
h1 Einwilligung zur Verwendung von Cookies …
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Statistisches Bundesamt
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Servicemenü
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Suche
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Suche
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Suche
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pressemitteilungen
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pressevorschau
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aktuelles
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Daten und Analyse
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Im Fokus
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Unternavigation aller Website-Bereiche
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Oft gesucht
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Daten zur konjunkturellen Entwicklung
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Daten zur Reform des Gesundheitssystems
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Neu erschienen:
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 WISTA 2/2026
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Relaunch des
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Dashboard
1.87:1
#000000
on
#3B3B3B
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Menü1.90:13.0:1
#000000
#3C3C3C
Fail
h1 Einwilligung zur Ver…1.87:13.0:1
#000000
#3B3B3B
Fail
h1 Statistisches Bundes…1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Servicemenü1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Suche1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Suche1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Suche1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Pressemitteilungen1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Pressevorschau1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Aktuelles1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Daten und Analyse1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Im Fokus1.87:13.0:1
#000000
#3B3B3B
Fail
h2 Unternavigation alle…1.87:13.0:1
#000000
#3B3B3B
Fail
h3 Oft gesucht1.87:13.0:1
#000000
#3B3B3B
Fail
h3 Daten zur konjunktur…1.87:13.0:1
#000000
#3B3B3B
Fail
h3 Daten zur Reform des…1.87:13.0:1
#000000
#3B3B3B
Fail
h3 Neu erschienen:1.87:13.0:1
#000000
#3B3B3B
Fail
h3 WISTA 2/20261.87:13.0:1
#000000
#3B3B3B
Fail
h3 Relaunch des1.87:13.0:1
#000000
#3B3B3B
Fail
h3 Dashboard1.87:13.0:1
#000000
#3B3B3B
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
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
4 <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 "navskiphead" 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
36 headings
PASS
36 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.
Info::
3 hidden heading(s) (aria-hidden)
  • H1 Menü
  • H1 Einwilligung zur Verwendung von Cookies und ähnlichen Technologien duplicate H1
  • H2 (empty)
  • H2 Servicemenü hidden
  • H2 Suche
  • H2 Suche
  • H1 Statistisches Bundesamt duplicate H1
  • H2 Suche
  • H3 Oft gesucht
  • H2 Pressemitteilungen
  • H2 Pressemitteilungen
  • H2 Pressevorschau
  • H2 Pressevorschau
  • H2 Aktuelles hidden
  • H3 Zahl der Woche : 9,4 % der weiblichen Auszubildenden begannen 2024 eine Ausbildung zur Medizinischen Fachangestellten.
  • H3 Daten zur konjunkturellen Entwicklung
  • H3 Daten zur Reform des Gesundheitssystems
  • H3 Neu erschienen: WISTA 2/2026
  • H3 Relaunch des Dashboard Konjunktur
  • H3 Daten zum Krieg im Nahen Osten
  • H3 Durchschnittsmensch: neue Daten zum Thema Gesundheit
  • H3 Haushalte für die LWR-Befragung gesucht
  • H3 Siegerteams der nationalen Phase stehen fest!
  • H3 Fakten zum Thema Rente
  • H3 Klassifikation der Wirtschaftszweige 2025
  • H2 Daten und Analyse
  • H2 Im Fokus
  • H3 Rente
  • H3 Durchschnittsmensch
  • H3 Fachkräfte
  • H3 Klima
  • H3 Seite teilen
  • H2 Unternavigation aller Website-Bereiche hidden
  • H3 Service
  • H3 Anschrift
  • H3 Folgen Sie uns!

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 21 images OK
PASS
All 21 images OK
Info::
12 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
21 images 9 good alt text 12 decorative
All images have appropriate alt text.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: SiteGlobals/Frontend/Styles/addon_print.css?v=15
Print Stylesheet ✓ Print Optimized
Print stylesheet SiteGlobals/Frontend/Styles/addon_print.css?v=15 ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 27 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.

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.

○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
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
○`[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
○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.
○Image elements have `[alt]` attributes
○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.
○`[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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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