Skip to content
https://Www.donaubad.de

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
F
Heading Hierarchy
Action
40 headings, 3 skip(s)
FIX
40 headings, 3 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H4 Aktueller Stand (Freitag, 08.05.2026 / 15:00 Uhr)
  • H2 Herzlich Willkommen im Donaubad
  • H2 Entdecken Sie alle Bereiche
  • H4 ERLEBNISBAD skipped
  • H4 SAUNA
  • H4 FREIBAD
  • H4 EISSPORT
  • H4 INLINESPORT
  • H4 WOHNMOBIL
  • H4 GASTRONOMIE
  • H4 FITNESS
  • H2 Unsere Öffnungszeiten
  • H3 Erlebnisbad
  • H3 Sauna
  • H3 Freibad
  • H3 Eissportanlage
  • H3 Inline- & Eventhalle
  • H3 Wohnmobil
  • H3 Gastronomie
  • H3 Fitness
  • H2 Unsere Events & Veranstaltungen
  • H4 Hüpfburgenpark skipped
  • H4 Sommer-Grillen 2026 - Feierabend neu genießen!
  • H4 Lange Saunaabende mit Motto
  • H4 Sauna-Spezial - Zu Gast im Donaubad
  • H4 GROßE SOMMER-POOLPARTY für Kids & Teens
  • H2 Gutscheine & Shop
  • H2 Unsere Angebote im Überblick
  • H2 (empty)
  • H2 Unsere Meldungen
  • H4 Das Donaubad startet am 9. Mai in die Freibadsaison 2026 skipped
  • H4 Den Feierabend neu genießen: lange Sauna-Abende im Donaubad
  • H4 Hüpfburgenpark am Donaubad eröffnet
  • H4 Schöne Osterzeit im Donaubad - mit Glanzlichtern
  • H4 Erfolgreiche Jubiläums-Saison der Eissportanlage
  • H4 Schöner Saison-Abschluss für die Eissportanlage am Donaubad
  • H2 Unsere Premiumkarten
  • H2 Hoch hinaus mit dem Donaubad-Ballon!
  • H2 Social Media Wall
  • H2 Übersichtsplan Donaubad-Anlage

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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 ▾

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 ▾

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

D
Tabindex Anti-Patterns
Action
0 positive, 28 -1-on-focusable
FIX
0 positive, 28 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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 ✓Page Title Redirecting to /de ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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: #ffffff
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN ASIDE "Eye-Able Assistenztechnik. Öffnen mit ALT und 1. Bedienung mit TAB. Verlassen mit Esc." CONTENTINFO (missing!)

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

B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Donaubad
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Donaubad ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Donaubad Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 2 pass AA only
title Donaubad Ulm / Neu-Ulm – Erlebnisbad, …
3.72:1
#000000
on
#046AB3
needs 4.5:1 (normal text)
16px · top of page (header area)
p BEREICHE
3.72:1
#000000
on
#046AB3
needs 4.5:1 (normal text)
16px · top of page (header area)
p Unvergleichliches Badevergnügen!
3.86:1
#000000
on
#666A70
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div 09:00 - 21:00 Uhr
4.48:1
#000000
on
#6D7766
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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
h2 Unsere Öffnungszeit…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Gutscheine & Shop15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Hoch hinaus mit dem …15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Übersichtsplan Dona…15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Erlebnisbad15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Sauna15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Freibad15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Eissportanlage15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Inline- & Eventhalle15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Wohnmobil15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Gastronomie15.46:13.0:1
#000000
#DDDDDD
Pass
h3 Fitness15.46:13.0:1
#000000
#DDDDDD
Pass
title Donaubad Ulm / Neu-U…3.72:14.5:1
#000000
#046AB3
Fail
p BEREICHE3.72:14.5:1
#000000
#046AB3
Fail
div Bad & Sauna5.76:14.5:1
#000000
#7F8C4D
Pass
div Erlebnisbad5.64:14.5:1
#000000
#6C889C
Pass
p Unvergleichliches Ba…3.86:14.5:1
#000000
#666A70
Fail
div Geöffnet9.40:14.5:1
#000000
#B9AC95
Pass
div 09:00 - 21:00 Uhr4.48:14.5:1
#000000
#6D7766
Fail
div Sauna15.46:14.5:1
#000000
#DDDDDD
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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
8 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 8 all-caps heading(s)
A+
Alt Text Quality
All 66 images OK
PASS
All 66 images OK
Info::
10 decorative image(s) correctly marked
Info::
56 image(s) with good alt text
66 images 56 good alt text 10 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ccm-purpose-41ba25ccheckboxTechnisch notwendig (2)for/id
#ccm-purpose-a717ff5checkboxAnalyse / Statistiken (2)for/id
#ccm-purpose-cdcbd7ccheckboxAnzeigen / Ads (2)for/id
#ccm-purpose-6cd2721checkboxSocial Media (1)for/id
#ccm-purpose-15c61c3checkboxSonstiges (1)for/id
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "de"
PASS
Lang attribute set to "de"
Info::
<html lang="de"> is set and valid
Got: de
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 1 visible text node(s) render at >= 12 CSS pixels
PASS
All 1 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 92/100 — 4 failing, 28 passed
PASS
92

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.

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
ERLEBNISBAD div.uk-width-1-2@s > div.c-card > div.c-card-image-body > h4.uk-margin-medium-bottom
Tauchen Sie ein in ein unvergleichliches Badevergnügen im größten Erlebnisbad d… div.uk-width-1-2@s > div.c-card > div.c-card-image-body > p
Erlebnisbad entdecken div.uk-width-1-2@s > div.c-card > div.c-card-image-button > a.uk-button
ERLEBNISBAD div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > h3.c-opening-hours-tile-title
Mai - September div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > p.c-opening-hours-tile-opening-hours-name
Mehr Öffnungszeiten div.uk-inline-grid > div.uk-margin-top > a.c-link > p.c-link-title
SAUNA div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > h3.c-opening-hours-tile-title
Mai - September div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > p.c-opening-hours-tile-opening-hours-name
Mehr Öffnungszeiten div.uk-inline-grid > div.uk-margin-top > a.c-link > p.c-link-title
FREIBAD div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > h3.c-opening-hours-tile-title
Mai - September div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > p.c-opening-hours-tile-opening-hours-name
Mehr Informationen (Infos zum Vorverkauf Dauerkarten) div.uk-inline-grid > div.uk-margin-top > a.c-link > p.c-link-title
EISSPORTANLAGE div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > h3.c-opening-hours-tile-title
Oktober - März div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > p.c-opening-hours-tile-opening-hours-name
Mehr Informationen div.uk-inline-grid > div.uk-margin-top > a.c-link > p.c-link-title
INLINE- & EVENTHALLE div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > h3.c-opening-hours-tile-title
Hüpfburgenpark vom 04.04 bis 10.05 div.uk-grid > div.c-opening-hours-banner-item > div.c-opening-hours-tile > p.c-opening-hours-tile-opening-hours-name
Zur Laufschule, Miete Inlinehalle, Hüpfburgenpark alle Öffnungszeiten... div.uk-inline-grid > div.uk-margin-top > a.c-link > p.c-link-title
Mehr Informationen div.uk-inline-grid > div.uk-margin-top > a.c-link > p.c-link-title
Inline- & Eventhalle (1) div.c-carousel-filters > ul > li > a.c-carousel-filter
Sauna (3) div.c-carousel-filters > ul > li > a.c-carousel-filter
Erlebnisbad (1) div.c-carousel-filters > ul > li > a.c-carousel-filter
10.05.2026 a.uk-width-1-2@s > div.c-card > div.card-event-offer-detail-container > div.c-card-event-offer-detail
Erlebnisbad (5) div.c-carousel-filters > ul > li > a.c-carousel-filter
Sauna (5) div.c-carousel-filters > ul > li > a.c-carousel-filter
Inline- & Eventhalle (1) div.c-carousel-filters > ul > li > a.c-carousel-filter
Erlebnisbad div.c-offer-card-content > div.c-offer-card-body > div.c-offer-card-areas > div.c-offer-card-area
Zum Kindergeburtstag div.c-offer-card-body > div.c-offer-card-link > a.c-link > p.c-link-title
Sauna div.c-offer-card-content > div.c-offer-card-body > div.c-offer-card-areas > div.c-offer-card-area
Zur Massage div.c-offer-card-body > div.c-offer-card-link > a.c-link > p.c-link-title
Sauna div.c-offer-card-content > div.c-offer-card-body > div.c-offer-card-areas > div.c-offer-card-area
Zu den Dampfbad-Anwendungen div.c-offer-card-body > div.c-offer-card-link > a.c-link > p.c-link-title
Erlebnisbad div.c-offer-card-content > div.c-offer-card-body > div.c-offer-card-areas > div.c-offer-card-area
Zur Schwimmschule div.c-offer-card-body > div.c-offer-card-link > a.c-link > p.c-link-title
Erlebnisbad div.c-offer-card-content > div.c-offer-card-body > div.c-offer-card-areas > div.c-offer-card-area
Zur Aqua-Fitness div.c-offer-card-body > div.c-offer-card-link > a.c-link > p.c-link-title
Erlebnisbad div.c-offer-card-content > div.c-offer-card-body > div.c-offer-card-areas > div.c-offer-card-area
Zum Wasserparcour div.c-offer-card-body > div.c-offer-card-link > a.c-link > p.c-link-title
05.05.2026, Freibad div.uk-width-1-2@m > div.c-news-card > a.c-news-card-body-link > div.c-news-card-leader
Mehr lesen div.c-news-card > div.c-news-card-link > a.c-link > p.c-link-title

These are opportunities to improve the legibility of your content.

Navigation

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
ERLEBNISBAD div.uk-width-1-2@s > div.c-card > div.c-card-image-body > h4.uk-margin-medium-bottom
Hüpfburgenpark div.c-card > div.c-card-event-offer-picture > div.c-card-event-offer-body > h4.c-card-event-offer-headline
Das Donaubad startet am 9. Mai in die Freibadsaison 2026 div.c-news-card > a.c-news-card-body-link > div.c-news-card-headline > h4

These are opportunities to improve keyboard navigation in your application.

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.uk-width-1-2@m > div.c-news-card > div.c-news-card-link > a.c-news-card-body-link div.uk-width-1-2@m > div.c-news-card > div.c-news-card-link > a.c-news-card-body-link

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tage  Mai / August / September Juni / Juli Montag 12:00 - 20:00 Uhr 12.00 - 21.… a.c-news-card-body-link > div.c-news-card-excerpt > div.c-clamp-text > table
  Erwachsen Ermäßigt Kind Familie Klein Familie Groß Eintrittskarte 5,50 €  (bi… a.c-news-card-body-link > div.c-news-card-excerpt > div.c-clamp-text > table
○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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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
○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.
○`<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>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback