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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Heading Hierarchy
Action
25 headings, 4 skip(s)
FIX
25 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Studierenden Service Point (SSP) eröffnet - Neue zentrale Anlaufstelle für Studierende und Studieninteressierte
  • H2 Dialog von Tanz und Forschung: Friedemann Vogel erhält Verdienstorden des Landes Baden-Württemberg
  • H2 Wegweiser zum Studienanfang - Herzlich willkommen an der Universität Tübingen!
  • H2 Wer zu viel Süßes oder Fettiges isst, verändert schon nach wenigen Tagen die Hungerregulation im Gehirn
  • H1 DIE UNI TÜBINGEN: INNOVATIV. INTERDISZIPLINÄR. INTERNATIONAL.
  • H2 News
  • H4 21. Mediendozentur: Die neue Weltunordnung skipped
  • H4 Steinzeitlicher Steinbruch: Bereits vor 220.000 Jahren bauten Menschen in Südafrika gezielt Rohstoffe ab
  • H4 Der Tübinger Theologe Eilert Herms erhält den Erwin-Stein-Preis
  • H2 Termine
  • H6 Öffentlichkeit im Umbruch: Wie Medien Markt und Miteinander verändern skipped
  • H6 Emotion als epidemische Marker geteilter Rationalität
  • H6 Über das Vergessen
  • H2 WELCHER STUDIENGANG PASST ZU MIR?
  • H2 THEMEN DER UNIVERSITÄT
  • H5 Exzellenzstrategie skipped
  • H5 Internationalität
  • H5 Forschungsstandort
  • H5 Innovation
  • H2 ZAHLEN UND FAKTEN
  • H6 Service skipped
  • H6 Weitere Angebote
  • H6 Portale
  • H6 Kontaktinfo
  • H2 Datenschutzeinstellungen

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

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

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

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

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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::
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
19 landmarks
REVIEW
19 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
3 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 "Bereiche überspringen" 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

