Skip to content
https://www.hornbach.se

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
85
GRADE
B
FIX
3
REVIEW
5
PASS
16
INFO
0
Checks
24
16 PASS 5 REVIEW 3 FIX
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
2 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 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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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

B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Favicon & Branding
24 icon(s) detected
REVIEW
24 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
C
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 1 pass AA only
title HORNBACH - Byggvaruhuset för dina byggp…
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
div Din webbläsare accepterar inga cookies.…
1.82:1
#000000
on
#393939
needs 4.5:1 (normal text)
16px · top of page (header area)
span Stämmer
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
button Ja, det stämmer
4.28:1
#000000
on
#747162
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Välj annat varuhus
3.72:1
#000000
on
#606B52
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Göteborg
2.56:1
#000000
on
#4A5238
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Spåra / Annullera / Returnera
1.47:1
#000000
on
#292D0A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Produktjämförelse
1.53:1
#000000
on
#2E2F0F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Företagsservice
1.68:1
#000000
on
#4C2C15
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Kontakt
2.07:1
#000000
on
#603721
needs 4.5:1 (normal text)
16px · above the fold

7 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
title HORNBACH - Byggvaruh…1.93:14.5:1
#000000
#3D3D3D
Fail
div Din webbläsare acce…1.82:14.5:1
#000000
#393939
Fail
span Stämmer2.41:14.5:1
#000000
#4B4B4B
Fail
strong Göteborg3.14:13.0:1
#000000
#5C5C5C
Pass
span som ditt valda varuh…7.26:14.5:1
#000000
#6D9FB3
Pass
button Ja, det stämmer4.28:14.5:1
#000000
#747162
Fail
button Välj annat varuhus3.72:14.5:1
#000000
#606B52
Fail
span Göteborg2.56:14.5:1
#000000
#4A5238
Fail
span Spåra / Annullera /…1.47:14.5:1
#000000
#292D0A
Fail
span Produktjämförelse1.53:14.5:1
#000000
#2E2F0F
Fail
span Företagsservice1.68:14.5:1
#000000
#4C2C15
Fail
span Kontakt2.07:14.5:1
#000000
#603721
Fail
span Karriär21.00:14.5:1
#000000
#FFFFFF
Pass
span Sortiment21.00:14.5:1
#000000
#FFFFFF
Pass
span Badrum & VVS21.00:14.5:1
#000000
#FFFFFF
Pass
span Byggmaterial, trä, …21.00:14.5:1
#000000
#FFFFFF
Pass
span El & belysning21.00:14.5:1
#000000
#FFFFFF
Pass
span Färg & tapeter21.00:14.5:1
#000000
#FFFFFF
Pass
span Golv21.00:14.5:1
#000000
#FFFFFF
Pass
span Kakel & klinker21.00:14.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
No headings to evaluate -- check is N/A
PASS
No headings to evaluate -- check is N/A
Info::
No headings to evaluate -- check is N/A
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
22 image(s) with good alt text
22 images 22 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
global_searchsearchHittaaria-label
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
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
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 "sv"
PASS
Lang attribute set to "sv"
Info::
<html lang="sv"> is set and valid
Got: sv
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a id="cms-main-skiplink-target">
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.)
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 9 visible text node(s) render at >= 12 CSS pixels
PASS
All 9 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Hitta ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: HORNBACH
Info::
192x192 icon present
Info::
512x512 icon present
Info::
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)
A
PWA Depth
2 PWA signal(s) surfaced
PASS
2 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).
Info::
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
Info::
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.
Info::
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.
Info::
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.
Info::
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
Så inreder du balkongen div.hero-teaser-inner > div.grid-item > a.teaser-link
Till produkten div.article-info-wrapper > div.article-data-container > div.article-data-wrapper > a.cta
PDF-dokument Produktåterkallelse Öppna i nytt fönster ul.host-inner > li.icons-teaser > a.teaser-link
Varuhus & öppettider Öppna i nytt fönster ul.host-inner > li.icons-teaser > a.teaser-link
Reservera & hämta Öppna i nytt fönster ul.host-inner > li.icons-teaser > a.teaser-link
HORNBACH-appen Öppna i nytt fönster ul.host-inner > li.icons-teaser > a.teaser-link
Prisgaranti Öppna i nytt fönster ul.host-inner > li.icons-teaser > a.teaser-link
HORNBACH går på djupet – Din åsikt är viktig för oss. Öppna i nytt fönster div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
HORNBACH går på djupet – Din åsikt är viktig för oss. Öppna i nytt fönster div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
HORNBACH går på djupet – Din åsikt är viktig för oss. Öppna i nytt fönster div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
Nyfiken på hur det skulle vara att bli en av oss? Öppna i nytt fönster div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
Bläddra i vårt senaste projekthäfte Öppna i nytt fönster div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
Det är bara en bräda. Men i dina händer kan den bli vad som helst.För ingen brä… a.teaser-link
Vi arbetar ständigt med att uppdatera och förnya vårt sortiment! Här kan du se … a.teaser-link
HORNBACHs uppdaterade serie brytbara inomhusfärger är utvecklad för bättre täck… a.teaser-link
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
null div.container-wrapper-inner > ul.teaser-content > li.teaser-content-inner > a.teaser-href
Är det dags att byta dörren, lägga golvet eller montera markisen – men tiden rä… a.teaser-link
För proffs hos företag, kommuner och organisationer. Vi tror på bra service. Dä… a.teaser-link
Vad vore ett så imponerande sortiment av träprodukter värt om du inte kunde få … a.teaser-link
○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
●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 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.
○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