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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 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.

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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 5 <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
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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 ASIDE 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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Seite nicht gefunden ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 25 passed
REVIEW
85

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
© Fotos: A. Decaix, ANR SWEED und Mission „Boyuk Kesik“ & ANR KUR(A)GAN Was im … div.news-items > div.slick-list > div.slick-track > div.news_item
© BZH Mittwoch 22.04.2026 Prüfungsangst verstehen und wirksam vorbeugen Quantiu… div.news-items > div.slick-list > div.slick-track > div.news_item

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.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-prev div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-prev
div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-next div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-next
div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-prev div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-prev
div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-next div.tile-content > div.slider-navigation-wrapper > div.slider-navigation > button.slick-next

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.

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
© BZH a > div.img > div.copyright-container > span.copyright
Mittwoch a > div.img > div.content > span.day-name
22.04.2026 a > div.img > div.content > span.date
© U7 div#1qwpg5bjckuk > div.tile-content > div.image-subtitle > span
© U15 div#ypughi5p03ff > div.tile-content > div.image-subtitle > span
© BORA div#o5t8g2i25hg5 > div.tile-content > div.image-subtitle > span
© HRK div#ng57q4a8d8d6 > div.tile-content > div.image-subtitle > span
© Stifterverband div#ym1ckujl9t9s > div.tile-content > div.image-subtitle > span
© berufundfamilie div#vdipn4eixddd > div.tile-content > div.image-subtitle > span
EMPFOHLENE LINKS div.container > div.row > div.col-sm-6 > span.header

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
acht Exzellenzclustern div.tile-content > div > p > a.a-theme
Exzellenzuniversität div.tile-content > div > p > a.a-theme
junge Talente div.tile-content > div > p > a.a-theme
emerging leaders div.tile-content > div > p > a.a-theme
#WeAreUniBonn div#y5zusjfg6f7o > div.tile-content > p > a.a-theme

These are opportunities to improve the legibility of your content.

○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
●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
●`[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
●`<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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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
●Elements with visible text labels have matching accessible names.
○`[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 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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○Identical links have the same purpose.
○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+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 Forschen und Studieren an der Exzellenzuniversität Bonn
  • H2 We are Uni Bonn!
  • H3 Angkana Rüland
  • H3 Cyrill Stachniss
  • H3 Jaqueline Lorenzen
  • H3 Dominik Bach
  • H2 Mehr von der Universität Bonn
  • H3 Solidarität mit der Ukraine
  • H3 360-Grad-Tour durch die Uni
  • H3 Spitzenforschung
  • H3 Netzwerke und Zertifikate
  • H2 Links
A+
Alt Text Quality
1 of 10 images have issues
PASS
1 of 10 images have issues
Warning::
1 image(s) with filename as alt text
Info::
9 image(s) with good alt text
10 images 9 good alt text 1 generic
IssueCount
filename1 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
SearchableTexttextSearcharia-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
h1 Forschen und Studier…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We are Uni Bonn!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mehr von der Univers…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Angkana Rüland21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cyrill Stachniss21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Jaqueline Lorenzen21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Dominik Bach21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Solidarität mit der…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 360-Grad-Tour durch …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Spitzenforschung21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Netzwerke und21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Zertifikate21.00:13.0:1
#000000
#FFFFFF
Pass
title Universität Bonn21.00:14.5:1
#000000
#FFFFFF
Pass
a Universität21.00:14.5:1
#000000
#FFFFFF
Pass
a Studium21.00:14.5:1
#000000
#FFFFFF
Pass
a Forschung und Lehre10.74:14.5:1
#000000
#BAB9BA
Pass
a International10.74:14.5:1
#000000
#BAB9BA
Pass
div Fettzellen und Essve…10.74:14.5:1
#000000
#BAB9BA
Pass
div Forschende aus Bonn …9.49:14.5:1
#000000
#A5B0B6
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.

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

Send Feedback