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

Accessibility

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

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
19 landmarks
REVIEW
19 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 ASIDE "footerContactLabel" 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
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
qtextSuche auf Webseite mit Googlearia-label
qtextSuche auf Webseite mit Googlearia-label
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 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
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 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)
A+
Heading Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H1 Universität Würzburg
  • H2 Wissenschaft für die Gesellschaft
  • H2 Die JMU im Exzellenzwettbewerb
  • H2 Studieren an der JMU
  • H2 Karriere an der JMU
  • H2 Veranstaltungen
  • H2 Aktuelles
  • H3 RNA-Therapien: Würzburger Nanotransporter gegen Herzinfarkt
  • H3 einBLICK: Nachrichten aus der JMU
  • H3 Izatt-Christensen Award 2026 für Frank Würthner
  • H2 Studieren und Leben in Würzburg
  • H3 Studienangebot
  • H3 Dein Studium an der Uni Würzburg
  • H3 Studieren in Würzburg: Uni. Main. Zukunft.
  • H2 Stark in Forschung und Vernetzung
  • H3 Forschung
  • H3 Center for Artificial Intelligence and Data Science
  • H3 Exzellenzcluster der JMU
  • H3 Uni Würzburg startet in die finale Phase des Exzellenzwettbewerbs
  • H3 Erfolg im Exzellenzwettbewerb: Würzburger Spitzenforschung setzt sich durch
  • H3 JMU zeigt Forschungs- und Transferstärke im THE Ranking
  • H3 Bildnachweise
A+
Alt Text Quality
All 59 images OK
PASS
All 59 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
16 decorative image(s) correctly marked
Info::
41 image(s) with good alt text
59 images 41 good alt text 16 decorative
IssueCount
too long2 image(s)
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 Not found - Universität Würzburg ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /typo3temp/assets/compressed/merged-21d7f4fc9e3c117c006b7a474b70d346-67702bc64d7a3ad4028482a349dab7c5.css.gzip?1701247136
Print Stylesheet ✓ Print Optimized
Print stylesheet /typo3temp/assets/compressed/merged-21d7f4fc9e3c117c006b7a474b70d346-67702bc64d7a3ad4028482a349dab7c5.css.gzip?1701247136 ✓Inline @media print Not detected ✗
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 Universität Würzbu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wissenschaft für di…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Die JMU im Exzellenz…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Studieren an der JMU21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Karriere an der JMU21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Veranstaltungen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Studieren und Leben …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stark in Forschung u…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bildnachweise21.00:13.0:1
#000000
#FFFFFF
Pass
title Universität Würzbu…21.00:14.5:1
#000000
#FFFFFF
Pass
a Menu21.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 Forschung21.00:14.5:1
#000000
#FFFFFF
Pass
a Lehre21.00:14.5:1
#000000
#FFFFFF
Pass
a Einrichtungen21.00:14.5:1
#000000
#FFFFFF
Pass
a International21.00:14.5:1
#000000
#FFFFFF
Pass
a Universität21.00:14.5:1
#000000
#FFFFFF
Pass
a Aktuelles21.00:14.5:1
#000000
#FFFFFF
Pass
a Die JMU21.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.

A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 24 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.

Names and labels

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.csc-textpic-center-outer > div.csc-textpic-center-inner > figure.image > a div.csc-textpic-center-outer > div.csc-textpic-center-inner > figure.image > a
div.csc-textpic-center-outer > div.csc-textpic-center-inner > figure.image > a div.csc-textpic-center-outer > div.csc-textpic-center-inner > figure.image > a
div.csc-textpic-center-outer > div.csc-textpic-center-inner > figure.image > a div.csc-textpic-center-outer > div.csc-textpic-center-inner > figure.image > a

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

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
Jetzt informieren div#c447231 > ul.content-list-ul-arrow > li.bodytext > a
Jetzt bewerben und einschreiben div#c447231 > ul.content-list-ul-arrow > li.bodytext > a.internal-link

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
●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
●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
●Links are distinguishable without relying on color.
●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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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
○Buttons have an accessible name
○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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback