Skip to content
https://uibk.ac.at

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
7 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 7 <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
25 landmarks
REVIEW
25 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
2 of 7 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Global" SEARCH 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

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
Alt Text Quality
Action
14 of 17 images have issues
REVIEW
14 of 17 images have issues
Critical::
13 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
3 image(s) with good alt text
17 images 3 good alt text 1 generic 13 missing
IssueCount
missing13 image(s)
generic1 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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 25 passed
REVIEW
83

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

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.col-12 > div#cascadeelement_id-18595595 > form.position-relative > button.btn div.col-12 > div#cascadeelement_id-18595595 > form.position-relative > button.btn
div#uibk-credits > div.row > div.col-12 > button#uibk-toggle-crd-list div#uibk-credits > div.row > div.col-12 > button#uibk-toggle-crd-list

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.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100
div.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100
div.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100
div.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100
div.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100
div.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100
div.col > div.card > picture > img.w-100 div.col > div.card > picture > img.w-100

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-12 > div.uibk-main-content > div#cascadeelement_id-18595587 > a.uibk-copyright div.col-12 > div.uibk-main-content > div#cascadeelement_id-18595587 > a.uibk-copyright
div#studieren > div.col-12 > div#cascadeelement_id-18595595 > a.uibk-copyright div#studieren > div.col-12 > div#cascadeelement_id-18595595 > a.uibk-copyright
div#uibk-feed-18595618 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595618 > div.col > div.card > a.uibk-copyright
div.row > div.col-12 > figure#uibk-figure-18595626 > a.uibk-copyright div.row > div.col-12 > figure#uibk-figure-18595626 > a.uibk-copyright
div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright
div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright
div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright
div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright
div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright
div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright div#uibk-feed-18595676 > div.col > div.card > a.uibk-copyright
div.row > div.col-12 > div#cascadeelement_id-18595701 > a.uibk-copyright div.row > div.col-12 > div#cascadeelement_id-18595701 > a.uibk-copyright
div.row > div.col-12 > div#cascadeelement_id-18595709 > a.uibk-copyright div.row > div.col-12 > div#cascadeelement_id-18595709 > a.uibk-copyright
div.row > div.col-12 > div#cascadeelement_id-18595713 > a.uibk-copyright div.row > div.col-12 > div#cascadeelement_id-18595713 > a.uibk-copyright
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > a
div.col-12 > ul.socialmedia > li > a div.col-12 > ul.socialmedia > li > 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
div.col-12 > div.uibk-main-content > div#cascadeelement_id-18595587 > a.uibk-copyright div.col-12 > div.uibk-main-content > div#cascadeelement_id-18595587 > a.uibk-copyright

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Bildinfo div.col-12 > div.uibk-main-content > div#uibk-mainimage-description > button.uibk-nav-btn-open
○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
●Form elements have associated labels
●`[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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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
○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
○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
○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.
○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
40 headings
PASS
40 headings
Info::
Single H1 present
  • H1 Universität Innsbruck entdecken
  • H2 Webseitensuche
  • H2 Personensuche
  • H2 Quicklinks
  • H2 Wir bauen Brücken in die Zukunft ...
  • H2 Studieren
  • H3 Suchergebnisse
  • H2 Entdecken
  • H2 „Wir for­schen für die Menschen“
  • H2 Mehr­fach­krise gefähr­det Lebens­grund­la­gen
  • H2 Neu­be­ru­fe­nen­fest­akt und Habi­li­ta­ti­ons­feier
  • H3 Lange Nacht der Forschung 2026
  • H2 Forschen
  • H3 Alpiner Raum
  • H3 Biowissenschaften
  • H3 Digital Science
  • H3 Material- und Nanowissenschaften
  • H3 Kulturen
  • H3 Physik
  • H3 Scientific Computing
  • H3 Wirtschaft, Politik & Gesellschaft
  • H3 Geschlechterforschung
  • H2 Mitgestalten
  • H3 Lernen Sie Ihre künftigen Kolleg:innen kennen
  • H2 Ursula Scholl-Gris­se­mann
  • H2 Ste­fa­nie Möss­ler
  • H2 Ger­hard Moser
  • H2 Dirk H. Rup­now
  • H2 Daniela Kir­cher
  • H2 Mar­cel Sei­del
  • H2 Mar­tin Ring­bauer
  • H2 Eca­te­rina Sava-Huss
  • H2 Lisa-Maria Pflei­de­rer
  • H2 Andreas Stein­mayr
  • H2 Anne Hecks­te­den
  • H2 Alex­an­dra Brun­ner-Schwai­ger
  • H2 Universität
  • H3 Informationen für
  • H3 Newsletter
  • H3 Im Fokus
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#uibk-website-searchsearchSuchbegrifffor/id
lnamesearchNachnamearia-label
fnamesearchVornamearia-label
inputtext(Suchbegriff)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /static/uniweb/css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /static/uniweb/css/print.css ✓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
h2 Webseitensuche21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Personensuche21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Quicklinks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wir bauen Brücken i…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Studieren21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Entdecken21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Forschen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mitgestalten21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Universität21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Suchergebnisse21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lernen Sie Ihre kün…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Informationen für21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Newsletter21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Im Fokus21.00:13.0:1
#000000
#FFFFFF
Pass
title Universität Innsbru…21.00:14.5:1
#000000
#FFFFFF
Pass
span Suche21.00:14.5:1
#000000
#FFFFFF
Pass
span Quicklinks21.00:14.5:1
#000000
#FFFFFF
Pass
span Navigation21.00:14.5:1
#000000
#FFFFFF
Pass
span Universität Innsbru…21.00:14.5:1
#000000
#FFFFFF
Pass
label Suchbegriff21.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