Skip to content
https://telekom.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-n40tts
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://telekom.net/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://telekom.net/manifest.json

Manifest contains invalid JSON.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
13 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 13 <nav> element(s)
Back to Top
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.
B
Landmark Structure
16 landmarks
REVIEW
16 landmarks
Info::
<main> landmark present
Info::
13 <nav> landmark(s) found
Warning::
10 of 13 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV "Main Navigation" MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA 2 pass AA only
h1 Home
1.84:1
#000000
on
#6F1242
needs 3.0:1 (large text)
32px · bottom of viewport
h2 At a glance
1.84:1
#000000
on
#6F1242
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Specials
1.84:1
#000000
on
#6F1242
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Note
1.84:1
#000000
on
#6F1242
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cookies and similar technologies
1.84:1
#000000
on
#6F1242
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Sorry, we are not allowed to show you th…
1.84:1
#000000
on
#6F1242
needs 3.0:1 (large text)
19px · bottom of viewport
span Company profile
3.17:1
#000000
on
#485F76
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Worldwide
2.61:1
#000000
on
#2C5377
needs 4.5:1 (normal text)
16px · top of page (header area)
span Topic specials
2.50:1
#000000
on
#295075
needs 4.5:1 (normal text)
16px · above the fold
span Data privacy and security
2.32:1
#000000
on
#234B71
needs 4.5:1 (normal text)
16px · above the fold
span Digital Responsibility
2.20:1
#000000
on
#1D486E
needs 4.5:1 (normal text)
16px · above the fold
span Management unplugged
1.52:1
#000000
on
#3F2533
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Strategy
1.91:1
#000000
on
#612A3F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Management and Corporate Governance
1.96:1
#000000
on
#513358
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Board of Management
1.39:1
#000000
on
#152B15
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

5 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)
ElementRatioRequiredFGBGResult
h1 Home1.84:13.0:1
#000000
#6F1242
Fail
h2 At a glance1.84:13.0:1
#000000
#6F1242
Fail
h2 Specials1.84:13.0:1
#000000
#6F1242
Fail
h2 Note1.84:13.0:1
#000000
#6F1242
Fail
h2 Cookies and similar …1.84:13.0:1
#000000
#6F1242
Fail
h3 Sorry, we are not al…1.84:13.0:1
#000000
#6F1242
Fail
title Corporate Website: I…5.24:14.5:1
#000000
#7F7F7F
Pass
span Company5.24:14.5:1
#000000
#7F7F7F
Pass
span Company profile3.17:14.5:1
#000000
#485F76
Fail
span Worldwide2.61:14.5:1
#000000
#2C5377
Fail
span Topic specials2.50:14.5:1
#000000
#295075
Fail
span Data privacy and sec…2.32:14.5:1
#000000
#234B71
Fail
span Digital Responsibili…2.20:14.5:1
#000000
#1D486E
Fail
span Management unplugged1.52:14.5:1
#000000
#3F2533
Fail
span Strategy1.91:14.5:1
#000000
#612A3F
Fail
span Management and Corpo…1.96:14.5:1
#000000
#513358
Fail
span Board of Management1.39:14.5:1
#000000
#152B15
Fail
span Supervisory Board21.00:14.5:1
#000000
#FFFFFF
Pass
span Remuneration21.00:14.5:1
#000000
#FFFFFF
Pass
span Reports and declarat…21.00:14.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+
Heading Hierarchy
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 Home
  • H2 At a glance
  • H2 Specials
  • H3 Sorry, we are not allowed to show you this content due to your cookie settings.
  • H2 Note
  • H2 Cookies and similar technologies
A+
Alt Text Quality
All 37 images OK
PASS
All 37 images OK
Info::
37 image(s) with good alt text
37 images 37 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
querysearchSearch termnone
doctypeselectContent typenone
inputtextContent type Blog postMedia informationNewsVideo Content typenone
dateFrom_stringtextChoose date or period (from)none
dateTo_stringtextChoose period (to)none
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 27 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 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
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback