Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 11 -1-on-focusable

FIX

0 positive, 11 -1-on-focusable

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">

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

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">

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

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">

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

tabindex="-1" on naturally-focusable <button>

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

tabindex="-1" on naturally-focusable <button>

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

tabindex="-1" on naturally-focusable <button>

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

tabindex="-1" on naturally-focusable <button>

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

tabindex="-1" on naturally-focusable <button>

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

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

tabindex="-1" on naturally-focusable <button>

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

tabindex="-1" on naturally-focusable <button>

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

D

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

D

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

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.

D

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 ✗

F

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

Search

Skip Link

Labeled Navigation 2 <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.

C

Form Accessibility

Action

4 of 9 controls have issues

REVIEW

4 of 9 controls have issues

4 control(s) without accessible label

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

Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

5 control(s) properly labeled

9 controls

5 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	Necessary	for/id
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	Preferences	for/id
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	Statistics	for/id
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	Marketing	for/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformation	checkbox	Do not sell or share my personal information	for/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(none)	none

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

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

C

Link & Button Quality

Action

4 issue(s) across 50 links and 28 buttons

REVIEW

4 issue(s) across 50 links and 28 buttons

4 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: http://www.hygienekongress.de/de/kongress ("Read more"); https://www.bgw-online.de/bgw-online-de/service/medien-arbeitshilfen/medien-c… ("Read more"); /en/cme ("Read more"); /en/company ("Learn more")

15 link(s) open in new tab without warning

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

Got: https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cookiebot.com/goto/privacy-policy/; https://vimeo.com/privacy; https://vimeo.com/privacy; https://vimeo.com/privacy; https://www.cookiebot.com; /de/unternehmen/karriere; https://vimeo.com/bzhgmbh/sekundendieschuetzen; /Artikel-News/Berichterstattung-Kongress_Hygiene-Medizin-2025.pdf; /Artikel-News/Berichterstattung_Kongress-2025_Clinicum.pdf (+5 more)

31 link(s) with descriptive text

50 links

0 empty

4 generic text

15 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookiebot.com/en/what-is-beh…	Cookiebot by Usercentrics - op…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com/goto/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://vimeo.com/privacy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://vimeo.com/privacy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://vimeo.com/privacy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
/de/unternehmen/karriere	More infos	new tab	Add '(opens in new tab)' to text
http://www.hygienekongress.de/de/kongres…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Kongress
https://vimeo.com/bzhgmbh/sekundendiesch…	Watch now	new tab	Add '(opens in new tab)' to text
/Artikel-News/Berichterstattung-Kongress…	Read Now (GERMAN PDF)	new tab	Add '(opens in new tab)' to text
/Artikel-News/Berichterstattung_Kongress…	Read now (GERMAN PDF)	new tab	Add '(opens in new tab)' to text
https://www.bgw-online.de/bgw-online-de/…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Begx 2025 124636
/Artikel-News/nws_2_25_Schwerpunkt_Hygie…	Publication (German)	new tab	Add '(opens in new tab)' to text
/en/cme	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Cme
http://www.hygienekongress.de/de/kongres…	archives	new tab	Add '(opens in new tab)' to text
/de/bzh-cirs-bpl-portal	To CIRS	new tab	Add '(opens in new tab)' to text
/en/company	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Company
/instagram	Instagram	new tab	Add '(opens in new tab)' to text
/linkedin	LinkedIn	new tab	Add '(opens in new tab)' to text

59 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

http://www.hygienekongress.de/de/kongress ("Read more"); https://www.bgw-online.de/bgw-online-de/service/medien-arbeitshilfen/medien-c… ("Read more"); /en/cme ("Read more"); /en/company ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cookiebot.com/goto/privacy-policy/; https://vimeo.com/privacy; https://vimeo.com/privacy; https://vimeo.com/privacy; https://www.cookiebot.com; /de/unternehmen/karriere; https://vimeo.com/bzhgmbh/sekundendieschuetzen; /Artikel-News/Berichterstattung-Kongress_Hygiene-Medizin-2025.pdf; /Artikel-News/Berichterstattung_Kongress-2025_Clinicum.pdf (+5 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

C

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: BZH

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name BZH ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name BZH Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

A

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

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

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 Job Offers
H2 Congress 2026
H2 Hand hygiene that's fun!
H2 Reporting on hygiene and medicine
H2 Reporting by clinicum
H2 BeGX 2025
H2 Post-coronavirus hygiene: what remains important?
H3 Years of expertise
H3 Customers trust in us
H3 Employees
H3 Courses for CME/CNE
H3 Congress 2024 - archives
H3 BZH-CIRS-BPL Portal (German only)
H3 About us

A+

Heading Text Quality

All 14 heading(s) have substantive, well-formed text

PASS

All 14 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

1 of 14 images have issues

PASS

1 of 14 images have issues

1 image(s) with generic alt text

7 decorative image(s) correctly marked

6 image(s) with good alt text

14 images 6 good alt text 7 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Input Types

9 form control(s) checked, no type mismatches

PASS

9 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

9 form control(s) checked, no input-semantic issues

PASS

9 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 72 visible text node(s) render at >= 12 CSS pixels

PASS

All 72 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

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

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+

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 Job Offers	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Congress 2026	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Hand hygiene that's …	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Reporting on hygiene…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Reporting by clinicu…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 BeGX 2025	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Post-coronavirus hyg…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Years of expertise	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Customers trust in u…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Employees	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Courses for CME/CNE	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Congress 2024 - arch…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 BZH-CIRS-BPL Portal …	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 About us	16.98:1	3.0:1	#000000	#E7E7E7	Pass
title Deutsches Beratungsz…	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Consent	17.94:1	4.5:1	#000000	#EDEDED	Pass
a Details	10.80:1	4.5:1	#000000	#B9B9C4	Pass
a [#IABV2SETTINGS#]	15.76:1	4.5:1	#000000	#DFDFDF	Pass
a About	15.76:1	4.5:1	#000000	#DFDFDF	Pass
div This website uses co…	15.76:1	4.5:1	#000000	#DFDFDF	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+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 30 passed

PASS

100

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

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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