Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 FIX

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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 ModeNo Dark Mode Detected

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

2 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

Heading Hierarchy

1 headings

REVIEW

1 headings

No H1 heading found

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

H2 Top Artikel unserer Macher

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

Link & Button Quality

Action

3 issue(s) across 227 links and 7 buttons

REVIEW

3 issue(s) across 227 links and 7 buttons

1 link(s) with no accessible text

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

Got: #cms-main-skiplink-target

17 link(s) open in new tab without warning

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

Got: https://karriere.hornbach.de/?utm_source=unternehmenswebsite&utm_medium=header; https://karriere.hornbach.de/?utm_source=unternehmenswebsite&utm_medium=header; https://www.bodenhaus.de/?wt_mc=de.owned.own_brand_domain.hornbachde.kampagne…; https://karriere.hornbach.de/?utm_source=unternehmenswebsite&utm_medium=footer; https://www.hornbach-holding.de/; https://hornbach-baustoff-union.com/; https://www.hornbach-holding.de/investor-relations/; https://www.hornbach-holding.de/medien/; https://www.hornbach-holding.de/unternehmen/corporate-governance/hinweisgeber…; https://apps.apple.com/de/app/hornbach/id948194412 (+7 more)

2 button(s) with no accessible text

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

Got: button.reco_srfn9b0 (#888 on page); button.reco_srfn9b0 (#1107 on page)

209 link(s) with descriptive text

227 links

1 empty

0 generic text

17 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://karriere.hornbach.de/?utm_source…	Karriere	new tab	Add '(opens in new tab)' to text
https://karriere.hornbach.de/?utm_source…	Karriere	new tab	Add '(opens in new tab)' to text
#cms-main-skiplink-target	(empty)	empty	Add link text or aria-label
https://www.bodenhaus.de/?wt_mc=de.owned…	BODENHAUS: Fliesen. Platten. D…	new tab	Add '(opens in new tab)' to text
https://karriere.hornbach.de/?utm_source…	Karriere	new tab	Add '(opens in new tab)' to text
https://www.hornbach-holding.de/	HORNBACH Holding	new tab	Add '(opens in new tab)' to text
https://hornbach-baustoff-union.com/	Hornbach Baustoff Union	new tab	Add '(opens in new tab)' to text
https://www.hornbach-holding.de/investor…	Investor Relations	new tab	Add '(opens in new tab)' to text
https://www.hornbach-holding.de/medien/	Presse/Medien	new tab	Add '(opens in new tab)' to text
https://www.hornbach-holding.de/unterneh…	HORNBACH Hinweisgebersystem	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/de/app/hornbach/i…	App Store Logo Apple: Mit Schr…	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	App Store Logo Google: Mit Sch…	new tab	Add '(opens in new tab)' to text
https://appgallery.huawei.com/#/app/C102…	App Store Logo Huawei: Mit Sch…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/hornbach_de/?h…	Instagram Logo	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/hornbach.de	Facebook Logo	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/Hornbach	YouTube Logo	new tab	Add '(opens in new tab)' to text
https://www.pinterest.de/hornbachde/	Pinterest Logo	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@hornbach_de	TikTok Logo	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

214 links and buttons have descriptive text

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

#cms-main-skiplink-target

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.

https://karriere.hornbach.de/?utm_source=unternehmenswebsite&utm_medium=header; https://karriere.hornbach.de/?utm_source=unternehmenswebsite&utm_medium=header; https://www.bodenhaus.de/?wt_mc=de.owned.own_brand_domain.hornbachde.kampagne…; https://karriere.hornbach.de/?utm_source=unternehmenswebsite&utm_medium=footer; https://www.hornbach-holding.de/; https://hornbach-baustoff-union.com/; https://www.hornbach-holding.de/investor-relations/; https://www.hornbach-holding.de/medien/; https://www.hornbach-holding.de/unternehmen/corporate-governance/hinweisgeber…; https://apps.apple.com/de/app/hornbach/id948194412 (+7 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.reco_srfn9b0 (#888 on page); button.reco_srfn9b0 (#1107 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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Seite nicht gefunden. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

24 icon(s) detected

REVIEW

24 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA 2 pass AA only

title HORNBACH | Dein Projektbaumarkt & Online…

1.93:1

#000000

#3D3D3D

needs 4.5:1 (normal text)

16px · top of page (header area)

div Ihr Browser akzeptiert keine Cookies. F�…

1.82:1

#000000

#393939

needs 4.5:1 (normal text)

16px · top of page (header area)

span Ist

2.41:1

#000000

#4B4B4B

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Dein richtiger Markt?

3.36:1

#000000

#775B42

needs 4.5:1 (normal text)

16px · above the fold

button Ja, richtig

3.34:1

#000000

#765B3E

needs 4.5:1 (normal text)

16px · above the fold

button Anderen Markt wählen

3.74:1

#000000

#80623F

needs 4.5:1 (normal text)

16px · above the fold

span Bornheim (Pfalz)

3.48:1

#000000

#825B2D

needs 4.5:1 (normal text)

16px · above the fold

span Sendungsverfolgung

1.31:1

#000000

#13251F

needs 4.5:1 (normal text)

16px · above the fold

span ProfiService

4.04:1

#000000

#816855

needs 4.5:1 (normal text)

16px · above the fold

span Alle Services

3.82:1

#000000

#72675F

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)

