Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 7 REVIEW 3 FIX

Heading Hierarchy

Action

147 headings, 3 skip(s)

FIX

147 headings, 3 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Stellenmarkt 1.009
H2 Neu Werbefrei
H2 Nutzen Sie dejure.org ohne Ablenkung: PUR!
H2 Verlauf
H2 Meistgenutzte Gesetze
H2 Meistgenutzte Gesetze
H2 Gesetzesübersicht nach Rechtsgebieten
H3 Bürgerliches Recht
H3 Arbeitsrecht
H3 Handelsrecht, Gesellschaftsrecht
H3 Insolvenzrecht
H3 Versicherungsrecht
H3 Gewerblicher Rechtsschutz, Immaterialgüterrecht
H3 Wettbewerbsrecht
H3 Vergaberecht
H3 Zivilverfahrensrecht
H3 Kostenrecht
H3 Strafrecht, Strafverfahrensrecht
H3 Allgemeines Verwaltungsrecht
H3 Recht des öffentlichen Dienstes
H3 Recht des Datenschutzes und der öffentlichen Informationen
H3 Ordnungsrecht
H3 Steuerrecht
H3 Sozialrecht
H3 Ausländerrecht
H3 Gewerberecht, Preisrecht
H3 Produktsicherheit und -gestaltung
H3 Kreditwesen-, Börsen- und Wertpapierrecht
H3 Telekommunikationsrecht, Energiewirtschaft
H3 Medienrecht
H3 Baurecht, Umweltrecht, Naturschutzrecht, Raumordnung
H3 Abfallrecht
H3 Kommunalrecht
H3 Wohnungsrecht
H3 Verkehrsrecht/ Straßenrecht
H3 Sonstiges
H3 Verwaltungsprozeßrecht, Verfassungsprozeßrecht
H3 Gerichtsverfassungsrecht und Recht der juristischen Berufe
H3 Recht der freien Berufe
H3 Junge Menschen
H3 Übergreifendes
H2 Alphabetische Gesetzesübersicht
H4 A skipped
H4 B
H4 D
H4 E
H4 F
H4 G
H4 H
H4 I
H4 J
H4 K
H4 L
H4 M
H4 N
H4 O
H4 P
H4 R
H4 S
H4 T
H4 U
H4 V
H4 W
H4 Z
H2 Rechtsprechung
H2 Bundesgesetzblatt
H4 Nachrichten skipped
H4 22.04.2026
H4 21.04.2026
H4 20.04.2026
H4 17.04.2026
H4 16.04.2026
H4 15.04.2026
H4 14.04.2026
H4 13.04.2026
H4 10.04.2026
H4 09.04.2026
H4 08.04.2026
H4 07.04.2026
H4 02.04.2026
H4 01.04.2026
H4 31.03.2026
H4 30.03.2026
H4 27.03.2026
H4 26.03.2026
H4 25.03.2026
H4 24.03.2026
H4 23.03.2026
H4 20.03.2026
H4 19.03.2026
H4 18.03.2026
H4 17.03.2026
H4 16.03.2026
H4 13.03.2026
H4 12.03.2026
H4 11.03.2026
H4 10.03.2026
H4 09.03.2026
H4 06.03.2026
H4 05.03.2026
H4 04.03.2026
H4 03.03.2026
H4 02.03.2026
H4 27.02.2026
H2 Juristische Vernetzungs- funktion
H2 Bundesgesetzblatt heute neu
H2 Nachrichten
H4 Nachrichten skipped
H4 22.04.2026
H4 21.04.2026
H4 20.04.2026
H4 17.04.2026
H4 16.04.2026
H4 15.04.2026
H4 14.04.2026
H4 13.04.2026
H4 10.04.2026
H4 09.04.2026
H4 08.04.2026
H4 07.04.2026
H4 02.04.2026
H4 01.04.2026
H4 31.03.2026
H4 30.03.2026
H4 27.03.2026
H4 26.03.2026
H4 25.03.2026
H4 24.03.2026
H4 23.03.2026
H4 20.03.2026
H4 19.03.2026
H4 18.03.2026
H4 17.03.2026
H4 16.03.2026
H4 13.03.2026
H4 12.03.2026
H4 11.03.2026
H4 10.03.2026
H4 09.03.2026
H4 06.03.2026
H4 05.03.2026
H4 04.03.2026
H4 03.03.2026
H4 02.03.2026
H4 27.02.2026
H2 Über dejure.org/Rechtliches/Impressum
H2 Stellenmarkt 1.009

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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: #003366

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.

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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.

Page Structure — as a screen reader sees it

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

Alt Text Quality

1 of 3 images have issues

REVIEW

1 of 3 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 image(s) with good alt text

3 images 2 good alt text 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

60 issue(s) across 958 links and 2 buttons

REVIEW

60 issue(s) across 958 links and 2 buttons

59 link(s) with no accessible text

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

Got: a#uebersicht; /pur; a (#185 on page); a (#264 on page); a (#304 on page); a (#334 on page); a (#350 on page); a (#370 on page); a (#394 on page); a (#410 on page) (+49 more)

1 button(s) with no accessible text

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

Got: button#top_button

899 link(s) with descriptive text

958 links

59 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/pur	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

900 links and buttons have descriptive text

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

a#uebersicht; /pur; a (#185 on page); a (#264 on page); a (#304 on page); a (#334 on page); a (#350 on page); a (#370 on page); a (#394 on page); a (#410 on page) (+49 more)

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

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

button#top_button

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

Favicon & Branding

13 icon(s) detected

REVIEW

13 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

Valid manifest

REVIEW

Valid manifest

Name present: dejure.org

192x192 icon present

PWA Install Criteria Not Installable

Name dejure.org ✓192×192 icon ✓512×512 icon ✗Start URL . ✓Display Mode browser ✗

Name dejure.org Display Mode browser Background Color #036 Icons 5 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h2 Stellenmarkt

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Nutzen Sie dejure.org ohne Ablenkung: PU…

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Verlauf

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Meistgenutzte Gesetze

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Meistgenutzte Gesetze

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Gesetzesübersicht nach Rechtsgebieten

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Alphabetische Gesetzesübersicht

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Rechtsprechung

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Bundesgesetzblatt

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Juristische Vernetzungs- funktion

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Bundesgesetzblatt

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Nachrichten

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Über dejure.org/Rechtliches/Impressum

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Stellenmarkt

2.91:1

#000000

#575757

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Bürgerliches Recht

2.91:1

#000000

#575757

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Arbeitsrecht

2.91:1

#000000

#575757

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Handelsrecht, Gesellschaftsrecht

2.91:1

#000000

#575757

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Insolvenzrecht

2.91:1

#000000

#575757

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Versicherungsrecht

2.91:1

#000000

#575757

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Stellenmarkt	2.91:1	3.0:1	#000000	#575757	Fail
h2 Werbefrei	7.23:1	3.0:1	#FFFFFF	#575757	Pass
h2 Nutzen Sie dejure.or…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Verlauf	2.91:1	3.0:1	#000000	#575757	Fail
h2 Meistgenutzte Gesetz…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Meistgenutzte Gesetz…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Gesetzesübersicht n…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Alphabetische Gesetz…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Rechtsprechung	2.91:1	3.0:1	#000000	#575757	Fail
h2 Bundesgesetzblatt	2.91:1	3.0:1	#000000	#575757	Fail
h2 Juristische Vernetzu…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Bundesgesetzblatt	2.91:1	3.0:1	#000000	#575757	Fail
h2 Nachrichten	2.91:1	3.0:1	#000000	#575757	Fail
h2 Über dejure.org/Rec…	2.91:1	3.0:1	#000000	#575757	Fail
h2 Stellenmarkt	2.91:1	3.0:1	#000000	#575757	Fail
h3 Bürgerliches Recht	2.91:1	3.0:1	#000000	#575757	Fail
h3 Arbeitsrecht	2.91:1	3.0:1	#000000	#575757	Fail
h3 Handelsrecht, Gesell…	2.91:1	3.0:1	#000000	#575757	Fail
h3 Insolvenzrecht	2.91:1	3.0:1	#000000	#575757	Fail
h3 Versicherungsrecht	2.91:1	3.0:1	#000000	#575757	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.

Lighthouse Accessibility Audits

Action

Score 79/100 — 2 failing, 11 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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#suche > form#suchfeldform_ajax > span#suchfeldset_ajax > input#suchfeld_ajax `div#suche > form#suchfeldform_ajax > span#suchfeldset_ajax > input#suchfeld_ajax`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Buttons have an accessible name

●`[accesskey]` values are unique

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○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

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

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 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="search" name="Suchenach" id="suchfeld_ajax">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#suchfeld_ajax	search	(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

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 Fehler - dejure.org ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: https://j.dejure.org/jcg/print-05.css

Print Stylesheet ✓ Print Optimized

Print stylesheet https://j.dejure.org/jcg/print-05.css ✓Inline @media print Not detected ✗

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