Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

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

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Form Accessibility

Action

5 of 6 controls have issues

REVIEW

5 of 6 controls have issues

5 control(s) without accessible label

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

Got: <input type="checkbox" id="toctogglecheckbox">; <input type="checkbox">; <input type="checkbox">; <input type="submit" name="fulltext" id="mw-searchButton">; <input type="submit" name="go" id="searchButton">

1 control(s) properly labeled

6 controls

1 labeled

0 placeholder only

5 unlabeled

Control	Type	Label	Method
#searchInput	search	Suche	for/id
input	checkbox	(none)	none
input	checkbox	(none)	none
#toctogglecheckbox	checkbox	(none)	none
#mw-searchButton	submit	(none)	none
#searchButton	submit	(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

2 issue(s) across 151 links and 2 buttons

REVIEW

2 issue(s) across 151 links and 2 buttons

2 link(s) with no accessible text

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

Got: a#top; /Datei:Betreuungszahlen.gif

149 link(s) with descriptive text

151 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/Datei:Betreuungszahlen.gif	(empty)	empty	Add link text or aria-label

151 links and buttons have descriptive text

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

a#top; /Datei:Betreuungszahlen.gif

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Beavercheck-404-test-jgpujr – Online-Lexikon Betreuungsrecht ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

10 <nav> landmark(s) found

All <nav> elements are properly labeled

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.

Search landmark present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

30 headings

PASS

30 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Hauptseite
H2 Inhaltsverzeichnis
H2 Das Online-Lexikon Betreuungsrecht
H1 Kleines Betreuungs-ABC duplicate H1
H2 Das Betreuungsrecht?
H2 Die Betreuung?
H2 Der Berufsbetreuer?
H2 Das Betreuungsgericht?
H2 Die Betreuungsbehörde?
H2 Der Betreuungsverein?
H2 Short information in english
H2 Videos und Podcasts
H2 Siehe auch unter
H2 Zu diesem Lexikon
H3 Allgemeines
H3 Wie finde ich etwas
H3 Links auf dieses Lexikon
H3 Links in Beschlüssen
H3 Autorenhinweise
H2 Navigationsmenü
H3 Meine Werkzeuge
H3 Namensräume
H3 Varianten
H3 Ansichten
H3 Mehr
H3 Suche
H3 Navigation
H3 BGT e.V.
H3 Mitmachen
H3 Werkzeuge

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

1 of 2 images have issues

PASS

1 of 2 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

2 images 1 decorative 1 generic

Issue	Count
generic	1 image(s)

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
h1 Hauptseite	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Inhaltsverzeichnis	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Navigationsmenü	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Online-Lexikon Betre…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Aus Online-Lexikon B…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Zur Navigation sprin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Zur Suche springen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Das Online-Lexikon B…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Kleines Betreuungs-A…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2.1	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Das Betreuungsrecht?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2.2	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Die Betreuung?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2.3	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Der Berufsbetreuer?	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2.4	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Das Betreuungsgerich…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2.5	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Die Betreuungsbehör…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 2.6	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 29 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

●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

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

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

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

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

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