Skip to content
https://goethe.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓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: #a0c814
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 5 <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
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
1 of 5 <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 "Meta Navigation" 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
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
span Gebärdensprache
3.81:1
#000000
on
#686969
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Leichte Sprache
1.02:1
#000000
on
#010307
needs 4.5:1 (normal text)
16px · top of page (header area)
span Mein Goethe.de
1.03:1
#000000
on
#030505
needs 4.5:1 (normal text)
16px · top of page (header area)
p Mein Goethe.de
1.03:1
#000000
on
#040608
needs 4.5:1 (normal text)
16px · above the fold
a Meine Kurse und Prüfungen
1.08:1
#000000
on
#060E12
needs 4.5:1 (normal text)
16px · above the fold

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)
ElementRatioRequiredFGBGResult
h1 Suche21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Sprache. Kultur. Deu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Deutsch lernen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Deutschprüfungen A1…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 75 Jahre Goethe-Inst…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Veranstaltungen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Netzwerk21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Folgen Sie uns21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Service- und Informa…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Prüfungsorte weltwe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Schnelleinstieg21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Schnelleinstieg21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Netzwerk21.00:13.0:1
#000000
#FFFFFF
Pass
title Goethe-Institut | Sp…21.00:14.5:1
#000000
#FFFFFF
Pass
span Gebärdensprache3.81:14.5:1
#000000
#686969
Fail
span Leichte Sprache1.02:14.5:1
#000000
#010307
Fail
span Mein Goethe.de1.03:14.5:1
#000000
#030505
Fail
p Mein Goethe.de1.03:14.5:1
#000000
#040608
Fail
a Meine Kurse und Prü…1.08:14.5:1
#000000
#060E12
Fail
a Deutsch für dich8.16:14.5:1
#000000
#9FA2A2
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
Heading Hierarchy
26 headings
PASS
26 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Suche
  • H1 Sprache. Kultur. Deutschland. duplicate H1
  • H2 Im Austausch mit der Welt. Für Vielfalt, Verständigung und Vertrauen.
  • H2 Deutsch lernen
  • H2 Deutschprüfungen A1–C2
  • H3 Prüfungsorte weltweit
  • H2 75 Jahre Goethe-Institut
  • H3 Das Goethe-Institut im Jubiläumsjahr
  • H3 Geschichte des Goethe-Instituts
  • H3 Unser Jubiläumsprogramm
  • H2 Sprache
  • H3 Schnelleinstieg
  • H3 Monsterstark Deutsch lernen mit Boto
  • H3 Zuwanderung gestalten
  • H2 Kultur
  • H3 Schnelleinstieg
  • H3 Ecological Futures
  • H3 Culture Moves Europe
  • H2 Veranstaltungen
  • H2 Netzwerk
  • H3 Netzwerk
  • H2 Karriere
  • H3 Presse
  • H3 Newsletter
  • H2 Folgen Sie uns
  • H2 Service- und Informationsbereich

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 28 images OK
PASS
All 28 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
16 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
28 images 10 good alt text 16 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-input-page-headersearchSucheingabefor/id
#combobox-select-493755selectLand/Gebiet suchenfor/id
#combobox-input-493755textLand/Gebiet suchenfor/id
#combobox-select-340623selectLand/Gebiet suchenfor/id
#combobox-input-340623textLand/Gebiet suchenfor/id
#combobox-select-708463selectLand auswählenfor/id
#combobox-input-708463textLand auswählenfor/id
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 31 passed
PASS
97

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.

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 div#outer-container-467911 > div#quickfact-vertical-743593 > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#outer-container-467911 > div#quickfact-vertical-743593 > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div#outer-container-467911 > div#quickfact-vertical-743593 > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 1 div#outer-container-550868 > div#quickfact-vertical-773022 > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div#outer-container-550868 > div#quickfact-vertical-773022 > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div#outer-container-550868 > div#quickfact-vertical-773022 > div.swiper-pagination > span.swiper-pagination-bullet

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
●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
●`[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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○`<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.
○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