Skip to content
https://bundesregierung.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 8 <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
Landmark Structure
16 landmarks
REVIEW
16 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
1 of 8 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Service-Navigation" SEARCH MAIN ASIDE 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
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 Die Bundesregierung ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
A
Heading Hierarchy
44 headings
PASS
44 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Hinweis zum Datenschutz
  • H1 Bundesregierung | Startseite duplicate H1
  • H2 Hauptnavigation
  • H3 Bundeskanzler
  • H3 Schwerpunkte
  • H3 Bundesregierung
  • H3 Aktuelles
  • H3 Mediathek
  • H3 Service
  • H2 Hannover Messe und Deutsch-Brasilianische Regierungskonsultationen Technologischer Fortschritt und digitale Transformation
  • H3 Beitrag teilen
  • H2 Download Gemeinsame Erklärung der 3. Deutsch-Brasilianischen Regierungskonsultationen
  • H3 Beitrag teilen
  • H2 Newsroom
  • H2 Aktuelles
  • H3 Fragen und Antworten zur Entlastungsprämie Steuerfreie Prämie für Beschäftigte möglich
  • H3 Mobilfunkmessung per App Langsames Internet jetzt einfacher nachweisbar
  • H3 Polizeiliche Kriminalstatistik 2025 Leichter Rückgang der Straftaten
  • H3 Niedrigere Energiekosten für alle Das macht die Bundesregierung für Entlastungen bei den Energiepreisen
  • H2 Pressestatement des Kanzlers bei der Konferenz zur Sicherung der Straße von Hormus Für Stabilität im Nahen Osten
  • H3 Beitrag teilen
  • H2 Weitere Termine des Kanzlers
  • H3 Pressekonferenz zu den 3. Deutsch-Brasilianischen Regierungskonsultationen in Hannover Für eine starke und dynamische Partnerschaft
  • H3 Rede des Bundeskanzlers beim Jahresempfang des Bundesverbandes deutscher Banken e.V. Banken öffnen Türen zum Kapitalmarkt
  • H3 Pressekonferenz zu den Deutsch-Ukrainischen Regierungskonsultationen „Wir sind Partner für ein sicheres Europa“
  • H3 Pressekonferenz von Bundeskanzler Merz und Irlands Premierminister Martin Seite an Seite in der Europäischen Union
  • H3 Rede des Bundeskanzlers zum 100. Jubiläum der Deutschen Lufthansa Lufthansa als ein Schlüsselunternehmen für Deutschland
  • H3 Grußwort des Bundeskanzler beim Sachsen-Anhalt-Abend In gemeinsamer Verantwortung schwierige Zeiten meistern
  • H2 Spritpreise und Strukturreformen Regierungskoalition einigt sich auf schnelle Hilfen für Verbraucher und Wirtschaft
  • H3 Beitrag teilen
  • H2 Nach Fall des Assad-Regimes Bundesregierung unterstützt syrischen Übergangsprozess
  • H2 Aktuelle Entwicklungen im Nahen Osten Chance auf Frieden im Nahen Osten nutzen
  • H2 Humanitäre, finanzielle und militärische Hilfe So unterstützt Deutschland die Ukraine
  • H2 Naher Osten Deutschland steht in tiefer Freundschaft an der Seite Israels
  • H2 Nach Fall des Assad-Regimes Bundesregierung unterstützt syrischen Übergangsprozess
  • H2 Aktuelle Entwicklungen im Nahen Osten Chance auf Frieden im Nahen Osten nutzen
  • H2 Humanitäre, finanzielle und militärische Hilfe So unterstützt Deutschland die Ukraine
  • H2 Naher Osten Deutschland steht in tiefer Freundschaft an der Seite Israels
  • H2 Nach Fall des Assad-Regimes Bundesregierung unterstützt syrischen Übergangsprozess
  • H2 Bundesregierung in den Sozialen Medien
  • H2 Das Bundeskabinett im Überblick
  • H3 Beitrag teilen
  • H2 Terminkalender des Kanzlers
  • H2 SERVICES DER BUNDESREGIERUNG

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
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
21 image(s) with good alt text
24 images 21 good alt text
IssueCount
too long3 image(s)
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cookie-allow-necessarycheckboxnone
#cookie-allow-trackingcheckboxnone
#bpa-search-input-id-6inputSuchbegriff eingebenaria-label
#bpa-search-input-id-7inputSuchbegriff eingebenaria-label
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 Bundesregierung | St…15.73:13.0:1
#000000
#E3DEDA
Pass
h2 Hauptnavigation15.73:13.0:1
#000000
#E3DEDA
Pass
h2 SERVICES DER BUNDESR…15.73:13.0:1
#000000
#E3DEDA
Pass
h3 Beitrag teilen15.73:13.0:1
#000000
#E3DEDA
Pass
h3 Beitrag teilen15.73:13.0:1
#000000
#E3DEDA
Pass
h3 Beitrag teilen15.73:13.0:1
#000000
#E3DEDA
Pass
h3 Beitrag teilen15.73:13.0:1
#000000
#E3DEDA
Pass
h3 Beitrag teilen15.73:13.0:1
#000000
#E3DEDA
Pass
title Die Bundesregierung …21.00:14.5:1
#000000
#FFFFFF
Pass
strong Hinweis zum Datensch…21.00:13.0:1
#000000
#FFFFFF
Pass
p Wir verwenden Cookie…21.00:14.5:1
#000000
#FFFFFF
Pass
span Zur Datenschutzerkl…21.00:14.5:1
#000000
#FFFFFF
Pass
span Technisch notwendig …21.00:14.5:1
#000000
#FFFFFF
Pass
button mehr Informationen21.00:14.5:1
#000000
#FFFFFF
Pass
p Einige Cookies sind …21.00:14.5:1
#000000
#FFFFFF
Pass
span Statistik21.00:14.5:1
#000000
#FFFFFF
Pass
button mehr Informationen21.00:14.5:1
#000000
#FFFFFF
Pass
p Wir nutzen auf unser…21.00:14.5:1
#000000
#FFFFFF
Pass
p Das Tool verwendet C…21.00:14.5:1
#000000
#FFFFFF
Pass
p Wenn Sie mit der Aus…21.00:14.5: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.

A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 31 passed
PASS
96

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.checkbox > label > span > input#cookie-allow-necessary li.checkbox > label > span > input#cookie-allow-necessary
li.checkbox > label > span > input#cookie-allow-tracking li.checkbox > label > span > input#cookie-allow-tracking

These are opportunities to improve the usage of ARIA in your application which 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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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
●`[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
●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 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
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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.
○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.
○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.
○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