Skip to content
https://tu-dresden.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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: #00008c
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
h1 We are
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · mid-page
h1 collaborative.
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 News
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Calendar of Events
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Studying at TU Dresden
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Invest in the future
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Facts & figures
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Spotlight on TUD
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Popular searches
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Our Services
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Services
1.38:1
#000000
on
#00008C
needs 3.0:1 (large text)
24px · bottom of viewport
title Technische Universität Dresden — TU D…
1.38:1
#000000
on
#00008C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main navigation
1.38:1
#000000
on
#00008C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to search
4.06:1
#000000
on
#6D6D6D
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 We are1.38:13.0:1
#000000
#00008C
Fail
h1 collaborative.1.38:13.0:1
#000000
#00008C
Fail
h1 News1.38:13.0:1
#000000
#00008C
Fail
h1 Calendar of Events1.38:13.0:1
#000000
#00008C
Fail
h1 Studying at TU Dresd…1.38:13.0:1
#000000
#00008C
Fail
h1 Invest in the future1.38:13.0:1
#000000
#00008C
Fail
h1 Facts & figures1.38:13.0:1
#000000
#00008C
Fail
h1 Spotlight on TUD1.38:13.0:1
#000000
#00008C
Fail
h1 Popular searches1.38:13.0:1
#000000
#00008C
Fail
h2 Our Services1.38:13.0:1
#000000
#00008C
Fail
h2 Our Services1.38:13.0:1
#000000
#00008C
Fail
title Technische Universit…1.38:14.5:1
#000000
#00008C
Fail
a Skip to main navigat…1.38:14.5:1
#000000
#00008C
Fail
a Skip to main navigat…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to search4.06:14.5:1
#000000
#6D6D6D
Fail
a Skip to content12.17:14.5:1
#000000
#C5C5C5
Pass
span Information for21.00:14.5:1
#000000
#FFFFFF
Pass
a Prospective students21.00:14.5:1
#000000
#FFFFFF
Pass
a Students21.00:14.5:1
#000000
#FFFFFF
Pass
a Cooperation partners21.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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 22 passed
REVIEW
78

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
© TUD University of Excellence TUD has been one of Germany’s Universities of E… section.content-teaser-box > div.row > div.columns > div.teaser-box
APR 22 2026 Gewerb­liche Schutzrechte in der Praxis - Teil II - Paten­trecherch… section.event-slider > div.row > div.columns > div.owl-carousel
© AVANGA Filmproduktion VIDEO: WE ARE TUD MORE © CD BROCHURE: KNOWLEDGE FOR… div.banner-box-background > div.row > div.columns > div.owl-carousel

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
Read more University of Excellence div.owl-item > div.content-teaser-item > div.more-wrapper > a.more

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
© TUD University of Excellence TUD has been one of Germany’s Universities of E… section.content-teaser-box > div.row > div.columns > div.teaser-box
APR 22 2026 Gewerb­liche Schutzrechte in der Praxis - Teil II - Paten­trecherch… section.event-slider > div.row > div.columns > div.owl-carousel
© AVANGA Filmproduktion VIDEO: WE ARE TUD MORE © CD BROCHURE: KNOWLEDGE FOR… div.banner-box-background > div.row > div.columns > div.owl-carousel

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.

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
Read more div.columns > div.more-wrapper > a.more > span.link-icon
Read more div.columns > div.more-wrapper > a.more > span.link-icon
Read more div.columns > div.more-wrapper > a.more > span.link-icon
FACTS & FIGURES div.row > div.columns > div.float-left > h1.box-title

These are opportunities to improve the legibility of your content.

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.formatted > div.contact-block > p.tel > a.ms-text div.formatted > div.contact-block > p.tel > a.ms-text
div.formatted > div.contact-block > p > a.ms-m-href div.formatted > div.contact-block > p > a.ms-m-href

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
1 div.columns > div.teaser-box > div.owl-dots > button.owl-dot
2 div.columns > div.teaser-box > div.owl-dots > button.owl-dot
3 div.columns > div.teaser-box > div.owl-dots > button.owl-dot
4 div.columns > div.teaser-box > div.owl-dots > button.owl-dot
5 div.columns > div.teaser-box > div.owl-dots > button.owl-dot
6 div.columns > div.teaser-box > div.owl-dots > button.owl-dot
1 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot
2 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot
3 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot
4 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot
5 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot
1 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot
2 div.columns > div.owl-carousel > div.owl-dots > button.owl-dot

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
●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
●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
●`<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
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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.
○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
Landmark Structure
6 landmarks
PASS
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.
Info::
Skip navigation link present
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

A
Heading Hierarchy
13 headings
PASS
13 headings
Warning::
Multiple H1 headings (8 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 We arecollaborative.We areexcellent!
  • H1 News duplicate H1
  • H1 Calendar of Events duplicate H1
  • H1 Studying at TU Dresden duplicate H1
  • H1 Invest in the future duplicate H1
  • H1 Facts & figures duplicate H1
  • H1 Spotlight on TUD duplicate H1
  • H2 Video: We are TUD
  • H2 Brochure: Knowledge for Life
  • H1 Popular searches duplicate H1
  • H2 Campus Navigator
  • H2 Our Services
  • H2 Our Services

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Alt Text Quality
All 14 images OK
PASS
All 14 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
9 image(s) with good alt text
14 images 9 good alt text
IssueCount
too long5 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#global-searchtextSearchfor/id
inputsubmit(none)none

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

<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

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

Send Feedback