Skip to content
https://uni-hamburg.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ 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::
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
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <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.
Page Structure — as a screen reader sees it
BANNER header NAV "Topnavigation 1" MAIN 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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title UHH : Universität Hamburg ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Heading Hierarchy
21 headings
PASS
21 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Universität Hamburg (UHH)
  • H1 Willkommen an der Universität Hamburg duplicate H1
  • H2 Was uns ausmacht
  • H2 Studieren
  • H2 Forschen und kooperieren
  • H2 Bei uns arbeiten
  • H2 News
  • H3 Neue Emmy Noether-Nachwuchsgruppe erforscht Eigenschaften von Quantenmaterialien
  • H3 Vergleichende Studie: Moderne Klimamodelle sind so genau wie noch nie
  • H3 Forschen und Verstehen: Wie viel Grün bedarf es zum Glücklichsein?
  • H3 Willkommen an Bord: Prof. Dr. Michael Krelle verstärkt die Erziehungswissenschaft
  • H3 Wie kann die Arbeit in Krankenhäusern zukunftssicher gestaltet werden?
  • H3 Neue Studie zu Sanktionen: Gegensätze ziehen sich an? Nicht in der Außenpolitik.
  • H3 Willkommen an Bord: Prof. Dr. Anca Balietti verstärkt die Wirtschaftswissenschaft
  • H3 Weitere Meldungen
  • H2 Veranstaltungen
  • H3 Bloody Thursday im WiWi-Bunker
  • H3 Sonntagsführung: Seidenbienen, Kuckucke und andere Frühjahrsinsekten
  • H3 Wissenssysteme und Frauenkämpfe in Lateinamerika
  • H3 Ess-Störungen: Wer bin ich – in meinem Körper mit und ohne Gewicht?
  • H2 Universität Hamburg

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 22 images OK
PASS
All 22 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
21 image(s) with good alt text
22 images 21 good alt text
IssueCount
too long1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://assets.rrz.uni-hamburg.de/assets/print-85727ed44b77df53ff88b8a79482dc1ba86ec114c0f78c348368e4be1d7acaee.css
Print Stylesheet ✓ Print Optimized
Print stylesheet https://assets.rrz.uni-hamburg.de/assets/print-85727ed44b77df53ff88b8a79482dc1ba86ec114c0f78c348368e4be1d7acaee.css ✓Inline @media print Not detected ✗
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 Universität Hamburg…6.13:13.0:1
#000000
#8E8990
Pass
h1 Willkommen an der Un…6.13:13.0:1
#000000
#8E8990
Pass
h2 Was uns ausmacht6.13:13.0:1
#000000
#8E8990
Pass
h2 Studieren6.13:13.0:1
#000000
#8E8990
Pass
h2 Forschen und kooperi…6.13:13.0:1
#000000
#8E8990
Pass
h2 Bei uns arbeiten6.13:13.0:1
#000000
#8E8990
Pass
h2 Veranstaltungen6.13:13.0:1
#000000
#8E8990
Pass
h2 Universität Hamburg6.13:13.0:1
#000000
#8E8990
Pass
h3 Neue Emmy Noether-Na…6.13:13.0:1
#000000
#8E8990
Pass
h3 Vergleichende Studie…6.13:13.0:1
#000000
#8E8990
Pass
h3 Forschen und Versteh…6.13:13.0:1
#000000
#8E8990
Pass
h3 Willkommen an Bord: …6.13:13.0:1
#000000
#8E8990
Pass
h3 Wie kann die Arbeit …6.13:13.0:1
#000000
#8E8990
Pass
h3 Neue Studie zu Sankt…6.13:13.0:1
#000000
#8E8990
Pass
h3 Willkommen an Bord: …6.13:13.0:1
#000000
#8E8990
Pass
h3 Weitere Meldungen6.13:13.0:1
#000000
#8E8990
Pass
h3 Bloody Thursday im W…6.13:13.0:1
#000000
#8E8990
Pass
h3 Sonntagsführung: Se…6.13:13.0:1
#000000
#8E8990
Pass
h3 Wissenssysteme und F…6.13:13.0:1
#000000
#8E8990
Pass
h3 Ess-Störungen: Wer …6.13:13.0:1
#000000
#8E8990
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 97/100 — 1 failing, 29 passed
PASS
97

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Feedback div.breite > ul.linkliste > li > a.feedback
Impressum div.breite > ul.linkliste > li > a.imprint
Datenschutzerklärung div.breite > ul.linkliste > li > a.privacypolicy
Sitemap div.breite > ul.linkliste > li > a.sitemap

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]`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
●Input buttons have discernible text.
●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
●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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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.
○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 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.
○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
○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