Skip to content
https://bmbf.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 4 <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
Heading Hierarchy
36 headings, 1 skip(s)
REVIEW
36 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Navigation und Service
  • H1 Hinweis zur Verwendung von Cookies duplicate H1
  • H2 Statistik
  • H2 Externe Medien
  • H1 Bundesministerium für Forschung, Technologie und Raumfahrt duplicate H1
  • H3 Neue Technologien entwickeln: Hightech Agenda Deutschland skipped
  • H3 Zukunft der Medizinforschung an der Charité
  • H3 Innovationen für den Industriestandort Deutschland: Dorothee Bär auf der Hannover Messe 2026
  • H3 „Deutschland soll innovativster Biotech-Standort der Welt werden"
  • H3 Dorothee Bär: „Wir brauchen Forschung, um hybride Angriffe abzuwehren und unsere Demokratie zu schützen.“
  • H3 Wiederaufbau durch Wissen: BMFTR stärkt Forschungs- und Innovationspartnerschaft mit der Ukraine
  • H3 Bundesforschungsministerin Bär bei der Venture SPRIND 2026: Innovationen brauchen Mut und Kapital
  • H3 Dorothee Bär: Mit der Quantum Computing Competition zum Top-Quantentechnologieland
  • H2 Willkommen im Bundesministerium für ­Forschung, Technologie und Raumfahrt
  • H3 Von Klima bis Quanten: Sechs Absichtserklärungen mit Brasilien unterzeichnet
  • H3 Ein Jahr 1.000-Köpfe-Plus: 286 Spitzenforschende gefördert
  • H3 All Systems Go! Artemis II startet mit deutscher Technik zum Mond
  • H3 Transnationale Bildung: international im eigenen Land studieren und forschen
  • H3 Wissenschaftsjahr 2026 – Medizin der Zukunft
  • H2 Von der Forschung in die Praxis
  • H3 Bundesagentur für Sprunginnovationen (SPRIND)
  • H3 Innovative Hochschule
  • H3 Forschungszulage
  • H2 Spitzenforschung mit Weitblick
  • H3 Künstliche Intelligenz
  • H3 Robotik
  • H3 Supercomputing
  • H3 Quanten­technologien
  • H3 Dekade gegen Krebs
  • H2 Wir stärken die internationale Zusammenarbeit in der Wissenschaft
  • H3 Vernetzung weltweit
  • H3 Wissenschaftsdiplomatie
  • H3 Europäischer Forschungsraum
  • H3 Horizont Europa
  • H2 Das Ministerium
  • H2 (empty)

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

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 Homepage - Dokument nicht gefunden - BMFTR ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
14 icon(s) detected
REVIEW
14 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
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 Navigation und Service
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
32px · top of page (header area)
h1 Hinweis zur Verwendung von Cookies
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
32px · above the fold
h1 Bundesministerium für Forschung, Techno…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Statistik
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · above the fold
h2 Externe Medien
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · mid-page
h2 Willkommen im Bundesministerium für
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Von der Forschung
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 mit Weitblick
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Wir stärken die
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Zusammenarbeit in der Wissenschaft
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Das
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Neue Technologien entwickeln: Hightech A…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Zukunft der Medizinforschung an der Char…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Innovationen für den Industriestandort …
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 „Deutschland soll innovativster Biotec…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Dorothee Bär: „Wir brauchen Forschung…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Wiederaufbau durch Wissen: BMFTR stärkt…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bundesforschungsministerin Bär bei der …
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Dorothee Bär: Mit der Quantum Computing…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Von Klima bis Quanten: Sechs Absichtserk…
1.28:1
#000000
on
#002040
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Navigation und Servi…1.28:13.0:1
#000000
#002040
Fail
h1 Hinweis zur Verwendu…1.28:13.0:1
#000000
#002040
Fail
h1 Bundesministerium f…1.28:13.0:1
#000000
#002040
Fail
h2 Statistik1.28:13.0:1
#000000
#002040
Fail
h2 Externe Medien1.28:13.0:1
#000000
#002040
Fail
h2 Willkommen im Bundes…1.28:13.0:1
#000000
#002040
Fail
h2 Von der Forschung1.28:13.0:1
#000000
#002040
Fail
h2 mit Weitblick1.28:13.0:1
#000000
#002040
Fail
h2 Wir stärken die1.28:13.0:1
#000000
#002040
Fail
h2 Zusammenarbeit in de…1.28:13.0:1
#000000
#002040
Fail
h2 Das1.28:13.0:1
#000000
#002040
Fail
h3 Neue Technologien en…1.28:13.0:1
#000000
#002040
Fail
h3 Zukunft der Medizinf…1.28:13.0:1
#000000
#002040
Fail
h3 Innovationen für de…1.28:13.0:1
#000000
#002040
Fail
h3 „Deutschland soll …1.28:13.0:1
#000000
#002040
Fail
h3 Dorothee Bär: „Wi…1.28:13.0:1
#000000
#002040
Fail
h3 Wiederaufbau durch W…1.28:13.0:1
#000000
#002040
Fail
h3 Bundesforschungsmini…1.28:13.0:1
#000000
#002040
Fail
h3 Dorothee Bär: Mit d…1.28:13.0:1
#000000
#002040
Fail
h3 Von Klima bis Quante…1.28:13.0:1
#000000
#002040
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 28 passed
REVIEW
89

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Künstliche Intelligenz SCHLÜSSELTECHNOLOGIE Das BMFTR fördert die Weiterentwi… div#content > div.l-module-wrapper > div.l-teaser-grid > div.l-teaser-grid__row

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.

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
div.row > div.column > div.c-autosuggest > button.submit div.row > div.column > div.c-autosuggest > button.submit

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Neue Technologien entwickeln: Hightech Agenda Deutschland div#content > div.c-teaser-image-slider > div.c-teaser-image-slider__text-wrapper > h3.c-teaser-image-slider__headline

These are opportunities to improve keyboard navigation in your application.

○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]`s are contained by their required parent element
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
●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
○Elements with `role="dialog"` or `role="alertdialog"` 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
○ARIA IDs are unique
○`<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.
○`[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
13 landmarks
PASS
13 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "navskiphead" SEARCH 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+
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
14 image(s) with good alt text
14 images 14 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#_9nfoonwmncheckboxStatistik-Tracker einschaltenfor/id
#_3lupjxmllcheckboxExterne Medien immer einbettenfor/id
#f1051644d1051642searchSuchbegrifffor/id
#replacedSelect_label_917278selectThemenbereich:for/id
#f917278d1051602textSuchbegrifffor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://www.bmftr.bund.de/SiteGlobals/Frontend/Styles/addon_print.css?v=9
Print Stylesheet ✓ Print Optimized
Print stylesheet https://www.bmftr.bund.de/SiteGlobals/Frontend/Styles/addon_print.css?v=9 ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback