Skip to content
https://strato.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Form Accessibility
Action
7 of 9 controls have issues
FIX
7 of 9 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="purpose2">; <input type="checkbox" id="purpose3">; <input type="checkbox" id="purpose4">; <input type="radio" name="time" id="time1">; <input type="radio" name="time" id="time2">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">
Info::
2 control(s) properly labeled
9 controls
2 labeled
2 placeholder only
5 unlabeled
ControlTypeLabelMethod
#purpose1checkboxnone
#domain_search_name_1776799022153textWunschdomain eingeben ...for/id
inputtext(Enter your Reference ID)placeholder only
inputtext(Paste the generated URL path here (e.g., /buy/ger/basket/addshortname/...))placeholder only
#time1radio(none)none
#time2radio(none)none
#purpose2checkbox(none)none
#purpose3checkbox(none)none
#purpose4checkbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="purpose2">; <input type="checkbox" id="purpose3">; <input type="checkbox" id="purpose4">; <input type="radio" name="time" id="time1">; <input type="radio" name="time" id="time2">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text">; <input type="text">

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
1 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 1 <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
Heading Hierarchy
15 headings, 1 skip(s)
REVIEW
15 headings, 1 skip(s)
Info::
Single H1 present
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.
  • H2 Cookie-Einstellungen
  • H2 Cookie-Einstellungen
  • H5 Notwendig skipped
  • H5 Statistik
  • H5 Marketing
  • H5 Partnerschaften
  • H1 Domain, E-Mail, Website, Hosting & Server
  • H2 Kopf voller Ideen?
  • H3 Im Web präsent ab 0 € – super easy mit KI
  • H2 (empty)
  • H3 Hosting
  • H3 Webshop
  • H3 V-Server
  • H3 STRATO Mail
  • H2 STRATO hostet energieeffizient und klimafreundlich

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

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 ✓Page Title STRATO | 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
h1 Domain, E-Mail, Website, Hosting & Serve…
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Cookie-Einstellungen
1.43:1
#000000
on
#322700
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Cookie-Einstellungen
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Kopf voller Ideen?
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
24px · bottom of viewport
h2 STRATO hostet energieeffizient und klima…
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Im Web präsent ab 0 € – super easy …
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Hosting
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Webshop
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
19px · bottom of viewport
h3 V-Server
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
19px · bottom of viewport
h3 STRATO Mail
1.64:1
#000000
on
#323232
needs 3.0:1 (large text)
19px · bottom of viewport
title STRATO | Gedacht. Gemacht.
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · top of page (header area)
p Wir setzen Cookies ein, um unsere Websei…
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · top of page (header area)
span Einstellungen
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · top of page (header area)
p können Sie auswählen, welche Cookies S…
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · above the fold
span Richtlinie zur Verwendung von Cookies
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · above the fold
p und in unseren
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · above the fold
span Datenschutzhinweisen
1.41:1
#000000
on
#322600
needs 4.5:1 (normal text)
16px · above the fold
p . Technisch notwendige Cookies werden au…
1.64:1
#000000
on
#323232
needs 4.5:1 (normal text)
16px · above the fold
span Ablehnen
1.64:1
#000000
on
#323232
needs 4.5:1 (normal text)
16px · above the fold
p gesetzt.
1.64:1
#000000
on
#323232
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Domain, E-Mail, Webs…1.64:13.0:1
#000000
#323232
Fail
h2 Cookie-Einstellungen1.43:13.0:1
#000000
#322700
Fail
h2 Cookie-Einstellungen1.64:13.0:1
#000000
#323232
Fail
h2 Kopf voller Ideen?1.64:13.0:1
#000000
#323232
Fail
h2 STRATO hostet energi…1.64:13.0:1
#000000
#323232
Fail
h3 Im Web präsent ab 0…1.64:13.0:1
#000000
#323232
Fail
h3 Hosting1.64:13.0:1
#000000
#323232
Fail
h3 Webshop1.64:13.0:1
#000000
#323232
Fail
h3 V-Server1.64:13.0:1
#000000
#323232
Fail
h3 STRATO Mail1.64:13.0:1
#000000
#323232
Fail
title STRATO | Gedacht. Ge…1.41:14.5:1
#000000
#322600
Fail
p Wir setzen Cookies e…1.41:14.5:1
#000000
#322600
Fail
span Einstellungen1.41:14.5:1
#000000
#322600
Fail
p können Sie auswähl…1.41:14.5:1
#000000
#322600
Fail
span Richtlinie zur Verwe…1.41:14.5:1
#000000
#322600
Fail
p und in unseren1.41:14.5:1
#000000
#322600
Fail
span Datenschutzhinweisen1.41:14.5:1
#000000
#322600
Fail
p . Technisch notwendi…1.64:14.5:1
#000000
#323232
Fail
span Ablehnen1.64:14.5:1
#000000
#323232
Fail
p gesetzt.1.64:14.5:1
#000000
#323232
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.

A
Landmark Structure
19 landmarks
PASS
19 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 Navigation" MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 32 images OK
PASS
All 32 images OK
Info::
32 image(s) with good alt text
32 images 32 good alt text
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 32 passed
PASS
96

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
Einstellungen div.clearfix > div > p > span.consent__link

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.

○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
●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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●ARIA IDs are unique
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○`<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>`.
○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