Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

Heading Hierarchy

Action

24 headings, 5 skip(s)

FIX

24 headings, 5 skip(s)

Multiple H1 headings (6 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Guten Tag!
H1 Studieren am KIT duplicate H1
H3 Forschungsorientiertes Studium skipped
H3 Studiengänge
H3 Bewerbung
H1 Der Gründungsboom ist hausgemacht duplicate H1
H3 Mehr als eine gute Idee skipped
H3 Transfer
H3 Das KIT auf der Hannover Messe
H1 Studieren am KIT duplicate H1
H3 Forschungsorientiertes Studium skipped
H3 Studiengänge
H3 Bewerbung
H1 Der Gründungsboom ist hausgemacht duplicate H1
H3 Mehr als eine gute Idee skipped
H3 Transfer
H3 Das KIT auf der Hannover Messe
H1 Aktuelles aus dem KIT duplicate H1
H2 Veranstaltungen
H4 PRANA skipped
H3 Besuchen
H3 Bewerben
H3 Presse
H3 Kontakt

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: KIT

192x192 icon present

PWA Install Criteria Not Installable

Name KIT ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗

Name KIT Icons 6 icon(s)

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #009682

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Form Accessibility

Action

32 of 59 controls have issues

REVIEW

32 of 59 controls have issues

32 control(s) without accessible label

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

Got: <input type="text" id="feedback_2026_q3_9_text">; <input type="text" id="feedback_2026_q7_2_text">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_2">; <input type="radio" name="feedback_2026_q8_2"> (+22 more)

27 control(s) properly labeled

59 controls

27 labeled

0 placeholder only

32 unlabeled

Control	Type	Label	Method
#feedback_2026_q1	select	Ich …	for/id
#feedback_2026_q2	select	Wie häufig besuchen Sie kit.edu?	for/id
#feedback_2026_q3_1	checkbox		none
#feedback_2026_q3_2	checkbox		none
#feedback_2026_q3_3	checkbox		none
#feedback_2026_q3_4	checkbox		none
#feedback_2026_q3_5	checkbox		none
#feedback_2026_q3_6	checkbox		none
#feedback_2026_q3_7	checkbox		none
#feedback_2026_q3_8	checkbox		none
#feedback_2026_q3_9	checkbox		none
#feedback_2026_q4_1	radio		none
#feedback_2026_q4_2	radio		none
#feedback_2026_q4_3	radio		none
#feedback_2026_q4_4	radio		none
#feedback_2026_q5_1	radio		none
#feedback_2026_q5_2	radio		none
#feedback_2026_q5_3	radio		none
#feedback_2026_q6_1	checkbox		none
#feedback_2026_q6_2	checkbox		none
#feedback_2026_q6_3	checkbox		none
#feedback_2026_q6_4	checkbox		none
#feedback_2026_q6_5	checkbox		none
#feedback_2026_q7_1	radio		none
#feedback_2026_q7_2	radio		none
searchquery	search	suchen	aria-label
#target-groups-search	search	suchen	aria-label
feedback_2026_q8_1	radio	(none)	none
feedback_2026_q8_1	radio	(none)	none
feedback_2026_q8_1	radio	(none)	none
feedback_2026_q8_1	radio	(none)	none
feedback_2026_q8_1	radio	(none)	none
feedback_2026_q8_1	radio	(none)	none
feedback_2026_q8_2	radio	(none)	none
feedback_2026_q8_2	radio	(none)	none
feedback_2026_q8_2	radio	(none)	none
feedback_2026_q8_2	radio	(none)	none
feedback_2026_q8_2	radio	(none)	none
feedback_2026_q8_2	radio	(none)	none
feedback_2026_q8_3	radio	(none)	none
feedback_2026_q8_3	radio	(none)	none
feedback_2026_q8_3	radio	(none)	none
feedback_2026_q8_3	radio	(none)	none
feedback_2026_q8_3	radio	(none)	none
feedback_2026_q8_3	radio	(none)	none
feedback_2026_q8_4	radio	(none)	none
feedback_2026_q8_4	radio	(none)	none
feedback_2026_q8_4	radio	(none)	none
feedback_2026_q8_4	radio	(none)	none
feedback_2026_q8_4	radio	(none)	none
feedback_2026_q8_4	radio	(none)	none
feedback_2026_q8_5	radio	(none)	none
feedback_2026_q8_5	radio	(none)	none
feedback_2026_q8_5	radio	(none)	none
feedback_2026_q8_5	radio	(none)	none
feedback_2026_q8_5	radio	(none)	none
feedback_2026_q8_5	radio	(none)	none
#feedback_2026_q3_9_text	text	(none)	none
#feedback_2026_q7_2_text	text	(none)	none

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

<input type="text" id="feedback_2026_q3_9_text">; <input type="text" id="feedback_2026_q7_2_text">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_1">; <input type="radio" name="feedback_2026_q8_2">; <input type="radio" name="feedback_2026_q8_2"> (+22 more)

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

Link & Button Quality

Action

2 issue(s) across 289 links and 87 buttons

REVIEW

2 issue(s) across 289 links and 87 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#block671

30 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: http://www.konvent.kit.edu/index.php; https://www.asta-kit.de/; https://www.giving.kit.edu/index.php; https://www.stiftung.kit.edu/; https://www.irm.kit.edu/Sponsoring.php; https://www.irm.kit.edu/engagement.php; https://www.kfg.kit.edu/index.php; https://www.200jahre.kit.edu/index.php; https://www.km.kit.edu/campusfuehrungen.php; https://www.sle.kit.edu/vorstudium/studiengaenge.php (+20 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.burger (#317 on page)

258 link(s) with descriptive text

289 links

1 empty

0 generic text

30 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
http://www.konvent.kit.edu/index.php	Konvent	new tab	Add '(opens in new tab)' to text
https://www.asta-kit.de/	Verfasste Studierendenschaft	new tab	Add '(opens in new tab)' to text
https://www.giving.kit.edu/index.php	KIT GIVING	new tab	Add '(opens in new tab)' to text
https://www.stiftung.kit.edu/	KIT-Stiftung	new tab	Add '(opens in new tab)' to text
https://www.irm.kit.edu/Sponsoring.php	Sponsoring	new tab	Add '(opens in new tab)' to text
https://www.irm.kit.edu/engagement.php	KIT-Alumni	new tab	Add '(opens in new tab)' to text
https://www.kfg.kit.edu/index.php	KFG	new tab	Add '(opens in new tab)' to text
https://www.200jahre.kit.edu/index.php	200 Jahre KIT	new tab	Add '(opens in new tab)' to text
https://www.km.kit.edu/campusfuehrungen.…	Campusführungen	new tab	Add '(opens in new tab)' to text
https://www.sle.kit.edu/vorstudium/studi…	Studiengänge	new tab	Add '(opens in new tab)' to text
https://www.sle.kit.edu/vorstudium/bewer…	Bewerbung	new tab	Add '(opens in new tab)' to text
https://www.intl.kit.edu/14011.php	Internationale Studierende	new tab	Add '(opens in new tab)' to text
https://intranet.kit.edu/index.php	Intranet	new tab	Add '(opens in new tab)' to text
https://www.khys.kit.edu/promovieren-am-…	Promovieren am KIT	new tab	Add '(opens in new tab)' to text
https://www.techtransfer.kit.edu/technol…	Technologietransfer	new tab	Add '(opens in new tab)' to text
https://www.irm.kit.edu/entrepreneurship…	Gründen	new tab	Add '(opens in new tab)' to text
https://www.pse.kit.edu/karriere/Stellen…	Stellenangebote	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.km.kit.edu/nachgefragt_11318…	Mehr erfahren	new tab	Add '(opens in new tab)' to text
https://www.kit.edu/campusplan/	Campusplan	new tab	Add '(opens in new tab)' to text
/kit/veranstaltungen.php	Veranstaltungen	new tab	Add '(opens in new tab)' to text
https://www.kit-shop.de/	KIT-Shop	new tab	Add '(opens in new tab)' to text
https://www.kit-ausbildung.de/de/offene-…	Ausbildungsplätze	new tab	Add '(opens in new tab)' to text
https://www.khys.kit.edu/informationen_p…	Promotion	new tab	Add '(opens in new tab)' to text
https://www.km.kit.edu/kitkompakt.php	Newsletter	new tab	Add '(opens in new tab)' to text
https://www.km.kit.edu/presseteam.php	Pressekontakt	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/kitkarlsruhe	Instagram Profil	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/KIT.Karlsruhe.O…	Facebook Profil	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/KITVideocli…	Youtube Profil	new tab	Add '(opens in new tab)' to text
https://social.kit.edu/@KIT_Karlsruhe	Mastodon Profil	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/kit	LinkedIn Profil	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

344 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#block671

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

http://www.konvent.kit.edu/index.php; https://www.asta-kit.de/; https://www.giving.kit.edu/index.php; https://www.stiftung.kit.edu/; https://www.irm.kit.edu/Sponsoring.php; https://www.irm.kit.edu/engagement.php; https://www.kfg.kit.edu/index.php; https://www.200jahre.kit.edu/index.php; https://www.km.kit.edu/campusfuehrungen.php; https://www.sle.kit.edu/vorstudium/studiengaenge.php (+20 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.burger (#317 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title KIT - Karlsruher Institut für Technologie ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

Action

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 82/100 — 5 failing, 21 passed

REVIEW

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.

Navigation

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `div.navigation > ul.side-widgets > li.meta > a`
Impressum `div.navigation > ul.side-widgets > li.meta > a`
Sitemap `div.navigation > ul.side-widgets > li.meta > a`

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Forschungsorientiertes Studium `div.swiper-slide > div.stage-slider-tiles > a.stage-slider-tile > h3`
Mehr als eine gute Idee `div.swiper-slide > div.stage-slider-tiles > a.stage-slider-tile > h3`
Forschungsorientiertes Studium `div.swiper-slide > div.stage-slider-tiles > a.stage-slider-tile > h3`
Mehr als eine gute Idee `div.swiper-slide > div.stage-slider-tiles > a.stage-slider-tile > h3`
PRANA `div.event-content > div.info > a > h4.h4`

These are opportunities to improve keyboard navigation in your application.

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
header.page-header > div.content-wrap > div.navigation > button.burger `header.page-header > div.content-wrap > div.navigation > button.burger`
div.dropdown > ul.navigation-breadcrumb > li.home > button `div.dropdown > ul.navigation-breadcrumb > li.home > button`
div.dropdown > ul.navigation-breadcrumb > li.home > button `div.dropdown > ul.navigation-breadcrumb > li.home > button`
div.dropdown > ul.navigation-breadcrumb > li.home > button `div.dropdown > ul.navigation-breadcrumb > li.home > button`
div.dropdown > ul.navigation-breadcrumb > li.home > button `div.dropdown > ul.navigation-breadcrumb > li.home > button`
div.dropdown > ul.navigation-breadcrumb > li.home > button `div.dropdown > ul.navigation-breadcrumb > li.home > button`
div.dropdown > ul.navigation-breadcrumb > li.home > button `div.dropdown > ul.navigation-breadcrumb > li.home > button`

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
Das KIT `div.dropdown > ul.navigation-breadcrumb > li > span`
Themen `div.dropdown > ul.navigation-breadcrumb > li > span`
Studium `div.dropdown > ul.navigation-breadcrumb > li > span`
Forschung `div.dropdown > ul.navigation-breadcrumb > li > span`
Innovation `div.dropdown > ul.navigation-breadcrumb > li > span`
Karriere `div.dropdown > ul.navigation-breadcrumb > li > span`
Home `div.navigation > ul.side-widgets > li.meta > a`
Leichte Sprache `div.navigation > ul.side-widgets > li.meta > a`
Gebärdensprache `div.navigation > ul.side-widgets > li.meta > a`
Impressum `div.navigation > ul.side-widgets > li.meta > a`
Datenschutz `div.navigation > ul.side-widgets > li.meta > a`
Barrierefreiheit `div.navigation > ul.side-widgets > li.meta > a`
Sitemap `div.navigation > ul.side-widgets > li.meta > a`
Intranet `div.navigation > ul.side-widgets > li.meta > a`
MEHR ERFAHREN `div#div_27205 > div.tilecontent > div.bottom > a.button`
MEHR ERFAHREN `div#div_27112 > div.tilecontent > div.bottom > a.button`
MEHR ERFAHREN `div#div_34313 > div.tilecontent > div.bottom > a.button`
MEHR ERFAHREN `div#div_27204 > div.tilecontent > div.bottom > a.button`
Exzellenz `div#div_31164 > p > a > strong`
Als Exzellenzuniversität stärkt das KIT seine Spitzenforschung, pflegt den inte… `section#main_content > div.content > div#div_31164 > p`
Science for Impact `div#div_31163 > p > a > strong`
Das KIT übernimmt gesellschaftliche Verantwortung und trägt zur Gestaltung eine… `section#main_content > div.content > div#div_31163 > p`

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
Go to slide 1 `main > section.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `main > section.swiper-container > div.swiper-pagination > span.swiper-pagination-bullet`
Home `div.content-wrap > ul > li > a`
Leichte Sprache `div.content-wrap > ul > li > a`
Gebärdensprache `div.content-wrap > ul > li > a`
Impressum `div.content-wrap > ul > li > a`
Datenschutz `div.content-wrap > ul > li > a`
Barrierefreiheit `div.content-wrap > ul > li > a`
Sitemap `div.content-wrap > ul > li > a`
Intranet `div.content-wrap > ul > li > a`
KIT `div.content-wrap > ul > li > 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-*]` 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.

●`button`, `link`, and `menuitem` elements have accessible names

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○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.

○Uses ARIA roles only on compatible elements

○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.

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

4 decorative image(s) correctly marked

9 image(s) with good alt text

13 images 9 good alt text 4 decorative

All images have appropriate alt text.

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)

Element	Ratio	Required	FG	BG	Result
h1 Guten Tag!	19.68:1	3.0:1	#000000	#F9F7F7	Pass
h1 Aktuelles aus dem KI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Veranstaltungen	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Forschungsorientiert…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Studiengänge	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bewerbung	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Mehr als eine gute I…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Transfer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Das KIT auf der Hann…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Forschungsorientiert…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Studiengänge	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bewerbung	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Mehr als eine gute I…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Transfer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Das KIT auf der Hann…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Besuchen	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Bewerben	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Presse	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Kontakt	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Karlsruher Institut …	21.00:1	4.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.