Element	Ratio	Required	FG	BG	Result
h2 Top Artikel unserer …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title HORNBACH \| Dein Proj…	1.93:1	4.5:1	#000000	#3D3D3D	Fail
div Ihr Browser akzeptie…	1.82:1	4.5:1	#000000	#393939	Fail
span Ist	2.41:1	4.5:1	#000000	#4B4B4B	Fail
strong Bornheim (Pfalz)	3.14:1	3.0:1	#000000	#5C5C5C	Pass
span Dein richtiger Markt…	3.36:1	4.5:1	#000000	#775B42	Fail
button Ja, richtig	3.34:1	4.5:1	#000000	#765B3E	Fail
button Anderen Markt wähle…	3.74:1	4.5:1	#000000	#80623F	Fail
span Bornheim (Pfalz)	3.48:1	4.5:1	#000000	#825B2D	Fail
span Sendungsverfolgung	1.31:1	4.5:1	#000000	#13251F	Fail
span Artikelvergleich	4.94:1	4.5:1	#000000	#8F7663	Pass
span ProfiService	4.04:1	4.5:1	#000000	#816855	Fail
span Alle Services	3.82:1	4.5:1	#000000	#72675F	Fail
span Karriere	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Sortiment	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Bad & Sanitär	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Baustoffe	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Holz, Fenster & Tür…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Bodenbeläge & Flies…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Eisenwaren	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.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 37 images OK

PASS

All 37 images OK

37 image(s) with good alt text

37 images 37 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
global_search	search	Finden	aria-label

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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 "de"

PASS

Lang attribute set to "de"

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

Got: de

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

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" on naturally-focusable <a id="cms-main-skiplink-target">

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

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

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

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: HORNBACH

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name HORNBACH ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name HORNBACH Display Mode standalone Icons 9 icon(s)

PWA Depth

2 PWA signal(s) surfaced

PASS

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

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

A+

Mobile UX Depth

4 mobile-depth signal(s) detected

PASS

4 mobile-depth signal(s) detected

iOS smart-banner opt-in present (`apple-itunes-app`)

The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.

Android smart-banner opt-in present (`google-play-app`)

The page declares a companion Android app via `<meta name="google-play-app" content="app-id=...">` (or `google-play-id`). Combined with Chrome's intent: protocol or App Links, this lets supporting browsers offer to open the page in the app.

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
So baust Du eine Mähroboter-Garage. `div.moving-image-container > div.moving-image-link > div.moving-image-content > a.headline-wrapper`
Zum Produkt `div.article-info-wrapper > div.article-data-container > div.article-data-wrapper > a.cta`
Sag uns Deine Meinung zum Onlineshop. - öffnet im neuen Fenster `div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href`
Projekt-Starter: Garten - öffnet im neuen Fenster `div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href`
Raus damit im Onlineshop - öffnet im neuen Fenster `ul.host-inner > li.icons-teaser > a.teaser-link`
+49 6348/9839 - 0 `a.link`
ZU ALLEN MARKTINFORMATIONEN `a.secondary`

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Image elements do not have `[alt]` attributes that are redundant text.

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

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

○Identical links have the same purpose.

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