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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-khe168
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://uni-stuttgart.de/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://uni-stuttgart.de/manifest.json

Manifest contains invalid JSON.

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::
3 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 3 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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 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
Heading Hierarchy
35 headings
REVIEW
35 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Suche
  • H2 Informationen für
  • H3 Forschung
  • H3 Studium
  • H3 Karriere
  • H3 Über uns
  • H2 Aktuelles
  • H3 Quantenforschung stärken, Talente fördern: Weitere 4,5 Millionen Euro für Graduiertenschule
  • H3 Quantenrepeater auf dem Weg aus dem Labor in die Praxis
  • H3 Zwei Nachwuchspreise für digitale Innovationen im Bauwesen
  • H3 Nachhaltige Versorgung mit Rohstoffen
  • H3 Glow up our campus!
  • H3 Maschinenbau und Architektur erneut international hoch bewertet
  • H2 Veranstaltungstipps
  • H3 Girls' Day
  • H3 IntCDC Spring Conference 2026
  • H3 Der russische Angriffskrieg gegen die Ukraine. Historische Hintergründe und politische Folgen.
  • H2 Spitzenforschung an der Universität Stuttgart
  • H3 Aerospace Technologies
  • H3 Architecture and Adaptive Buildings
  • H3 Biomedical Systems and Robotics for Health
  • H3 Digital Humanities and Societies
  • H3 Production Technologies
  • H3 Quantum Technologies
  • H3 Simulation Science
  • H3 Neues aus der Forschung: Publikationen kompakt
  • H3 Podcast: Made in Science
  • H3 Universität
  • H3 Forschung
  • H3 Studieren an der Universität Stuttgart
  • H3 Wissens- und Technologietransfer
  • H3 Zielgruppe
  • H3 Formalia
  • H3 Services
  • H3 Organisation

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

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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
h2 Suche
1.22:1
#000000
on
#1E1A18
needs 3.0:1 (large text)
24px · above the fold · over background image/gradient

1 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
h2 Suche1.22:13.0:1
#000000
#1E1A18
Fail
h2 Informationen für18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Aktuelles18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Veranstaltungstipps18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Spitzenforschung an …18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Forschung18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Studium18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Karriere18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Über uns18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Quantenforschung st…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Quantenrepeater auf …18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Zwei Nachwuchspreise…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Nachhaltige Versorgu…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Glow up our campus!18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Maschinenbau und Arc…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Girls' Day18.10:13.0:1
#000000
#EEEEEE
Pass
h3 IntCDC Spring Confer…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Der russische Angrif…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Aerospace Technologi…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Architecture and Ada…18.10:13.0:1
#000000
#EEEEEE
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
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
6 image(s) with alt text over 125 characters
Info::
14 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
34 images 14 good alt text 14 decorative
IssueCount
too long6 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
#global-searchsearchSuchefor/id
inputsubmitStarte Suchearia-label
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 23 passed
PASS
92

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
[Fotos: Universität Stuttgart / Uli Regenscheit, o. A., o. A., o. A.] div.row > div.st_extended > p > small
o. A. div.st_extended > p > small > abbr
o. A. div.st_extended > p > small > abbr
o. A. div.st_extended > p > small > abbr
[Fotos: NASA, Unsplash, ICD/ITKE/IntCDC, Universität Stuttgart / Roland Halbe, … div.row > div.st_extended > p > small
[Fotos: Arizona State University, Biodesign Institute / Jason Drees , Canva] div.col-md-12 > div.b-teaser > p > small

These are opportunities to improve the legibility of your content.

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
Slider pausieren / wieder anstoßen div.isnt-overflow > div.c-slider--default > div.slider__pagination > button.slider__playpause

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
●Buttons have an accessible name
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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
○`[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.
○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.
○Identical links have the same purpose.
○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