C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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 Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 3 pass AA only
title Startseite | Universität Tübingen
1.32:1
#000000
on
#1B2329
needs 4.5:1 (normal text)
16px · top of page (header area)
a Direkt zur Hauptnavigation
2.46:1
#000000
on
#484D51
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Leichte Sprache
3.30:1
#000000
on
#5C6062
needs 4.5:1 (normal text)
16px · above the fold
a Gebärdensprache
3.39:1
#000000
on
#5D6263
needs 4.5:1 (normal text)
16px · above the fold
a Uni A-Z
4.20:1
#000000
on
#6B7074
needs 4.5:1 (normal text)
16px · above the fold
a Kontakt
3.70:1
#000000
on
#5F6870
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 DIE UNI TÜBINGEN: I…6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Studierenden Service…6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Dialog von Tanz und …6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Wegweiser zum Studie…6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Wer zu viel Süßes …6.25:13.0:1
#000000
#8C8C8C
Pass
h2 News6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Termine6.25:13.0:1
#000000
#8C8C8C
Pass
h2 WELCHER STUDIENGANG …6.25:13.0:1
#000000
#8C8C8C
Pass
h2 THEMEN DER UNIVERSIT…6.25:13.0:1
#000000
#8C8C8C
Pass
h2 ZAHLEN UND FAKTEN6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Datenschutzeinstellu…6.25:13.0:1
#000000
#8C8C8C
Pass
title Startseite | Univers…1.32:14.5:1
#000000
#1B2329
Fail
a Direkt zur Hauptnavi…2.46:14.5:1
#000000
#484D51
Fail
a Direkt zum Inhalt6.25:14.5:1
#000000
#8C8C8C
Pass
a Direkt zur Fußleist…6.25:14.5:1
#000000
#8C8C8C
Pass
a Direkt zur Suche6.25:14.5:1
#000000
#8C8C8C
Pass
a Leichte Sprache3.30:14.5:1
#000000
#5C6062
Fail
a Gebärdensprache3.39:14.5:1
#000000
#5D6263
Fail
a Uni A-Z4.20:14.5:1
#000000
#6B7074
Fail
a Kontakt3.70:14.5:1
#000000
#5F6870
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 88/100 — 4 failing, 27 passed
REVIEW
88

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.ut-switchbar__list > li#switchbar-search > div#switchblock-search > span.ut-switchblock__close-icon ul.ut-switchbar__list > li#switchbar-search > div#switchblock-search > span.ut-switchblock__close-icon
ul.ut-switchbar__list > li#switchbar-login > div#switchblock-login > span.ut-switchblock__close-icon ul.ut-switchbar__list > li#switchbar-login > div#switchblock-login > span.ut-switchblock__close-icon
ul.ut-switchbar__list > li#switchbar-language > div#switchblock-language > span.ut-switchblock__close-icon ul.ut-switchbar__list > li#switchbar-language > div#switchblock-language > span.ut-switchblock__close-icon

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
nav.ut-page-header__switch > ul.ut-switchbar__list > li#switchbar-search > button#ut-identifier--search-toggle nav.ut-page-header__switch > ul.ut-switchbar__list > li#switchbar-search > button#ut-identifier--search-toggle
nav.ut-page-header__switch > ul.ut-switchbar__list > li#switchbar-login > button.ut-switchbar__toggle nav.ut-page-header__switch > ul.ut-switchbar__list > li#switchbar-login > button.ut-switchbar__toggle
nav.ut-page-header__switch > ul.ut-switchbar__list > li#switchbar-language > button.ut-switchbar__toggle nav.ut-page-header__switch > ul.ut-switchbar__list > li#switchbar-language > button.ut-switchbar__toggle

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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.in2-modal > div.in2-modal-flexline > div.in2-modal-reset > input#in2-modal-checkbox-essential div.in2-modal > div.in2-modal-flexline > div.in2-modal-reset > input#in2-modal-checkbox-essential
div.in2-modal > div.in2-modal-flexline > div.in2-modal-reset > input#in2-modal-checkbox-external div.in2-modal > div.in2-modal-flexline > div.in2-modal-reset > input#in2-modal-checkbox-external
Alle akzeptieren div.in2-modal__blackbox > div.in2-modal > div.in2-modal-spacing > button.in2-modal-reset
Speichern & schließen div.in2-modal__blackbox > div.in2-modal > div.in2-modal-spacing > button.in2-modal-reset
Essentiell div.in2-modal__blackbox > div.in2-modal > dl.in2-modal-accordion > dt.in2-modal-accordion__title
Videos div.in2-modal__blackbox > div.in2-modal > dl.in2-modal-accordion > dt.in2-modal-accordion__title
Impressum div.in2-modal__blackbox > div.in2-modal > div.in2-modal-flexline > a.in2-modal-link
Datenschutzerklärung div.in2-modal__blackbox > div.in2-modal > div.in2-modal-flexline > a.in2-modal-link

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
21. Mediendozentur: Die neue Weltunordnung a.ut-news-item__link > div.ut-news-item > div.ut-news-item__content > h4.ut-heading
Öffentlichkeit im Umbruch: Wie Medien Markt und Miteinander verändern a.ut-news-item__link > div.ut-news-item > div.ut-news-item__content > h6.ut-heading
Exzellenzstrategie div#c1658961 > div.ut-text-media__contentcontainer > div.ut-box__block > h5.ut-heading
Service div.ut-grid__col-1 > div#footerpanel-1 > div#footerpanel-1-ph > h6.ut-heading

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]` 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.
●Select elements have associated label elements.
●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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
3 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
11 images 8 good alt text 3 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchsearchSuchanfrage eingebenaria-label
#usertextBenutzername eingebenaria-label
#passwordpasswordPasswort eingebenaria-label
#fieldsOfStudyselectIch interessiere mich fürfor/id
#facultiesselectin der Fakultätfor/id
#in2-modal-checkbox-essentialcheckboxEssentiellfor/id
#in2-modal-checkbox-externalcheckboxVideosfor/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Error | Universität Tübingen ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback