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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 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-bobyf8
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
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://uni-mainz.de/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://uni-mainz.de/manifest.json

Manifest contains invalid JSON.

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::
2 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 2 <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.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 7 failing, 21 passed
FIX
68

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.contact-col > div.jgu_link > a.jgu_link_inner > span.jgu_button div.contact-col > div.jgu_link > a.jgu_link_inner > span.jgu_button

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#nuka-carousel > div.nuka-slide-container > div.slider-controls > button.pagination-arrow div#nuka-carousel > div.nuka-slide-container > div.slider-controls > button.pagination-arrow
dialog.jgu-filter-mobile-modal > form#jgu_filter_form > div.fields > button.jgu-btn dialog.jgu-filter-mobile-modal > form#jgu_filter_form > div.fields > button.jgu-btn
dialog.jgu-filter-mobile-modal > form#jgu_filter_form > div.fields > button.jgu-btn dialog.jgu-filter-mobile-modal > form#jgu_filter_form > div.fields > button.jgu-btn

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.image > figure.jgu-image > div.jgu-image-wrapper > img div.image > figure.jgu-image > div.jgu-image-wrapper > img
div.image > figure.jgu-image > div.jgu-image-wrapper > img div.image > figure.jgu-image > div.jgu-image-wrapper > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.jgu-input-select > div.control > div.value-container > input#react-select-2-input div.jgu-input-select > div.control > div.value-container > input#react-select-2-input
div.jgu-input-select > div.control > div.value-container > input#react-select-3-input div.jgu-input-select > div.control > div.value-container > input#react-select-3-input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bachelor of Arts Bachelor of Arts (Ein-Fach-Bachelor) Bachelor of Arts (Zwei-Fä… div.fields > div.field > div.jgu_filter_select > select.hide_a11y
Gesellschafts- und Sozialwissenschaften Ingenieurwissenschaften Kunst, Musik, D… div.fields > div.field > div.jgu_filter_select > select.hide_a11y
weiterführend grundständig div.fields > div.field > div.jgu_filter_select > select.hide_a11y
Bachelor of Arts Bachelor of Arts (Ein-Fach-Bachelor) Bachelor of Arts (Zwei-Fä… div.fields > div.field > div.jgu_filter_select > select.hide_a11y
Gesellschafts- und Sozialwissenschaften Ingenieurwissenschaften Kunst, Musik, D… div.fields > div.field > div.jgu_filter_select > select.hide_a11y
weiterführend grundständig div.fields > div.field > div.jgu_filter_select > select.hide_a11y

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
mehr erfahren div.tb-box-content > a.jgu-teaserbox-content > div.jrc-tc-bottom > span.hover-text

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
Campusplan Universität div.jgu_link > a.jgu_link_inner > span.text > a
Leitbild der JGU ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Leitbild der JGU div.jgu_link > a.jgu_link_inner > span.text > a
Zahlen & Fakten ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Zahlen & Fakten div.jgu_link > a.jgu_link_inner > span.text > a
Personensuche ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Personensuche div.jgu_link > a.jgu_link_inner > span.text > a
Pressemitteilungen ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Pressemitteilungen div.jgu_link > a.jgu_link_inner > span.text > a
JGU-Magazin ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
JGU-Magazin div.jgu_link > a.jgu_link_inner > span.text > a
Botanischer Garten ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Botanischer Garten div.jgu_link > a.jgu_link_inner > span.text > a
Collegium musicum ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Collegium musicum div.jgu_link > a.jgu_link_inner > span.text > a
Schule des Sehens ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Schule des Sehens div.jgu_link > a.jgu_link_inner > span.text > a
junior campus mainz ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
junior campus mainz div.jgu_link > a.jgu_link_inner > span.text > a
Studieren 50 Plus ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Studieren 50 Plus div.jgu_link > a.jgu_link_inner > span.text > a
Kontakt ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Kontakt div.jgu_link > a.jgu_link_inner > span.text > a
Impressum ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Impressum div.jgu_link > a.jgu_link_inner > span.text > a
Datenschutz ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Datenschutz div.jgu_link > a.jgu_link_inner > span.text > a
Leichte Sprache ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Leichte Sprache div.jgu_link > a.jgu_link_inner > span.text > a
Barrierefreiheit ul.jgu_links > li > div.jgu_link > a.jgu_link_inner
Barrierefreiheit div.jgu_link > a.jgu_link_inner > span.text > a
Johannes Gutenberg-Universität Mainz div.row > div.padding-top > div.jgu_link > a.jgu_link_inner
Johannes Gutenberg-Universität Mainz div.jgu_link > a.jgu_link_inner > span.text > a

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-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
●`[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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
○`[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
○`<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
○Links are distinguishable without relying on color.
○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.
○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.
B
Heading Hierarchy
4 headings
REVIEW
4 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Exzellente ForschungErfolg durch Profilbildung
  • H2 StudiengangsfinderWelcher Studiengang passt zu mir?
  • H2 Studiengänge filtern
  • H2 Kooperationen und Partner

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

C
Alt Text Quality
Action
7 of 24 images have issues
REVIEW
7 of 24 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with alt text over 125 characters
Info::
11 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
24 images 4 good alt text 11 decorative 7 missing
IssueCount
missing7 image(s)
too long2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Form Accessibility
Action
8 of 9 controls have issues
REVIEW
8 of 9 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input id="react-select-2-input">; <input id="react-select-3-input">; <select name="degree">; <input name="degree-search">; <select name="faechergruppen">; <input name="faechergruppen-search">; <select name="studyType">; <input name="studyType-search">
Info::
1 control(s) properly labeled
9 controls
1 labeled
0 placeholder only
8 unlabeled
ControlTypeLabelMethod
#jgu_filter_searchsearchSuchenfor/id
#react-select-3-inputinput(none)none
#react-select-2-inputinput(none)none
degreeselect(none)none
degree-searchinput(none)none
faechergruppenselect(none)none
faechergruppen-searchinput(none)none
studyTypeselect(none)none
studyType-searchinput(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input id="react-select-2-input">; <input id="react-select-3-input">; <select name="degree">; <input name="degree-search">; <select name="faechergruppen">; <input name="faechergruppen-search">; <select name="studyType">; <input name="studyType-search">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Quicklinks" MAIN CONTENTINFO footer

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

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
title Johannes Gutenberg-U…21.00:14.5:1
#000000
#FFFFFF
Pass
span Hauptmenü21.00:14.5:1
#000000
#FFFFFF
Pass
span Suche21.00:14.5:1
#000000
#FFFFFF
Pass
span Sprache21.00:14.5:1
#000000
#FFFFFF
Pass
p Foto: Alexander Grie…21.00:14.5:1
#000000
#FFFFFF
Pass
span Video abspielen21.00:14.5:1
#000000
#FFFFFF
Pass
span Forschungsprofil21.00:14.5:1
#000000
#FFFFFF
Pass
div Internationale Spitz…21.00:14.5:1
#000000
#FFFFFF
Pass
span mehr erfahren21.00:14.5:1
#000000
#FFFFFF
Pass
p Foto: Christian Gro…21.00:14.5:1
#000000
#FFFFFF
Pass
span Rhein-Main-Universit…21.00:14.5:1
#000000
#FFFFFF
Pass
div Die strategische All…21.00:14.5:1
#000000
#FFFFFF
Pass
span mehr erfahren21.00:14.5:1
#000000
#FFFFFF
Pass
p Foto: Alexander Sell21.00:14.5:1
#000000
#FFFFFF
Pass
span Im Fokus21.00:14.5:1
#000000
#FFFFFF
Pass
div JGU on tour – Exku…21.00:14.5:1
#000000
#FFFFFF
Pass
span mehr erfahren21.00:14.5:1
#000000
#FFFFFF
Pass
p © mindjazz pictures21.00:14.5:1
#000000
#FFFFFF
Pass
span JGU-Magazin21.00:14.5:1
#000000
#FFFFFF
Pass
div Vom Hörsaal auf die…21.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.

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

Send Feedback