Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

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

13 headings

REVIEW

13 headings

No H1 heading found

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

H2 Calendar
H2 Transparenz in Thüringen nicht abservieren!
H2 Kanzleisoftware in der Cloud lässt Daten regnen
H2 CCC lehnt Palantir-Gesetze und biometrische Rasterfahnung ab
H2 Debug-Modus bei Legal-Tech-Plattform advocado legt sensible Daten offen
H2 Datenleck im CampusNet
H2 Automatisierte Verhaltensüberwachung: Gefährlichen Mumpitz einstellen
H2 Gesundheitsdatengau verhindern
H2 CCC fordert, die VDS endgültig zu begraben
H2 CCC unterstützt den monatlichen Digital Independence Day
H2 Keine Aushöhlung digitaler Rechte in der EU!
H2 Tags
H2 Featured

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

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" id="menu-toggle">

1 control(s) rely on placeholder only

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

Got: <input type="search" name="search_term" id="search_term">

1 control(s) properly labeled

3 controls

1 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#light-mode	checkbox	Switch between dark and light mode	aria-label
#search_term	search	(suchen)	placeholder only
#menu-toggle	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

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

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title The page you were looking for doesn't exist (404) ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Link & Button Quality

67 links, 0 buttons — all OK

PASS

67 links, 0 buttons — all OK

67 link(s) with descriptive text

67 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

67 links and buttons have descriptive text

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)

Element	Ratio	Required	FG	BG	Result
h2 Calendar	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tags	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title CCC \| Startseite	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span lights	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Club	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CCC Regional	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Unterstützen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Themen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Veranstaltungen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Publikationen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Transparenz	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Kontakt	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Der Chaos Computer C…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Seine Aktivitäten r…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Kampagnen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Veranstaltungen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p , Politikberatung,	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Mitteilungen	21.00:1	4.5:1	#000000	#FFFFFF	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 92/100 — 2 failing, 16 passed

PASS

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.

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
Kampagnen `div#center_column > div.article > p > a`
Veranstaltungen `div#center_column > div.article > p > a`
Mitteilungen `div#center_column > div.article > p > a`
dezentralen Gruppen im deutschsprachigen Raum `div#center_column > div.article > p > a`
Veranstaltungen `div#center_column > div.article > p > a`
Publikationen `div#center_column > div.article > p > a`
Hackerethik `div#center_column > div.article > p > a`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
mehr … `div.article > div.article_partial > p.excerpt > a.inactive`
84 `div#wrapper > div#center_column > div.pagination > a`
85 `div#wrapper > div#center_column > div.pagination > a`
Next » `div#wrapper > div#center_column > div.pagination > a.next_page`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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-hidden="true"]` is not present on the document `<body>`

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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○`<frame>` or `<iframe>` elements have a title

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

○Skip links are focusable.

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

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

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

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