Skip to content
https://ionos.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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: #001b41
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::
3 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 3 <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
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Seite oder Datei nicht gefunden ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: IONOS
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name IONOS ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name IONOS Display Mode standalone Theme Color #001b41 Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
span Hosting
1.47:1
#000000
on
#002860
needs 4.5:1 (normal text)
16px · above the fold
span Server
1.47:1
#000000
on
#002860
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 in Deutschland und E…8.53:13.0:1
#000000
#8FA7C8
Pass
h3 Cookie-Einstellungen8.53:13.0:1
#000000
#8FA7C8
Pass
title IONOS | Von Website …9.57:14.5:1
#000000
#99B1D2
Pass
div Vous êtes actuellem…9.57:14.5:1
#000000
#99B1D2
Pass
a Accéder au site fra…9.57:14.5:1
#000000
#99B1D2
Pass
a 0721 / 170 55229.57:14.5:1
#000000
#99B1D2
Pass
span Neu9.57:14.5:1
#000000
#99B1D2
Pass
span Momentum KI9.57:14.5:1
#000000
#99B1D2
Pass
span Domains & SSL9.57:14.5:1
#000000
#99B1D2
Pass
span E-Mail & Office9.57:14.5:1
#000000
#99B1D2
Pass
span Website9.57:14.5:1
#000000
#99B1D2
Pass
span Onlineshop9.57:14.5:1
#000000
#99B1D2
Pass
span WordPress9.57:14.5:1
#000000
#99B1D2
Pass
span Hosting1.47:14.5:1
#000000
#002860
Fail
span Server1.47:14.5:1
#000000
#002860
Fail
span Cloud9.57:14.5:1
#000000
#99B1D2
Pass
span Internet & Mobilfunk9.57:14.5:1
#000000
#99B1D2
Pass
a 0721 / 170 55229.57:14.5:1
#000000
#99B1D2
Pass
p Einfacher Einstieg m…9.57:14.5:1
#000000
#99B1D2
Pass
span KI-Telefonassistent9.57:14.5:1
#000000
#99B1D2
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 Hierarchy
26 headings, 1 skip(s)
PASS
26 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 Nur bei IONOS
  • H2 Profi-Website in Sekunden dank KI.
  • H2 Warum nicht sofort online durchstarten?
  • H2 Digital an Ihrer Seite.
  • H2 Von Domain über Website bis zur Cloud.
  • H1 Führen Sie Ihr Unternehmen online zum Erfolg – mit KI von IONOS.
  • H3 Passende Domain skipped
  • H3 E-Mail-Komplett-Paket
  • H2 Zum Online-Erfolg mit Ihrer Website und smarten KI-Tools.
  • H3 Website in Sekunden dank KI
  • H3 Weltweit verkaufen – schnell & sicher
  • H3 Ihr KI-Telefonassistent: 24/7 erreichbar
  • H3 Smarte Tools für maximale Reichweite
  • H3 Hosting für WordPress vom Preis-Leistungssieger
  • H3 Das schnellste Webhosting
  • H3 VPS Server unschlagbar günstig
  • H3 Deutsche, souveräne Cloud
  • H2 Setzen Sie auf den Marktführer.
  • H3 in Deutschland und Europa die Nummer 1.
  • H2 Gemeinsam mit unseren Kunden auf Wachstumskurs.
  • H2 Führende Marken und Partner setzen auf IONOS.
  • H3 Nur bei IONOS
  • H3 Ihr persönlicher Berater
  • H3 24/7 Experten-Support
  • H2 IONOS – Digital an Ihrer Seite.
  • H3 Cookie-Einstellungen

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 252 images OK
PASS
All 252 images OK
Info::
164 decorative image(s) correctly marked
Info::
88 image(s) with good alt text
252 images 88 good alt text 164 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
mutlicheck.domaintextBitte dieses Feld ausfüllen.aria-label
checker.DomaintextBitte dieses Feld ausfüllen.aria-label
A
Favicon & Branding
14 icon(s) detected
PASS
14 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 30 passed
PASS
91

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.

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.tw-py-20 > div.tw-rd-container > form.tw-relative > button.tw-z-1 div.tw-py-20 > div.tw-rd-container > form.tw-relative > button.tw-z-1
div.tw-rounded-lg > div.tw-rd-container > form.tw-relative > button.tw-z-1 div.tw-rounded-lg > div.tw-rd-container > form.tw-relative > button.tw-z-1

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menü öffnen div.tw-container > div.tw-inline-flex > div > button.tw-relative
ionos logo nav.tw-relative > div.tw-container > div.tw-inline-flex > a#header-logo
Jetzt anrufen:0721/170 5522 div.tw-container > div.tw-absolute > div > a.whitespace-nowrap
Login div.tw-absolute > div > div.tw-z-51 > button.tw-text-ellipsis

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Passende Domain div.tw-flex > a.tw-min-h-300 > div > h3.tw-block

These are opportunities to improve keyboard navigation in your application.

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
Nur bei IONOS Ihr persönlicher Berater Mehr body.tw-font-sans-regular > div#__next > button.tw-fixed
○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
●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
●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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○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.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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