Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 7 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: rgb(31, 41, 55)

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

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

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) without accessible label

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

Got: <input type="checkbox" id="mobile-menu-toggle">; <input type="checkbox" id="fullscreen-submenu-sammelsurium">

2 controls

0 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#mobile-menu-toggle	checkbox	(none)	none
#fullscreen-submenu-sammelsurium	checkbox	(none)	none

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

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

Link & Button Quality

1 issue(s) across 22 links and 4 buttons

REVIEW

1 issue(s) across 22 links and 4 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://erhoeremich.de ("")

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: mailto:mario@erhoeremich.de?subject=Contact; https://www.openbsd.org/; https://gohugo.io/; https://blowfish.page/

17 link(s) with descriptive text

22 links

0 empty

1 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	ERHÖRE MICH !	img no alt	Add alt attribute to the image
mailto:mario@erhoeremich.de?subject=Cont…	Email	new tab	Add '(opens in new tab)' to text
https://erhoeremich.de	Link	generic text	Replace with descriptive text
Before: Link Suggested: Erhoeremich.De
https://www.openbsd.org/	OpenBSD	new tab	Add '(opens in new tab)' to text
https://gohugo.io/	Hugo	new tab	Add '(opens in new tab)' to text
https://blowfish.page/	Blowfish	new tab	Add '(opens in new tab)' to text

21 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://erhoeremich.de ("")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

mailto:mario@erhoeremich.de?subject=Contact; https://www.openbsd.org/; https://gohugo.io/; https://blowfish.page/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ...But only very few people understand the deeper meaning of this. ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

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 ERHÖRE MICH !

1.75:1

#000000

#303742

needs 3.0:1 (large text)

32px · above the fold

h2 ein Memorandum vergangener Emissionen

1.78:1

#000000

#313843

needs 3.0:1 (large text)

24px · mid-page

title ERHÖRE MICH !

1.27:1

#000000

#191F27

needs 4.5:1 (normal text)

16px · top of page (header area)

span ↓

1.25:1

#000000

#181E26

needs 4.5:1 (normal text)

16px · top of page (header area)

a Zum Hauptinhalt springen

1.30:1

#000000

#1B212B

needs 4.5:1 (normal text)

16px · top of page (header area)

span ERHÖRE MICH !

1.28:1

#000000

#1A2028

needs 4.5:1 (normal text)

16px · top of page (header area)

a ERHÖRE MICH !

1.47:1

#000000

#252B33

needs 4.5:1 (normal text)

16px · above the fold

span Sammelsurium

1.51:1

#000000

#272D35

needs 4.5:1 (normal text)

16px · above the fold

span Potpurri aus ehemals 4von8 ausgestrahlte…

1.42:1

#000000

#242831

needs 4.5:1 (normal text)

16px · above the fold

span Sammelsurium

1.36:1

#000000

#1F252F

needs 4.5:1 (normal text)

16px · above the fold

span Potpurri aus ehemals 4von8 ausgestrahlte…

1.59:1

#000000

#2B303A

needs 4.5:1 (normal text)

16px · above the fold

span unter Umständen Merkwürdig

1.65:1

#000000

#2D333D

needs 4.5:1 (normal text)

16px · above the fold

span unter Umständen Merkwürdig

1.80:1

#000000

#323943

needs 4.5:1 (normal text)

16px · above the fold

a ↑

1.49:1

#000000

#252C37

needs 4.5:1 (normal text)

16px · mid-page

a Impressum, Disclaimer und so’n angst-m…

1.58:1

#000000

#28303B

needs 4.5:1 (normal text)

16px · mid-page

1.58:1

#000000

#28303B

needs 4.5:1 (normal text)

16px · mid-page

a OpenBSD

1.39:1

#000000

#1E2732

needs 4.5:1 (normal text)

16px · mid-page

p 7.4 -> 7.8)

1.53:1

#000000

#262E3A

needs 4.5:1 (normal text)

16px · mid-page

p Erstellt mit

1.43:1

#000000

#212935

needs 4.5:1 (normal text)

16px · mid-page

a Hugo

1.69:1

#000000

#2C3541

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 ERHÖRE MICH !	1.75:1	3.0:1	#000000	#303742	Fail
h2 ein Memorandum verga…	1.78:1	3.0:1	#000000	#313843	Fail
title ERHÖRE MICH !	1.27:1	4.5:1	#000000	#191F27	Fail
span ↓	1.25:1	4.5:1	#000000	#181E26	Fail
a Zum Hauptinhalt spri…	1.30:1	4.5:1	#000000	#1B212B	Fail
span ERHÖRE MICH !	1.28:1	4.5:1	#000000	#1A2028	Fail
a ERHÖRE MICH !	1.47:1	4.5:1	#000000	#252B33	Fail
span Sammelsurium	1.51:1	4.5:1	#000000	#272D35	Fail
span Potpurri aus ehemals…	1.42:1	4.5:1	#000000	#242831	Fail
span Sammelsurium	1.36:1	4.5:1	#000000	#1F252F	Fail
span Potpurri aus ehemals…	1.59:1	4.5:1	#000000	#2B303A	Fail
span unter Umständen Mer…	1.65:1	4.5:1	#000000	#2D333D	Fail
span unter Umständen Mer…	1.80:1	4.5:1	#000000	#323943	Fail
a ↑	1.49:1	4.5:1	#000000	#252C37	Fail
a Impressum, Disclaime…	1.58:1	4.5:1	#000000	#28303B	Fail
p ©2026 Mario (web &…	1.58:1	4.5:1	#000000	#28303B	Fail
a OpenBSD	1.39:1	4.5:1	#000000	#1E2732	Fail
p 7.4 -> 7.8)	1.53:1	4.5:1	#000000	#262E3A	Fail
p Erstellt mit	1.43:1	4.5:1	#000000	#212935	Fail
a Hugo	1.69:1	4.5:1	#000000	#2C3541	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+

Heading Hierarchy

2 headings

PASS

2 headings

Single H1 present

H1 ERHÖRE MICH !
H2 ein Memorandum vergangener Emissionen

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 decorative image(s) correctly marked

2 images 2 decorative

All images have appropriate alt text.

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "de"

PASS

Lang attribute set to "de"

<html lang="de"> is set and valid

Got: de

A+

Tabindex Anti-Patterns

3 explicit tabindex attribute(s) checked, no anti-patterns

PASS

3 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 12 visible text node(s) render at >= 12 CSS pixels

PASS

All 12 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

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).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 passed

PASS

100

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.

○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

●Image elements have `[alt]` attributes

●`[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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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 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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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.

○Identical links have the same purpose.

○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.

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