Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 7 REVIEW 4 FIX

Link & Button Quality

Action

18 issue(s) across 216 links and 22 buttons

FIX

18 issue(s) across 216 links and 22 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /?paged=2; https://www.netcup.com; #; #

13 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/in/benediktfilip/; https://www.xing.com/profile/Benedikt_Filip/; https://github.com/filipnet; https://www.flickr.com/photos/benedikt_filip; https://www.linkedin.com/in/benediktfilip/; https://www.xing.com/profile/Benedikt_Filip/; https://github.com/filipnet; https://www.flickr.com/photos/benedikt_filip; https://www.wpmoose.com/themes/yuki-ever-blog/; https://www.wpmoose.com (+3 more)

14 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.yuki-dropdown-toggle (#106 on page); button.yuki-dropdown-toggle (#111 on page); button.yuki-dropdown-toggle (#116 on page); button.yuki-dropdown-toggle (#121 on page); button.yuki-dropdown-toggle (#127 on page); button.yuki-dropdown-toggle (#132 on page); button.yuki-dropdown-toggle (#137 on page); button.yuki-dropdown-toggle (#142 on page); button.yuki-dropdown-toggle (#147 on page); button.yuki-dropdown-toggle (#152 on page) (+4 more)

199 link(s) with descriptive text

216 links

4 empty

0 generic text

13 new tab

14 empty buttons

Element	Text	Issue	Suggested Fix
https://www.linkedin.com/in/benediktfili…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.xing.com/profile/Benedikt_Fi…	XING	new tab	Add '(opens in new tab)' to text
https://github.com/filipnet	GitHub	new tab	Add '(opens in new tab)' to text
https://www.flickr.com/photos/benedikt_f…	Flickr	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/benediktfili…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.xing.com/profile/Benedikt_Fi…	XING	new tab	Add '(opens in new tab)' to text
https://github.com/filipnet	GitHub	new tab	Add '(opens in new tab)' to text
https://www.flickr.com/photos/benedikt_f…	Flickr	new tab	Add '(opens in new tab)' to text
https://www.filipnet.de/wavelog-mobile-a…	Wavelog Mobile Android App	img no alt	Add alt attribute to the image
https://www.filipnet.de/voxdmr/	VoxDMR Setup Guide	img no alt	Add alt attribute to the image
https://www.filipnet.de/qso-repeater/	How to use a Repeater for a QS…	img no alt	Add alt attribute to the image
https://www.filipnet.de/meshcore-node-se…	MeshCore: Node Setup Guide	img no alt	Add alt attribute to the image
https://www.filipnet.de/dmr-id-registrat…	DMR ID Registration for Ham Ra…	img no alt	Add alt attribute to the image
https://www.filipnet.de/repeater-digital…	Repeater Configuration: DMR	img no alt	Add alt attribute to the image
https://www.filipnet.de/repeater-analog-…	Repeater Configuration: Analog…	img no alt	Add alt attribute to the image
https://www.filipnet.de/simplex-analog-f…	Analog FM Configuration	img no alt	Add alt attribute to the image
https://www.filipnet.de/simplex-digital-…	Digital DMR Configuration	img no alt	Add alt attribute to the image
/?paged=2	(empty)	empty	Add link text or aria-label
https://www.netcup.com	(empty)	empty	Add link text or aria-label
https://www.wpmoose.com/themes/yuki-ever…	Yuki Ever Blog Theme	new tab	Add '(opens in new tab)' to text
https://www.wpmoose.com	WP Moose	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://en.support.wordpress.com/cookies…	View the official website	new tab	Add '(opens in new tab)' to text
https://matomo.org/faq/general/faq_146/	View the official website	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://www.filipnet.de/privacy-policy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

207 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/?paged=2; https://www.netcup.com; #; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.linkedin.com/in/benediktfilip/; https://www.xing.com/profile/Benedikt_Filip/; https://github.com/filipnet; https://www.flickr.com/photos/benedikt_filip; https://www.linkedin.com/in/benediktfilip/; https://www.xing.com/profile/Benedikt_Filip/; https://github.com/filipnet; https://www.flickr.com/photos/benedikt_filip; https://www.wpmoose.com/themes/yuki-ever-blog/; https://www.wpmoose.com (+3 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.yuki-dropdown-toggle (#106 on page); button.yuki-dropdown-toggle (#111 on page); button.yuki-dropdown-toggle (#116 on page); button.yuki-dropdown-toggle (#121 on page); button.yuki-dropdown-toggle (#127 on page); button.yuki-dropdown-toggle (#132 on page); button.yuki-dropdown-toggle (#137 on page); button.yuki-dropdown-toggle (#142 on page); button.yuki-dropdown-toggle (#147 on page); button.yuki-dropdown-toggle (#152 on page) (+4 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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 ✗

Heading Hierarchy

9 headings

REVIEW

9 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Wavelog Mobile Android App
H2 VoxDMR Setup Guide
H2 How to use a Repeater for a QSO
H2 MeshCore: Node Setup Guide
H2 DMR ID Registration for Ham Radio
H2 Repeater Configuration: DMR
H2 Repeater Configuration: Analog FM
H2 Analog FM Configuration
H2 Digital DMR Configuration

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

4 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

94% of visible text renders at >= 12 CSS px (9 below threshold)

REVIEW

94% of visible text renders at >= 12 CSS px (9 below threshold)

9 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: <time> 10.4px ("Sep 25, 2026"); <time> 10.4px ("Sep 21, 2026"); <time> 10.4px ("Sep 19, 2026"); <time> 10.4px ("Sep 14, 2026"); <time> 10.4px ("Sep 8, 2026").

Favicon & Branding

4 icon(s) detected

REVIEW

4 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 Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 10 pass AA only

title filipnet.de - step in and make yourself …

1.12:1

#000000

#0F1218

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.10:1

#000000

#0C1016

needs 4.5:1 (normal text)

16px · top of page (header area)

span Search for:

1.24:1

#000000

#161C2C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.14:1

#000000

#10141E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Content Overview

1.15:1

#000000

#121519

needs 4.5:1 (normal text)

16px · above the fold

a Photography

1.13:1

#000000

#0F1319

needs 4.5:1 (normal text)

16px · above the fold

a IT-Infrastructure

1.11:1

#000000

#0D1117

needs 4.5:1 (normal text)

16px · above the fold

a Automation

1.38:1

#000000

#102642

needs 4.5:1 (normal text)

16px · above the fold · 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
title filipnet.de - step i…	1.12:1	4.5:1	#000000	#0F1218	Fail
a Skip to content	1.10:1	4.5:1	#000000	#0C1016	Fail
span Search for:	1.24:1	4.5:1	#000000	#161C2C	Fail
a Home	1.14:1	4.5:1	#000000	#10141E	Fail
a Content Overview	1.15:1	4.5:1	#000000	#121519	Fail
a Photography	1.13:1	4.5:1	#000000	#0F1319	Fail
a IT-Infrastructure	1.11:1	4.5:1	#000000	#0D1117	Fail
a Automation	1.38:1	4.5:1	#000000	#102642	Fail
a Virtualization	7.37:1	4.5:1	#000000	#999999	Pass
a Security	7.19:1	4.5:1	#000000	#979797	Pass
a Linux	6.99:1	4.5:1	#000000	#949595	Pass
a Windows	6.99:1	4.5:1	#000000	#949595	Pass
a Internet of Things	6.99:1	4.5:1	#000000	#949595	Pass
a Smart Home	6.99:1	4.5:1	#000000	#949595	Pass
a Home Assistant	6.99:1	4.5:1	#000000	#949595	Pass
a Ham Radio	6.99:1	4.5:1	#000000	#949595	Pass
a Meshtastic	6.99:1	4.5:1	#000000	#949595	Pass
a filipnet.de	6.99:1	4.5:1	#000000	#949595	Pass
span step in and make you…	6.99:1	4.5:1	#000000	#949595	Pass
a filipnet.de	6.99:1	4.5:1	#000000	#949595	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.

Lighthouse Accessibility Audits

Score 83/100 — 4 failing, 21 passed

REVIEW

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
ul#menu-primary > li#menu-item-1288 > a > button.yuki-dropdown-toggle `ul#menu-primary > li#menu-item-1288 > a > button.yuki-dropdown-toggle`
ul#menu-primary > li#menu-item-1291 > a > button.yuki-dropdown-toggle `ul#menu-primary > li#menu-item-1291 > a > button.yuki-dropdown-toggle`
ul#menu-primary > li#menu-item-4825 > a > button.yuki-dropdown-toggle `ul#menu-primary > li#menu-item-4825 > a > button.yuki-dropdown-toggle`

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
main.yuki-posts-container > div#content > nav.yuki-pagination > a.yuki-btn `main.yuki-posts-container > div#content > nav.yuki-pagination > a.yuki-btn`
div.prose > aside#block-9 > figure.wp-block-image > a `div.prose > aside#block-9 > figure.wp-block-image > a`
span#tarteaucitronDisclaimerAlert > span.tarteaucitronDisclaimerAlertInner > div.tarteaucitronDisclaimerHead > a.dsgvoaio_close_btn `span#tarteaucitronDisclaimerAlert > span.tarteaucitronDisclaimerAlertInner > div.tarteaucitronDisclaimerHead > a.dsgvoaio_close_btn`

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.

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
Disclaimer: `aside#block-6 > p.wp-block-paragraph > strong > mark.has-inline-color`
✓ Accept `div#tarinnerinner > div.dsgvonoticebtns > div.dsgvonoticebtnsinner > span#tarteaucitronPersonalize`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tutorial `article#post-5140 > div.card-content > div.entry-tags > a.entry-tax-item`
Wavelog `article#post-5140 > div.card-content > div.entry-tags > a.entry-tax-item`
Legal Notice / Impressum `div.yuki-menu-wrap > ul#menu-mandatory-information > li#menu-item-1082 > a`
Privacy Policy / Datenschutz `div.yuki-menu-wrap > ul#menu-mandatory-information > li#menu-item-1083 > a`

These items highlight common accessibility best practices.

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

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

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

●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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

○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

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

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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

All 9 heading(s) have substantive, well-formed text

PASS

All 9 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

10 decorative image(s) correctly marked

4 image(s) with good alt text

14 images 4 good alt text 10 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-form-6ae7af11aafd3	search	Search for:	none
#matomoAllowed	checkbox		none
#dsgvoaio-checkbox-essentials	checkbox	Essentials	none
#dsgvoaio-checkbox-statistics	checkbox	Statistics	none

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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 "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

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

PASS

2 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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - filipnet.de ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

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