Skip to content
https://danfoss.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
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 The page cannot be found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
6 icon(s) detected
FIX
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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: #e2000f
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::
8 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 8 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
5 of 8 <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 "menu" 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
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 You control your data
  • H2 Cookie policy
  • H2 What is a cookie?
  • H2 How our website uses cookies
  • H2 How long are cookies stored?
  • H2 How to block or delete cookies
  • H2 How can you delete cookies?
  • H2 Changing your consent
  • H2 Do you have any questions?
  • H2 We engineer a better future
  • H2 How to efficiently scale data centers
  • H2 Explore news and articles
  • H2 Our business segments
  • H3 Explore competitive decarbonization in action
  • H2 Quick access

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 You control your data
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · above the fold
h2 Cookie policy
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What is a cookie?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How our website uses cookies
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How long are cookies stored?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How to block or delete cookies
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How can you delete cookies?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Changing your consent
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Do you have any questions?
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We engineer a better future
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How to efficiently scale data centers
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore news and articles
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our business segments
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Quick access
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Explore competitive decarbonization in a…
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
19px · bottom of viewport
title We engineer a better future | Danfoss
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
div Powered by:
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Cookie Information
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
span opens in new tab
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
div We and our business partners use technol…
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 You control your dat…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Cookie policy2.45:13.0:1
#000000
#4C4C4C
Fail
h2 What is a cookie?2.45:13.0:1
#000000
#4C4C4C
Fail
h2 How our website uses…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 How long are cookies…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 How to block or dele…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 How can you delete c…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Changing your consen…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Do you have any ques…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 We engineer a better…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 How to efficiently s…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Explore news and art…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Our business segment…2.45:13.0:1
#000000
#4C4C4C
Fail
h2 Quick access2.45:13.0:1
#000000
#4C4C4C
Fail
h3 Explore competitive …2.45:13.0:1
#000000
#4C4C4C
Fail
title We engineer a better…2.45:14.5:1
#000000
#4C4C4C
Fail
div Powered by:2.45:14.5:1
#000000
#4C4C4C
Fail
a Cookie Information2.45:14.5:1
#000000
#4C4C4C
Fail
span opens in new tab2.45:14.5:1
#000000
#4C4C4C
Fail
div We and our business …2.45:14.5:1
#000000
#4C4C4C
Fail

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.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 26 passed
REVIEW
87

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.col-start-2 > ul.flex > li.block > a#login-link-desktop nav.col-start-2 > ul.flex > li.block > a#login-link-desktop

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.col-start-2 > ul.flex > li > button#base-ui-:re: nav.col-start-2 > ul.flex > li > button#base-ui-:re:
ul.flex > li.block > div.group > button.flex ul.flex > li.block > div.group > button.flex

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
nav.col-start-2 > ul.flex > li.block > a#login-link-desktop nav.col-start-2 > ul.flex > li.block > a#login-link-desktop
body.android-active > main#main > a.scroll-to-top body.android-active > main#main > a.scroll-to-top

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.

○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 are valid and not misspelled
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
○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.
○`<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.
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
6 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
16 images 10 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cookie_cat_functionalcheckboxnone
#cookie_cat_statisticcheckboxnone
#cookie_cat_marketingcheckboxnone
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Danfoss.com
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Danfoss.com ✓192×192 icon ✓512×512 icon ✓Start URL . ✓Display Mode browser ✗
Name Danfoss.com Display Mode browser Theme Color #e2000f Background Color #fff Icons 5 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback