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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
8
PASS
1
INFO
0
Checks
13
1 PASS 8 REVIEW 4 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 (missing!) ASIDE CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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: #13306a
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
2 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search
Skip Link
Labeled Navigation 2 <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
Heading Hierarchy
20 headings
REVIEW
20 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 CampusPost
  • H2 Aktuelle Meldungen
  • H2 Frontiers Planet Prize: Göttinger Biodiversitätsforscher ist „National Champion“
  • H2 „Beharrlich. Kritisch. Unverzichtbar!“
  • H2 Auszeichnung für Forstwissenschaftler
  • H2 „Doppelspalt“-Experiment enthüllt verborgene Details zwischen Licht und Materie
  • H2 Auszeichnung für Agrarökologen
  • H2 Feierliche Einweihung: XLAB Stiftung eröffnet Begegnungszentrum
  • H2 Veranstaltungskalender
  • H2 23.04.2026
  • H2 23.04.2026
  • H2 23.04.2026
  • H2 23.04.2026
  • H2 24.04.2026
  • H2 24.04.2026
  • H2 Weitere Termine
  • H3 Kontakt
  • H3 Soziale Medien
  • H3 Online-Dienste
  • H3 Service

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
Form Accessibility
Action
5 of 7 controls have issues
REVIEW
5 of 7 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="query" id="search-mobile">; <input type="radio" name="searchengineRadio" id="googleRadioMobile">; <input type="radio" name="searchengineRadio" id="meiliRadioMobile">; <input type="text" name="query" id="search-mobile">; <input type="radio" name="searchengineRadio" id="meiliRadio">
Info::
2 control(s) properly labeled
7 controls
2 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#searchtextSuchbegrifffor/id
#googleRadioradioMit Google™ suchenfor/id
#meiliRadioMobileradio(none)none
#search-mobiletext(none)none
#search-mobiletext(none)none
#googleRadioMobileradio(none)none
#meiliRadioradio(none)none

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

<input type="text" name="query" id="search-mobile">; <input type="radio" name="searchengineRadio" id="googleRadioMobile">; <input type="radio" name="searchengineRadio" id="meiliRadioMobile">; <input type="text" name="query" id="search-mobile">; <input type="radio" name="searchengineRadio" id="meiliRadio">

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

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 404 Not Found – 🙈 - Georg-August-Universität Göttingen Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Universität Göttingen
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Universität Göttingen 192×192 icon 512×512 icon Start URL Display Mode standalone
Name Universität Göttingen Display Mode standalone Theme Color #13306a Background Color #13306a Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 CampusPost
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aktuelle Meldungen
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frontiers Planet Prize: Göttinger Biodi…
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 „Beharrlich. Kritisch. Unverzichtbar!…
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Auszeichnung für Forstwissenschaftler
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 „Doppelspalt“-Experiment enthüllt v…
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Auszeichnung für Agrarökologen
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Feierliche Einweihung: XLAB Stiftung er…
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Veranstaltungskalender
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 23.04.2026
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 23.04.2026
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 23.04.2026
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 23.04.2026
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 24.04.2026
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 24.04.2026
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Weitere Termine
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Kontakt
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Soziale Medien
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Online-Dienste
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Service
1.66:1
#000000
on
#13306A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 CampusPost1.66:13.0:1
#000000
#13306A
Fail
h2 Aktuelle Meldungen1.66:13.0:1
#000000
#13306A
Fail
h2 Frontiers Planet Pri…1.66:13.0:1
#000000
#13306A
Fail
h2 „Beharrlich. Kriti…1.66:13.0:1
#000000
#13306A
Fail
h2 Auszeichnung für Fo…1.66:13.0:1
#000000
#13306A
Fail
h2 „Doppelspalt“-Ex…1.66:13.0:1
#000000
#13306A
Fail
h2 Auszeichnung für Ag…1.66:13.0:1
#000000
#13306A
Fail
h2 Feierliche Einweihun…1.66:13.0:1
#000000
#13306A
Fail
h2 Veranstaltungskalend…1.66:13.0:1
#000000
#13306A
Fail
h2 23.04.20261.66:13.0:1
#000000
#13306A
Fail
h2 23.04.20261.66:13.0:1
#000000
#13306A
Fail
h2 23.04.20261.66:13.0:1
#000000
#13306A
Fail
h2 23.04.20261.66:13.0:1
#000000
#13306A
Fail
h2 24.04.20261.66:13.0:1
#000000
#13306A
Fail
h2 24.04.20261.66:13.0:1
#000000
#13306A
Fail
h2 Weitere Termine1.66:13.0:1
#000000
#13306A
Fail
h3 Kontakt1.66:13.0:1
#000000
#13306A
Fail
h3 Soziale Medien1.66:13.0:1
#000000
#13306A
Fail
h3 Online-Dienste1.66:13.0:1
#000000
#13306A
Fail
h3 Service1.66:13.0:1
#000000
#13306A
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 80/100 — 5 failing, 23 passed
REVIEW
80

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 parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Öffentliche Ringvorlesung: Lachen in Krisenzeiten Sommersemester 2026 div#page-showcase > section.row > div#gcms-slider > div.carousel-inner

When an input field 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 more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Öffentliche Ringvorlesung: Lachen in Krisenzeiten Sommersemester 2026 div#page-showcase > section.row > div#gcms-slider > div.carousel-inner

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

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
form.search-form > div.form-group > div.input-group > input#search-mobile form.search-form > div.form-group > div.input-group > input#search-mobile
li > form.search-form > div.form-check > input#googleRadioMobile li > form.search-form > div.form-check > input#googleRadioMobile
li > form.search-form > div.form-check > input#meiliRadioMobile li > form.search-form > div.form-check > input#meiliRadioMobile

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-sm-6 > ul#social-buttons > li > a.facebook div.col-sm-6 > ul#social-buttons > li > a.facebook
div.col-sm-6 > ul#social-buttons > li > a.instagram div.col-sm-6 > ul#social-buttons > li > a.instagram
div.col-sm-6 > ul#social-buttons > li > a.bluesky div.col-sm-6 > ul#social-buttons > li > a.bluesky
div.col-sm-6 > ul#social-buttons > li > a.mastodon div.col-sm-6 > ul#social-buttons > li > a.mastodon
div.col-sm-6 > ul#social-buttons > li > a.youtube div.col-sm-6 > ul#social-buttons > li > a.youtube
div.col-sm-6 > ul#social-buttons > li > a.linkedin div.col-sm-6 > ul#social-buttons > li > a.linkedin

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
`button`, `link`, and `menuitem` elements have accessible names
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
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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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
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.
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.
A+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
5 decorative image(s) correctly marked
Info::
41 image(s) with good alt text
47 images 41 good alt text 5 decorative
IssueCount
too long1 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback