Skip to content
https://www.setandsetting-retreat.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
24
10 PASS 6 REVIEW 8 FIX
D
Form Accessibility
Action
6 of 21 controls have issues
FIX
6 of 21 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="submit">; <input type="submit">; <input type="submit" id="w-node-d9c5399e-a132-f889-c3be-2d6be28184ed-bde373b8">; <input type="submit" id="mc-embedded-subscribe">; <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="EMAIL" id="mce-EMAIL">
Info::
15 control(s) properly labeled
21 controls
15 labeled
1 placeholder only
5 unlabeled
ControlTypeLabelMethod
#marketing-2checkboxnone
#personalization-2checkboxnone
#analytics-2checkboxnone
#firstname-2textDein Vornamefor/id
#email-2emailDeine E-Mailfor/id
#SSR-Wenig-2radionone
#SSR-Mittel-2radionone
#SSR-Viel-2radionone
#Contact-FirstnametextVornamefor/id
#Contact-NametextNamefor/id
#Contact-EmailemailEmailfor/id
#Contact-MessagetextareaMessagefor/id
#marketing-2checkboxnone
#personalization-2checkboxnone
#analytics-2checkboxnone
#mce-EMAILemail(E-Mail-Adresse)placeholder only
#mc-embedded-subscribesubmit(none)none
inputsubmit(none)none
#w-node-d9c5399e-a132-f889-c3be-2d6be28184ed-bde373b8submit(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="submit" id="w-node-d9c5399e-a132-f889-c3be-2d6be28184ed-bde373b8">; <input type="submit" id="mc-embedded-subscribe">; <input type="submit">

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="email" name="EMAIL" id="mce-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

D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="EMAIL" id="mce-EMAIL">
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email-2" id="email-2">, <input type="email" name="Contact-Email" id="Contact-Email">, <input type="email" name="EMAIL" id="mce-EMAIL">
F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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::
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
20 landmarks
REVIEW
20 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.
Info::
No contentinfo (footer) 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 header NAV MAIN CONTENTINFO (missing!)

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
Mobile-Readable Font Sizes
98% of visible text renders at >= 12 CSS px (3 below threshold)
REVIEW
98% of visible text renders at >= 12 CSS px (3 below threshold)
Info::
3 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 11.0px ("Offen"); <div> 11.0px ("Offen"); <div> 11.0px ("Offen").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
PWA Depth
3 PWA signal(s) surfaced
REVIEW
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 25 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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.fs-cc-banner_card > div.fs-cc-banner_container > div.fs-cc-banner_buttons-wrapper > div.fs-cc-banner_close div.fs-cc-banner_card > div.fs-cc-banner_container > div.fs-cc-banner_buttons-wrapper > div.fs-cc-banner_close

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.

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
Datenschutz div.fs-cc-banner_card > div.fs-cc-banner_container > div.fs-cc-banner_text > a.fs-cc-banner_text-link
ABLEHNEN div.fs-cc-banner_card > div.fs-cc-banner_container > div.fs-cc-banner_buttons-wrapper > a.fs-cc-banner_button
ERWARTE AUSSERGEWÖHNLICHES div.padding-section-large > div.text-align-center > div.max-width-large > div.heading-style-sub-title
— Gründerin div.padding-vertical > div.quote_component > div#w-node-_14403e35-deeb-da03-b110-339bb0ae3610-f90b9a1c > div.text-color-olive
— Ärztlicher Psychotherapeut div.padding-section-large > div.w-layout-grid > div#w-node-_223035fc-7965-034e-ff24-8ba15d116920-f90b9a1c > div.text-color-olive
zu Education a.process_card > div#w-node-_16feaf44-21fb-a801-157c-cf12b4c01e26-f90b9a1c > div.button > div
zum Anmeldegespräch a.process_card > div#w-node-_2b9b0574-1f0b-fc7f-6ed1-f399d4f95314-f90b9a1c > div.button > div
zu unseren Retreats a.process_card > div#w-node-d20c8dde-2934-d41d-3c2c-3fdcbb9fe1bc-f90b9a1c > div.button > div
zu MOSAIK a.process_card > div#w-node-_6672d9ee-ab56-2e59-a746-12ce4ac71844-f90b9a1c > div.button > div
OFFEN a.overview_link > div.overview_image-wrapper > div.retreat_tag-wrapper > div.retreat_tag
Zum Anmeldegespräch div.cta_component > div.cta_button-parent > a.btn_link-ghost > div.btn_text-ghost
div#mc_embed_signup > form#wf-form-Newsletter > div#w-node-_8e9fb329-6a40-4958-c51e-1633bde373e3-bde373b8 > input#mce-EMAIL div#mc_embed_signup > form#wf-form-Newsletter > div#w-node-_8e9fb329-6a40-4958-c51e-1633bde373e3-bde373b8 > input#mce-EMAIL

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js html.w-mod-js

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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
div.padding-section-large > div.header80_content > div.rotate > a.trust-pilot-widget div.padding-section-large > div.header80_content > div.rotate > a.trust-pilot-widget
div.container-large > div.padding-section-large > div.retreat-report_component > a.retreat-report_mockup-parent div.container-large > div.padding-section-large > div.retreat-report_component > a.retreat-report_mockup-parent
div.w-layout-grid > div.footer_link-list > div.link_wrapper > a.footer_link div.w-layout-grid > div.footer_link-list > div.link_wrapper > a.footer_link

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
●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
●Input buttons have discernible text.
●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
●`<frame>` or `<iframe>` elements have a title
●Links are distinguishable without relying on color.
●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
●Identical links have the same purpose.
○`[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
○Buttons have an accessible name
○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
○`<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.
○`<input type="image">` elements have `[alt]` text
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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>`.
○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
41 headings
PASS
41 headings
Info::
Single H1 present
  • H1 Spürst du den Ruf?
  • H2 Wir auch.
  • H3 SET & SETTING in Zahlen
  • H3 Du spürst es ganz deutlich
  • H3 Eine Veränderung steht an
  • H3 Sie ist zum greifen nah
  • H3 Aber wenn, dann richtig
  • H2 Wir wissen genau, worauf es ankommt
  • H3 Sicherheit & Professionalität
  • H3 Vertrauen & Loslassen
  • H3 Erfahrung & Weisheit
  • H2 Luminary
  • H2 Der Goldstandard für psychedelische Retreats
  • H3 Ethisch
  • H3 Ausgebildet
  • H3 Zeitgemäß
  • H3 Qualitativ
  • H3 Nachhaltig
  • H3 Vorausgehend
  • H2 „Die Zeit ist reif für Psychedelika - und das mit allerhöchstem Anspruch an Sicherheit und Transparenz.“
  • H2 Für alle Fälle gewappnet: Unser Sicherheitskonzept
  • H2 Unser Beitrag zur psychedelischen Forschung
  • H3 Wie fühlt ihr euch eine Woche nach dem Retreat?
  • H3 93,9% glauben, dass die Psilocybin-Erfahrung ihr Leben nachhaltig zum Positiven verändern wird
  • H3 im Durschschnitt sind sie 30% sorgenfreier, entspannter, zufriedener und weniger gestresst
  • H2 Echte Menschen - echte Veränderung
  • H2 Der SET & SETTING Transformationsprozess
  • H3 Informiere dich zu den verschiedenen Phasen unseres Transformationsprozesses
  • H3 01 INformieren
  • H3 02 Anmeldegespräch
  • H3 03 VORBEREITUNG
  • H3 04 RETREAT
  • H3 05 Integration
  • H2 Unsere Retreat-Formate
  • H2 Unsere Nächsten Termine
  • H3 BIST DU BEREIT DIR SELBST ZU BEGEGNEN?
  • H3 DEIN NÄCHSTER SCHRITT
  • H2 Luminary
  • H2 Psychedelischer Lesestoff
  • H2 OFFENE FRAGEN?
  • H2 Kontakt
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
5 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 5 all-caps heading(s)
A+
Alt Text Quality
All 75 images OK
PASS
All 75 images OK
Info::
68 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
75 images 7 good alt text 68 decorative
All images have appropriate alt text.
A+
Form Input Types
21 form control(s) checked, no type mismatches
PASS
21 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
21 form control(s) checked, no input-semantic issues
PASS
21 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Tabindex Anti-Patterns
17 explicit tabindex attribute(s) checked, no anti-patterns
PASS
17 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 2 iframe(s) have descriptive titles
PASS
All 2 iframe(s) have descriptive titles
Info::
All 2 iframe(s) have title attributes
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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 Spürst du den Ruf?16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Wir auch.16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Wir wissen genau, wo…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Luminary16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Der Goldstandard fü…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 „Die Zeit ist reif…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Für alle Fälle gew…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Unser Beitrag zur ps…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Echte Menschen - ech…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Der SET & SETTING Tr…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Unsere Retreat-Forma…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Unsere Nächsten Ter…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Luminary16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Psychedelischer Lese…16.01:13.0:1
#000000
#E3E1D6
Pass
h2 OFFENE FRAGEN?16.01:13.0:1
#000000
#E3E1D6
Pass
h2 Kontakt16.01:13.0:1
#000000
#E3E1D6
Pass
h3 SET & SETTING in Zah…16.01:13.0:1
#000000
#E3E1D6
Pass
h3 Du spürst es ganz d…16.01:13.0:1
#000000
#E3E1D6
Pass
h3 Eine Veränderung st…16.01:13.0:1
#000000
#E3E1D6
Pass
h3 Sie ist zum greifen …16.01:13.0:1
#000000
#E3E1D6
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