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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 SEARCH MAIN CONTENTINFO (missing!)

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
Heading Hierarchy
18 headings
REVIEW
18 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 PATHS2INCLUDE zeigt Wege zu mehr Fairness auf dem Arbeitsmarkt
  • H2 LUH präsentiert aktuelle Projekte auf der Hannover Messe
  • H2 40 Jahre nach der Nuklearkatastrophe von Chornobyl
  • H2 Weltquantentag am 14. April: Exzellenzcluster QuantumFrontiers im Podcast
  • H2 Blühende Deiche verbessern den Küstenschutz
  • H2 Gründungsvorhaben erhalten EXIST-Förderung
  • H2 (empty)
  • H2 Exzellenzcluster an der LUH
  • H2 Finden + Orientieren
  • H2 Studieren an der LUH
  • H3 Fachrichtungen
  • H2 Internationales
  • H2 Aktuelle Internationale Tagungen an der LUH
  • H2 Nachhaltigkeit
  • H2 Aktuelle Meldungen
  • H2 Aktuelle Veranstaltungen
  • H2 Spitzenforschung erleben: Unsere Forschungsschwerpunkte
  • H2 Was uns wichtig ist

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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 error404 – Leibniz Universität Hannover ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

19 pass 1 fail WCAG AA
title Startseite – Leibniz Universität Ha…
1.76:1
#000000
on
#00376B
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 PATHS2INCLUDE zeigt …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 LUH präsentiert akt…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 40 Jahre nach der Nu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Weltquantentag am 14…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Blühende Deiche ver…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gründungsvorhaben e…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Exzellenzcluster an …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Finden + Orientieren21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Studieren an der LUH21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Internationales21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aktuelle Internation…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nachhaltigkeit21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aktuelle Meldungen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aktuelle Veranstaltu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Spitzenforschung erl…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Was uns wichtig ist21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fachrichtungen21.00:13.0:1
#000000
#FFFFFF
Pass
title Startseite – Lei…1.76:14.5:1
#000000
#00376B
Fail
span Fakultäten21.00:14.5:1
#000000
#FFFFFF
Pass
button Schließen21.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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 27 passed
REVIEW
84

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 child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English div.o-brand--gradient > div.row > div.columns > a.show-for-small-only

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.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot
div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot
div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot
div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot
div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot
div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot div.c-introduction--gradient > div.c-introduction-slider__controls > div#dots > button.dot

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
figure.c-figure > div.flex-video > div.embed-responsive > iframe.embed-responsive-item figure.c-figure > div.flex-video > div.embed-responsive > iframe.embed-responsive-item

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.

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
div.c-introduction--gradient > div.c-introduction-slider__controls > div.c-introduction-slider__navigation > button.c-introduction-slider__prev div.c-introduction--gradient > div.c-introduction-slider__controls > div.c-introduction-slider__navigation > button.c-introduction-slider__prev
div.c-introduction--gradient > div.c-introduction-slider__controls > div.c-introduction-slider__navigation > button.c-introduction-slider__status div.c-introduction--gradient > div.c-introduction-slider__controls > div.c-introduction-slider__navigation > button.c-introduction-slider__status
div.c-introduction--gradient > div.c-introduction-slider__controls > div.c-introduction-slider__navigation > button.c-introduction-slider__next div.c-introduction--gradient > div.c-introduction-slider__controls > div.c-introduction-slider__navigation > button.c-introduction-slider__next

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
●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
●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
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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
○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.
○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.
A
Alt Text Quality
1 of 67 images have issues
PASS
1 of 67 images have issues
Warning::
1 image(s) with filename as alt text
Info::
6 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
58 image(s) with good alt text
67 images 58 good alt text 2 decorative 1 generic
IssueCount
filename1 image(s)
too long6 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="tx_t3luhunisearch_search[input_name_searchstring]">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-opencheckboxSuche öffnenaria-label
tx_t3luhunisearch_search[input_name_searchstring]text(Suche)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="tx_t3luhunisearch_search[input_name_searchstring]">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback