Skip to content
https://united-domains.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Heading Hierarchy
Action
52 headings, 6 skip(s)
FIX
52 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H5 Möchten Sie uns eine Nachricht schreiben?
  • H5 Sie möchten mit uns sprechen?
  • H5 Suchen Sie Hilfe zu einem dieser Themen?
  • H5 Sie finden nicht, was Sie suchen?
  • H6 Top-Domains
  • H5 Möchten Sie uns eine Nachricht schreiben?
  • H5 Sie möchten mit uns sprechen?
  • H5 Suchen Sie Hilfe zu einem dieser Themen?
  • H5 Sie finden nicht, was Sie suchen?
  • H5 Möchten Sie uns eine Nachricht schreiben?
  • H5 Sie möchten mit uns sprechen?
  • H5 Suchen Sie Hilfe zu einem dieser Themen?
  • H5 Sie finden nicht, was Sie suchen?
  • H1 Domain-Check
  • H2 Suchen. Sichern. Starten.
  • H4 Jetzt eigene Email-Domain ab 1 € skipped
  • H5 Sehr hohe Kundenzufriedenheit
  • H5 Ausgezeichneter Domain-Support
  • H5 Hervorragende Sicherheit
  • H2 Starten Sie Ihr nächstes digitales Projekt
  • H4 Unsere Domain-Empfehlungen skipped
  • H3 Professionelle Domainverwaltung
  • H6 Übersichtlich. Professionell. Sicher. skipped
  • H2 Machen Sie die Domain zu Ihrem Projekt
  • H3 (empty)
  • H5 Ihre eigene E-Mail Domain skipped
  • H5 Hosting für WordPress
  • H5 Webspace
  • H5 Sichere Website-Kommunikation mit SSL
  • H5 Homepage Baukasten
  • H4 Diese Unternehmen vertrauen united-domains:
  • H2 Kaufen Sie Ihre Domain beim Domain-Experten
  • H4 Über 1.000 Domain-Endungen skipped
  • H4 Registrieren Sie Ihre Domain schnell & einfach
  • H5 Hervorragende Sicherheit
  • H5 Wir sind für Sie da
  • H5 Sichern Sie Ihre Domains
  • H5 Ihre eigene E-Mail-Adresse
  • H5 Hosting & Webspace
  • H5 Domainberatung
  • H2 Weitere Trends und Tipps rund um Domains
  • H5 Was ist Phishing und wie kann man sich davor schützen? skipped
  • H5 2025 endet mit 386,9 Mio. registrierter Domains
  • H5 .com steht auf Wachstum und legt im Januar 2026 um 850.000 Registrierungen zu
  • H3 Häufig gestellte Fragen zu unserem Domain-Check
  • H3 Was ist ein Domain-Check?
  • H3 Was gibt es bei der Suche nach einer Domain zu beachten?
  • H3 Wo kann ich eine Domain prüfen?
  • H3 Wo sehe ich, ob eine Domain frei ist?
  • H3 Wieso muss man Domains kaufen?
  • H3 Wie viel kosten Hosting und Domain?
  • H3 Bietet united-domains einen Domain Generator?

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

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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: #092850
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.

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::
1 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
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
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: united-domains
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name united-domains ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name united-domains Display Mode standalone Theme Color #092850 Background Color #ffffff Icons 2 icon(s)
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 5 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Domain-Check5.36:13.0:1
#000000
#7A837B
Pass
h2 Suchen. Sichern. Sta…5.36:13.0:1
#000000
#7A837B
Pass
h2 Starten Sie Ihr näc…5.36:13.0:1
#000000
#7A837B
Pass
h2 Machen Sie die Domai…5.36:13.0:1
#000000
#7A837B
Pass
h2 Kaufen Sie Ihre Doma…5.36:13.0:1
#000000
#7A837B
Pass
h2 Weitere Trends und …5.36:13.0:1
#000000
#7A837B
Pass
h3 Professionelle Domai…5.36:13.0:1
#000000
#7A837B
Pass
h3 Häufig gestellte Fr…5.36:13.0:1
#000000
#7A837B
Pass
h3 Was ist ein Domain-C…5.36:13.0:1
#000000
#7A837B
Pass
h3 Was gibt es bei der …5.36:13.0:1
#000000
#7A837B
Pass
h3 Wo kann ich eine Dom…5.36:13.0:1
#000000
#7A837B
Pass
h3 Wo sehe ich, ob eine…5.36:13.0:1
#000000
#7A837B
Pass
h3 Wieso muss man Domai…5.36:13.0:1
#000000
#7A837B
Pass
h3 Wie viel kosten Host…5.36:13.0:1
#000000
#7A837B
Pass
h3 Bietet united-domain…5.36:13.0:1
#000000
#7A837B
Pass
title Domain Check: Kosten…5.84:14.5:1
#000000
#878786
Pass
a Zum Inhalt springen5.84:14.5:1
#000000
#878786
Pass
span Bitte haben Sie eine…5.84:14.5:1
#000000
#878786
Pass
span Ihre Daten werden ve…5.84:14.5:1
#000000
#878786
Pass
button Hilfe5.84:14.5:1
#000000
#878786
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
Alt Text Quality
1 of 54 images have issues
PASS
1 of 54 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
16 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
54 images 37 good alt text 16 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Form Accessibility
All 48 controls labeled
PASS
All 48 controls labeled
Info::
48 control(s) properly labeled
48 controls
48 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#atm-forms-auto-id-819821392emailE-Mailfor/id
#atm-forms-auto-id-690322476passwordPasswortfor/id
#atm-forms-auto-id-854593863emailE-Mailfor/id
#atm-forms-auto-id-559208830passwordPasswortfor/id
domaintextareaWunschdomain eingebenaria-label
prompttextareaBitte geben Sie einen Text ein, um Domainvorschläge zu generieren. Max. 250 Zeichenaria-label
inputcheckboxnone
inputcheckboxnone
#cookieLayerArea6checkboxGooglefor/id
#cookieLayerArea9checkboxetracker GmbHfor/id
#cookieLayerArea20checkboxHotjar Ltd.for/id
#cookieLayerArea22checkboxSurvicatefor/id
#cookieLayerArea23checkboxIONOS SEfor/id
#cookieLayerArea24checkboxJENTIS GmbHfor/id
#cookieLayerArea26checkboxKameleoonfor/id
inputcheckboxnone
#cookieLayerArea13checkboxunited-domainsfor/id
#cookieLayerArea14checkboxIONOS SEfor/id
#cookieLayerArea15checkboxEmarsys interactive services GmbHfor/id
#cookieLayerArea17checkboxHubspotfor/id
inputcheckboxnone
#cookieLayerArea25checkboxGooglefor/id
#cookieLayerArea5checkboxBingfor/id
#cookieLayerArea16checkboxFacebookfor/id
#cookieLayerArea18checkboxLinkedInfor/id
#cookieLayerArea28checkboxTikTokfor/id
#cookieLayerArea21checkboxTUNE, Inc.for/id
inputcheckboxnone
inputcheckboxnone
#cookieLayerArea6checkboxGooglefor/id
#cookieLayerArea9checkboxetracker GmbHfor/id
#cookieLayerArea20checkboxHotjar Ltd.for/id
#cookieLayerArea22checkboxSurvicatefor/id
#cookieLayerArea23checkboxIONOS SEfor/id
#cookieLayerArea24checkboxJENTIS GmbHfor/id
#cookieLayerArea26checkboxKameleoonfor/id
inputcheckboxnone
#cookieLayerArea13checkboxunited-domainsfor/id
#cookieLayerArea14checkboxIONOS SEfor/id
#cookieLayerArea15checkboxEmarsys interactive services GmbHfor/id
#cookieLayerArea17checkboxHubspotfor/id
inputcheckboxnone
#cookieLayerArea25checkboxGooglefor/id
#cookieLayerArea5checkboxBingfor/id
#cookieLayerArea16checkboxFacebookfor/id
#cookieLayerArea18checkboxLinkedInfor/id
#cookieLayerArea28checkboxTikTokfor/id
#cookieLayerArea21checkboxTUNE, Inc.for/id
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+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /assets/css/atomic-print.cb-e4cb3.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /assets/css/atomic-print.cb-e4cb3.css ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 18 passed
PASS
95

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

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
Cookie-Einstellungen Wir setzen Cookies ein, um unsere Website optimal für Sie… body.gen-layer__body-open > dialog.gen-layer

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.

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
Datenschutzhinweisen div.gen-layer__white > form.cookie-layer-form > p.intro-text > a
○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
●`[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
●Links are distinguishable without relying on color.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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
○Document has a `<title>` element
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○Heading elements appear in a sequentially-descending order
○`<html>` element has a `[lang]` attribute
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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"]`
○Document has a main landmark.
○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.
○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.

Send Feedback