Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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

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

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 Jump to top of page ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 4 pass AA only

button DAAD

1.24:1

#000000

#131F1D

needs 4.5:1 (normal text)

16px · above the fold

p und

1.31:1

#000000

#122615

needs 4.5:1 (normal text)

16px · above the fold

button Dritte

2.31:1

#000000

#74362D

needs 4.5:1 (normal text)

16px · above the fold

button Cookies

1.41:1

#000000

#092E14

needs 4.5:1 (normal text)

16px · above the fold

p gesetzt und

1.28:1

#000000

#13231B

needs 4.5:1 (normal text)

16px · above the fold

button Nutzungsdaten verarbeitet

1.44:1

#000000

#232A2C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p . Hierbei werden durch den DAAD und Drit…

1.36:1

#000000

#1A262E

needs 4.5:1 (normal text)

16px · above the fold

button Drittländer

1.45:1

#000000

#132B3F

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Einwilligung zur Nut…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h1 Startseite des Deuts…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 USA - Information un…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Anschrift	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 DAAD Newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Nützliche Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Deutscher Akademisch…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Direkt zum Inhalt	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Cookies	5.24:1	4.5:1	#000000	#7F7F7F	Pass
p Zur Verbesserung der…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
button DAAD	1.24:1	4.5:1	#000000	#131F1D	Fail
p und	1.31:1	4.5:1	#000000	#122615	Fail
button Dritte	2.31:1	4.5:1	#000000	#74362D	Fail
button Cookies	1.41:1	4.5:1	#000000	#092E14	Fail
p gesetzt und	1.28:1	4.5:1	#000000	#13231B	Fail
button Nutzungsdaten verarb…	1.44:1	4.5:1	#000000	#232A2C	Fail
p . Hierbei werden dur…	1.36:1	4.5:1	#000000	#1A262E	Fail
button Drittländer	1.45:1	4.5:1	#000000	#132B3F	Fail
p übermittelt, in den…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button widerrufen	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.

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

6 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Heading Hierarchy

7 headings

PASS

7 headings

Multiple H1 headings (2 found)

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

H1 Einwilligung zur Nutzung von Cookies
H1 Startseite des Deutschen Akademischen Austauschdienstes duplicate H1
H2 Im Einsatz gegen Infektionen
H2 USA - Information und Beratung
H2 Anschrift
H2 DAAD Newsletter
H2 Nützliche Links

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 5 images OK

PASS

All 5 images OK

1 decorative image(s) correctly marked

4 image(s) with good alt text

5 images 4 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#js-unique-v-0-0-2	checkbox	Farbumschalter	for/id
#js-unique-v-0-0-7	input	Suchbegriff*	for/id
#js-unique-v-0-0-10	checkbox	Farbumschalter	for/id
#js-unique-v-0-0-15	input	Suchbegriff*	for/id

Link & Button Quality

34 links, 24 buttons — all OK

PASS

34 links, 24 buttons — all OK

8 link(s) open in new tab without warning

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

Got: https://www.daad.de/de/impressum/; https://www.daad.de/de/datenschutzerklaerung/; https://www.facebook.com/DAAD.Worldwide/; https://www.threads.net/@daad_worldwide; https://www.youtube.com/channel/UC2OducLYmtJGJ0zTCNr7NrA; https://www.instagram.com/daad_worldwide/; https://www.linkedin.com/school/daad-worldwide; https://bsky.app/profile/daadworldwide.bsky.social

26 link(s) with descriptive text

34 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.daad.de/de/impressum/	Impressum	new tab	Add '(opens in new tab)' to text
https://www.daad.de/de/datenschutzerklae…	Datenschutzerklärung	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/DAAD.Worldwide/	Zum DAAD auf Facebook	new tab	Add '(opens in new tab)' to text
https://www.threads.net/@daad_worldwide	Zum DAAD auf Threads	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UC2OducL…	Zum DAAD auf YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/daad_worldwide…	Zum DAAD auf Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/daad-wor…	Zum DAAD auf LinkedIn	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/daadworldwide.b…	Zum DAAD auf Bluesky	new tab	Add '(opens in new tab)' to text

50 links and buttons have descriptive text

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

https://www.daad.de/de/impressum/; https://www.daad.de/de/datenschutzerklaerung/; https://www.facebook.com/DAAD.Worldwide/; https://www.threads.net/@daad_worldwide; https://www.youtube.com/channel/UC2OducLYmtJGJ0zTCNr7NrA; https://www.instagram.com/daad_worldwide/; https://www.linkedin.com/school/daad-worldwide; https://bsky.app/profile/daadworldwide.bsky.social

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 28 passed

PASS

100

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.

○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

●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

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

●`[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 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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

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

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