Skip to content
https://hamburg.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 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
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::
1 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 1 <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
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 Fehlerseite 404 - hamburg.de ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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
A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 MAIN ASIDE "Visuelle Assistenzsoftware öffnen." 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
37 headings
PASS
37 headings
Info::
Single H1 present
  • H1 Moin!
  • H2 Aktuelles
  • H3 Kiel stimmt für Olympia
  • H3 "Wohnen bleiben im Quartier"
  • H3 Tagestipps für Mittwoch
  • H3 Bunte Wasserlichtkonzerte im Park
  • H2 Informationen über barrierefreie Angebote
  • H3 Hamburg.de barrierefrei
  • H3 Neuigkeiten
  • H2 Hier finden Sie weitere wichtige und aktuelle Themen, die Hamburg gerade bewegen
  • H3 Hamburg legt Finanzkonzept vor
  • H3 Maria Lassnig und Edvard Munch
  • H3 Zwischen Äpfeln, Birnen und Beeren
  • H3 Hebesatz für Gewerbesteuer bleibt auch 2026 unverändert – Hundesteuergesetz modernisiert
  • H2 Politik und Verwaltung
  • H3 Senat
  • H3 Behörden
  • H3 Bezirke
  • H2 Ihre Anlaufstelle für alle Services der Stadt
  • H2 Die Inhalte führen zur Übersichtseite für Hotels, Kultur und zu einem neuen Musical in Hamburg.
  • H3 Buchen Sie Ihr Hotel in Hamburg
  • H3 Kultur
  • H3 Zurück in die Zukunft – Das Musical
  • H2 Kirchentag 2029 in Hamburg
  • H2 Reden des Ersten Bürgermeisters
  • H2 Kirchentag 2029 in Hamburg
  • H2 Reden des Ersten Bürgermeisters
  • H2 Kirchentag 2029 in Hamburg
  • H2 Informationen zu Themen aus den Bereichen Politik und Verwaltung sowie Freizeit und Kultur
  • H3 Hamburgs Untergrund analog und digital erfahrbar
  • H3 Neuer 6 Euro-Service startet ab sofort in Randgebieten Hamburgs
  • H3 Tipps für einen Kurztrip
  • H3 Hebesatz für Gewerbesteuer bleibt auch 2026 unverändert – Hundesteuergesetz modernisiert
  • H2 Sammlung von weiterführenden Inhalten
  • H2 Was suchen Sie?
  • H2 Wichtige Themen
  • H2 Häufig gesucht
A+
Alt Text Quality
All 28 images OK
PASS
All 28 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
28 images 24 good alt text 2 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#km1-searchbox-search-input-127searchSucheingabefeldaria-label
searchInputAutoCompletesearchAutocompletearia-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
h2 Aktuelles21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Informationen über …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hier finden Sie weit…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Politik und Verwaltu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ihre Anlaufstelle f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Die Inhalte führen …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Kirchentag 2029 in H…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reden des Ersten Bü…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Kirchentag 2029 in H…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reden des Ersten Bü…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Kirchentag 2029 in H…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Informationen zu The…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sammlung von weiterf…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Was suchen Sie?21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wichtige Themen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Häufig gesucht21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Kiel stimmt für Oly…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 "Wohnen bleiben im Q…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tagestipps für Mitt…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bunte Wasserlichtkon…21.00:13.0: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 91/100 — 2 failing, 23 passed
PASS
91

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Sucheingabefeld body.km1-page > main.km1-main > div#km1-search-dialog

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.km1-teaser-slider > div.km1-slider > div.km1-slider__controls > button.km1-button div.km1-teaser-slider > div.km1-slider > div.km1-slider__controls > button.km1-button
div.km1-teaser-slider > div.km1-slider > div.km1-slider__controls > button.km1-button div.km1-teaser-slider > div.km1-slider > div.km1-slider__controls > button.km1-button

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
●`[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 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.
●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
○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.
○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.
○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