Skip to content
https://morgenpost.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Heading Hierarchy
Action
47 headings, 1 skip(s)
FIX
47 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Anzeigen
  • H3 Weitere Angebote
  • H3 Abo-Welt
  • H2 Aktuelle Schlagzeilen
  • H3 Dominique Horwitz: Zwei Seelen reißen krass in dieser Brust gestern um 23:04 Uhr
  • H3 Berlin-Rückkehr nach sechs Jahren: FC Bayern zieht ins Pokalfinale ein gestern um 22:45 Uhr
  • H3 Popstar Dua Lipa finanziert Pick-up für ukrainisches Frontlazarett gestern um 21:52 Uhr
  • H3 Trump oder die Mullahs: „Am Ende kommt es darauf an, wer zuerst zuckt” gestern um 21:43 Uhr
  • H3 Trotz Niederlage: Deshalb kann Union Berlin gegen Meister Bayern feiern gestern um 21:28 Uhr
  • H3 Taiwan kopiert US-Angriffsdrohne: Was kann die „Papa Delta“? gestern um 21:06 Uhr
  • H2 Videos
  • H2 Was Deutschland bewegt
  • H2 Bezirke
  • H2 Blaulicht-Nachrichten
  • H4 Morgenpost Späti skipped
  • H4 Morgenpost Späti
  • H2 Sport
  • H2 Interaktiv
  • H2 Exklusiv
  • H2 Meistgelesen
  • H2 Ratgeber & Wissen
  • H2 Podcast
  • H2 (empty)
  • H2 Spiele
  • H3 Daily Kreuzworträtsel
  • H3 Wordle
  • H3 Pärchensuche
  • H3 Sudoku
  • H3 Schiffe versenken
  • H3 Brückenrätsel
  • H3 Zahlenkreuzworträtsel
  • H2 Meinung
  • H2 Kolumne
  • H2 Eat Club
  • H2 IMTEST
  • H2 Kultur
  • H2 Politik
  • H2 Panorama
  • H2 Wirtschaft
  • H2 Gastronomie
  • H2 Finanzen
  • H3 (empty)
  • H4 Abo
  • H4 Specials
  • H4 Service
  • H4 In eigener Sache
  • H4 Ratgeber & Wissen

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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::
4 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 4 <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
52 landmarks
REVIEW
52 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <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 "Anzeigen" MAIN ASIDE "Inhalt von einem externen Anbieter" 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
Alt Text Quality
29 of 150 images have issues
REVIEW
29 of 150 images have issues
Warning::
29 image(s) with filename as alt text
Info::
9 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
111 image(s) with good alt text
150 images 111 good alt text 1 decorative 29 generic
IssueCount
filename29 image(s)
too long9 image(s)
C
Form Accessibility
Action
3 of 29 controls have issues
REVIEW
3 of 29 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="userAccountCheckbox">; <input type="range">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
Info::
26 control(s) properly labeled
29 controls
26 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#footer-Abo-0radioAbofor/id
#footer-Specials-1radioSpecialsfor/id
#footer-Service-2radioServicefor/id
#footer-In-eigener-Sache-3radioIn eigener Sachefor/id
#footer-Ratgeber---Wissen-4radioRatgeber & Wissenfor/id
querysearchSuchearia-label
#burger-navigation-Mein-Bezirk-0radioMein Bezirkfor/id
#burger-navigation-Mein-Verein-1radioMein Vereinfor/id
#burger-navigation-Berlin-2radioBerlinfor/id
#burger-navigation-Verkehr-3radioVerkehrfor/id
#burger-navigation-Blaulicht-4radioBlaulichtfor/id
#burger-navigation-Panorama-5radioPanoramafor/id
#burger-navigation-Sport-6radioSportfor/id
#burger-navigation-Politik-7radioPolitikfor/id
#burger-navigation-Kultur-8radioKulturfor/id
#burger-navigation-Wirtschaft-9radioWirtschaftfor/id
#burger-navigation-Gastronomie-10radioGastronomiefor/id
#burger-navigation-Ratgeber---Wissen-11radioRatgeber & Wissenfor/id
#burger-navigation-Berliner-helfen-12radioBerliner helfenfor/id
#burger-navigation-Morgenpost-English-13radioMorgenpost Englishfor/id
#burger-navigation-Interaktiv-14radioInteraktivfor/id
#burger-navigation-Infografik-15radioInfografikfor/id
#burger-navigation-Alle-Themen-16radioAlle Themenfor/id
#burger-navigation-Abo-Welt-0radioAbo-Weltfor/id
#burger-navigation-Weitere-Angebote-1radioWeitere Angebotefor/id
#burger-navigation-Anzeigen-2radioAnzeigenfor/id
emailemail(E-Mail-Adresse eingeben)placeholder only
#userAccountCheckboxcheckbox(none)none
inputrange(none)none

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

<input type="checkbox" id="userAccountCheckbox">; <input type="range">

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.

<input type="email" name="email">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Aktuelle Nachrichten aus Berlin und der Welt - Berliner Morgenpost ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
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 #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 89/100 — 5 failing, 28 passed
REVIEW
89

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
Datenschutzerklärung div.cmpboxinner > div.cmpboxbtns > div.cmpmore > a.cmpmorelink
Impressum div.cmpboxinner > div.cmpboxbtns > div.cmpmore > a.cmpmorelink

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Datenschutzcenter div > div.choice-item > div.cmpboxtxt > a.cmplink

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main#pageMainContent > div.mx-4 > aside.w-full > iframe#tank-widget main#pageMainContent > div.mx-4 > aside.w-full > iframe#tank-widget

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Morgenpost Späti section.mx-auto > div.flex > div.order-1 > h4.functional-heading-lg

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
31 Min. div > div.mt-1 > div > button.podcast-play
○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.
●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
●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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Identical links have the same purpose.
○`[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
○No form fields have multiple labels
○`<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
○Select elements have associated label elements.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Berliner Morgenpost
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Berliner Morgenpost ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Berliner Morgenpost Display Mode standalone Theme Color #005d28 Background Color #FFFFFF Icons 2 icon(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)
ElementRatioRequiredFGBGResult
h2 Aktuelle Schlagzeile…10.14:13.0:1
#000000
#B4B4B5
Pass
h2 Videos10.14:13.0:1
#000000
#B4B4B5
Pass
h2 Was Deutschland bewe…10.14:13.0:1
#000000
#B4B4B5
Pass
h2 Exklusiv10.14:13.0:1
#000000
#B4B4B5
Pass
h2 Meistgelesen10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Anzeigen10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Weitere Angebote10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Abo-Welt10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Dominique Horwitz: Z…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Berlin-Rückkehr nac…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Popstar Dua Lipa fin…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Trump oder die Mulla…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Trotz Niederlage: De…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Taiwan kopiert US-An…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Daily Kreuzworträts…10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Wordle10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Pärchensuche10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Sudoku10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Schiffe versenken10.14:13.0:1
#000000
#B4B4B5
Pass
h3 Brückenrätsel10.14:13.0:1
#000000
#B4B4B5
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.

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

Send Feedback