Skip to content
https://www.hetzner.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
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
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="domainInput">; <input type="email" name="email">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#settings-vatselectCountry (VAT)for/id
#domainInputtext(desireddomain.com)placeholder only
emailemail(mail address)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id="domainInput">; <input type="email" name="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
15 icon(s) detected
REVIEW
15 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 Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 23 passed
REVIEW
83

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DEDICATED nav#mobile-shift-menu > div > div.mobile-nav-section > a.link-color-white
WEB & MANAGED nav#mobile-shift-menu > div > div.mobile-nav-section > a.link-color-white
STORAGE nav#mobile-shift-menu > div > div.mobile-nav-section > a.link-color-white
SERVICES nav#mobile-shift-menu > div > div.mobile-nav-section > a.link-color-white
ABOUT US nav#mobile-shift-menu > div > div.mobile-nav-section > a.link-color-white
LOGIN nav#mobile-shift-menu > div > div.mobile-nav-section > a.link-color-white

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
THIS WEBSITE USES COOKIES We want you to have the best possible user experience… body.modal-open > header#header > div#InitModal

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
div#geo-suggestion > div.container > div.d-flex > button#geo-decline div#geo-suggestion > div.container > div.d-flex > button#geo-decline
nav#nav_main > div.container > div.navbar-header > button.navbar-toggle nav#nav_main > div.container > div.navbar-header > button.navbar-toggle
form > div.input-group > span.input-group-btn > button.btn form > div.input-group > span.input-group-btn > button.btn

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.

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
AMD Ryzen 7 1700X div.info-box-content > p.margin-0 > span.font-size-normal > strong#sb-name
© 2026 Hetzner Online GmbH. All Rights Reserved. Prices div.footer-wrapper > div.footer-grey-section > div.footer-grey-section-left > div.footer-copyright
incl. 19 % VAT span

These are opportunities to improve the legibility of your content.

○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-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
●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
●`[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
●Links are distinguishable without relying on color.
●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
●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
●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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○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+
Heading Hierarchy
48 headings
PASS
48 headings
Info::
Single H1 present
  • H4 Close
  • H4 Dedicated
  • H4 Cloud
  • H4 Web & Managed
  • H4 Storage
  • H4 Services
  • H4 Jobs
  • H4 Community
  • H4 About us
  • H4 Support
  • H4 Login
  • H3 THIS WEBSITE USES COOKIES
  • H3 Choose your location settings
  • H4 Language
  • H4 Currency
  • H4 Country (VAT)
  • H3 Server Auction
  • H3 Server Finder
  • H3 EX-Line Server
  • H3 AX-Line Server
  • H3 RX-Line Servers
  • H3 SX-Line Server
  • H3 Dedicated GPU Server
  • H3 BRAND SERVER
  • H3 Web Hosting
  • H3 Managed Servers
  • H3 Object Storage
  • H3 Storage Box
  • H3 Storage Share
  • H3 Load Balancer
  • H3 Domain check
  • H3 DNS Management
  • H3 Registration Robot
  • H3 SSL Certificate
  • H3 Custom Solutions
  • H1 Product overview
  • H2 Server auction
  • H2 News / Press
  • H3 News
  • H4 WINDOWS SERVER 2025 NOW AVAILABLE
  • H4 HETZNER RECEIVES BSI C5 CERTIFICATION
  • H4 More AI: The new GPU-Server GEX131 sets standards for performance and price
  • H3 Press Releases
  • H4 Hetzner investiert in KI-basierte Netzwerksicherheit von Nokia
  • H4 Statement on price adjustment as of April 1st 2026
  • H4 Statement on the adjustment of setup fees
  • H2 Get your domain now
  • H2 Awards
A+
Alt Text Quality
All 45 images OK
PASS
All 45 images OK
Info::
45 image(s) with good alt text
45 images 45 good alt text
All images have appropriate alt text.
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)
ElementRatioRequiredFGBGResult
h1 Product overview4.62:13.0:1
#000000
#767676
Pass
h2 Server auction4.62:13.0:1
#000000
#767676
Pass
h2 News / Press4.62:13.0:1
#000000
#767676
Pass
h2 Get your domain now4.62:13.0:1
#000000
#767676
Pass
h2 Awards4.62:13.0:1
#000000
#767676
Pass
h3 THIS WEBSITE USES CO…4.62:13.0:1
#000000
#767676
Pass
h3 Choose your location…4.62:13.0:1
#000000
#767676
Pass
h3 Server Auction4.62:13.0:1
#000000
#767676
Pass
h3 Server Finder4.62:13.0:1
#000000
#767676
Pass
h3 EX-Line Server4.62:13.0:1
#000000
#767676
Pass
h3 AX-Line Server4.62:13.0:1
#000000
#767676
Pass
h3 RX-Line Servers4.62:13.0:1
#000000
#767676
Pass
h3 SX-Line Server4.62:13.0:1
#000000
#767676
Pass
h3 Dedicated GPU Server4.62:13.0:1
#000000
#767676
Pass
h3 BRAND SERVER4.62:13.0:1
#000000
#767676
Pass
h3 Web Hosting4.62:13.0:1
#000000
#767676
Pass
h3 Managed Servers4.62:13.0:1
#000000
#767676
Pass
h3 Object Storage4.62:13.0:1
#000000
#767676
Pass
h3 Storage Box4.62:13.0:1
#000000
#767676
Pass
h3 Storage Share4.62:13.0:1
#000000
#767676
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback