Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-vj2s9q

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at http://www.rheinmetall.ch/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: http://www.rheinmetall.ch/manifest.json

Manifest contains invalid JSON.

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 ✗

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark found

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

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

3 icon(s) detected

REVIEW

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

h2 Systeme &

1.68:1

#000000

#233644

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Karriere bei

1.68:1

#000000

#233644

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Investor

1.68:1

#000000

#233644

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Unsere

1.68:1

#000000

#233644

needs 3.0:1 (large text)

24px · bottom of viewport

title Der Technologiekonzern für Sicherheit u…

4.24:1

#000000

#707070

needs 4.5:1 (normal text)

16px · top of page (header area)

a jumpToMain

4.24:1

#000000

#707070

needs 4.5:1 (normal text)

16px · top of page (header area)

span Menü

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · top of page (header area) · 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 Taking responsibilit…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 News	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Systeme &	1.68:1	3.0:1	#000000	#233644	Fail
h2 Karriere bei	1.68:1	3.0:1	#000000	#233644	Fail
h2 Investor	1.68:1	3.0:1	#000000	#233644	Fail
h2 Unsere	1.68:1	3.0:1	#000000	#233644	Fail
title Der Technologiekonze…	4.24:1	4.5:1	#000000	#707070	Fail
a jumpToMain	4.24:1	4.5:1	#000000	#707070	Fail
span Menü	2.60:1	4.5:1	#000000	#505050	Fail
span siteLogo	20.12:1	4.5:1	#000000	#FAFAFA	Pass
label Suche	20.12:1	4.5:1	#000000	#FAFAFA	Pass
p Die Rheinmetall AG s…	20.12:1	4.5:1	#000000	#FAFAFA	Pass
p Durch unsere Arbeit …	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div 6632187	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div Beschäftigte*	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div 010	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div Standorte*	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div 197	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div MrdEUR Umsatz**	20.12:1	4.5:1	#000000	#FAFAFA	Pass
div 51230	20.12:1	4.5:1	#000000	#FAFAFA	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+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Taking responsibility in a changing world
H2 News Watch
H2 Systeme & Produkte
H2 Karriere bei Rheinmetall
H2 Investor Relations
H2 Unsere Verantwortung

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 26 images OK

PASS

All 26 images OK

26 image(s) with good alt text

26 images 26 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-toggle	text	Suche	for/id

Link & Button Quality

43 links, 5 buttons — all OK

PASS

43 links, 5 buttons — all OK

11 link(s) open in new tab without warning

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

Got: /de/verantwortung/verantwortung-uebersicht; https://dimensions-magazin.de/; https://twitter.com/RheinmetallAG; https://www.linkedin.com/company/rheinmetall; https://www.instagram.com/rheinmetallag/; https://www.kununu.com/de/rheinmetall-group; https://www.youtube.com/@RheinmetallGroup; https://www.glassdoor.de/%C3%9Cberblick/Arbeit-bei-Rheinmetall-EI_IE10472.11,…; https://www.xing.com/pages/rheinmetallgroup; https://whatsapp.com/channel/0029VaEgocfGE56unmdUrb1U (+1 more)

32 link(s) with descriptive text

43 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/de/verantwortung/verantwortung-uebersic…	Mehr erfahren	new tab	Add '(opens in new tab)' to text
https://dimensions-magazin.de/	Mehr erfahren	new tab	Add '(opens in new tab)' to text
https://twitter.com/RheinmetallAG	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/rheinme…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/rheinmetallag/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.kununu.com/de/rheinmetall-gr…	kununu	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@RheinmetallGrou…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.glassdoor.de/%C3%9Cberblick/…	glassdoor	new tab	Add '(opens in new tab)' to text
https://www.xing.com/pages/rheinmetallgr…	XING	new tab	Add '(opens in new tab)' to text
https://whatsapp.com/channel/0029VaEgocf…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://rheinmetall.integrityline.org/	Regelverstoß melden	new tab	Add '(opens in new tab)' to text

37 links and buttons have descriptive text

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

/de/verantwortung/verantwortung-uebersicht; https://dimensions-magazin.de/; https://twitter.com/RheinmetallAG; https://www.linkedin.com/company/rheinmetall; https://www.instagram.com/rheinmetallag/; https://www.kununu.com/de/rheinmetall-group; https://www.youtube.com/@RheinmetallGroup; https://www.glassdoor.de/%C3%9Cberblick/Arbeit-bei-Rheinmetall-EI_IE10472.11,…; https://www.xing.com/pages/rheinmetallgroup; https://whatsapp.com/channel/0029VaEgocfGE56unmdUrb1U (+1 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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "search-toggle" should use type="search" (currently type="text")

Field name "search-toggle" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

1 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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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 105 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

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.

A+

Lighthouse Accessibility Audits

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

●Select elements have associated label elements.

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

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

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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

○`<object>` elements have alternate text

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

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