Skip to content
https://businessinsider.de

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
D
Alt Text Quality
Action
3 of 30 images have issues
FIX
3 of 30 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
27 decorative image(s) correctly marked
30 images 27 decorative 3 missing
IssueCount
missing3 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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #002aff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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

C
Heading Hierarchy
Action
25 headings
REVIEW
25 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)
  • H2 (empty)
  • H2 Russland will PCK Öl abdrehen: Im Extremfall droht Autofahrern und Flughäfen im Osten der Sprit auszugehen
  • H2 Kamikaze-Drohnen für die Bundeswehr: Rheinmetall erhält Millionen-Auftrag
  • H2 Geld verdienen mit KI: So kassierte ein junger Medizinstudent 800 Euro im Monat
  • H2 Ungewöhnlicher McDonald’s: Wo ihr in Deutschland mit einem Boot durch den McDrive fahren könnt
  • H2 Neue Regelung bei der Entlastungsprämie: Auch Aufstocker erhalten jetzt 1000 Euro
  • H2 Meerenge von Hormus: Diese beiden Tui-Kreuzfahrtschiffe fuhren durch
  • H2 Neue Militärstrategie: Pistorius will Bundeswehr zur stärksten Armee Europas machen
  • H2 Drohnen im Fokus – Siemens setzt stärker aufs Verteidigungsgeschäft: „Nachfrage ist leider enorm“
  • H2 Bis zu 877 Euro mehr im Monat: Tabelle zeigt, wie stark die Gehälter von Top-Beamten steigen sollen
  • H2 Betrug im Möbelhaus: Kassiererin soll jahrelang Ikea-Waren an Kasse vorbeigeschafft haben
  • H2 Ich war alleine im Surf-Camp auf Bali: Das hat mir gezeigt, warum die Gen Z den Abenteuertourismus liebt
  • H2 Luxus schwächelt, Banken stark: Das sagen Top-Manager über die Folgen des Iran-Kriegs
  • H2 Ich musste mich auf 2000 Jobs bewerben, bevor ich zwei Angebote bekam – damit hätte ich nie gerechnet
  • H2 Ich bin für einen KI-Job nach San Francisco gezogen – und diese eine Frage wird mir hier ständig gestellt
  • H2 Nach Entlassungen: Personio wird erstmals profitabel und übernimmt das KI-Startup Aurio
  • H2 Wie ein einziger Partner dieses Berliner Startup auf Millionen-ARR brachte
  • H2 Abschuss von russischer Shahed-Drohne: Ukraine setzt erstmal Kombination aus Wasser- und Abfangdrohne ein, laut Armee
  • H2 „Lang lebe das Warzenschwein“ – US-Kult-Kampfjet darf nach Iran-Einsatz weiterfliegen
  • H2 KI und Tech im Fokus: Das erwartet euch beim OMR Festival 2026 in Hamburg
  • H2 Das erste Büro von OpenAI in San Francisco steht für 1,5 Millionen Dollar zum Verkauf – so sieht es von innen aus
  • H2 Ich musste das Haus meiner Mutter verkaufen, um ihre Pflegekosten zu decken: Das Ausmisten hat uns zusammen gebracht
  • H2 Ihr wollt einen neuen Mähroboter kaufen? Das ist die beste Marke
  • H2 Sonnenbrillen mit diesem Detail sind aktuell im Trend

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

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Business Insider ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Business Insider
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Business Insider ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name Business Insider Display Mode standalone Theme Color #185f7c Background Color #185f7c Icons 4 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
title Aktuelle News von Bu…21.00:14.5:1
#000000
#FFFFFF
Pass
a Direct naar de inhou…21.00:14.5:1
#000000
#FFFFFF
Pass
a Abo21.00:14.5:1
#000000
#FFFFFF
Pass
button Einloggen21.00:14.5:1
#000000
#FFFFFF
Pass
button Registrieren21.00:14.5:1
#000000
#FFFFFF
Pass
a Mein Konto21.00:14.5:1
#000000
#FFFFFF
Pass
a Abonnent werden21.00:14.5:1
#000000
#FFFFFF
Pass
a Best of BI+21.00:14.5:1
#000000
#FFFFFF
Pass
a Best of BI+21.00:14.5:1
#000000
#FFFFFF
Pass
a FAQ21.00:14.5:1
#000000
#FFFFFF
Pass
a App21.00:14.5:1
#000000
#FFFFFF
Pass
a App21.00:14.5:1
#000000
#FFFFFF
Pass
a Newsletter21.00:14.5:1
#000000
#FFFFFF
Pass
a Newsletter21.00:14.5:1
#000000
#FFFFFF
Pass
a Insider (US)21.00:14.5:1
#000000
#FFFFFF
Pass
button Abmelden21.00:14.5:1
#000000
#FFFFFF
Pass
a Plus21.00:14.5:1
#000000
#FFFFFF
Pass
a Wirtschaft+21.00:14.5:1
#000000
#FFFFFF
Pass
a Karriere+21.00:14.5:1
#000000
#FFFFFF
Pass
a Politik+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
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 25 passed
PASS
91

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tw-mt-6 > center > a > img div.tw-mt-6 > center > a > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main#main > div.tw-px-nudge > div.tw-grid > a.tw-block main#main > div.tw-px-nudge > div.tw-grid > a.tw-block
main#main > div.tw-px-nudge > div.tw-grid > a.tw-block main#main > div.tw-px-nudge > div.tw-grid > a.tw-block
main#main > div.tw-px-nudge > div.tw-grid > a.tw-block main#main > div.tw-px-nudge > div.tw-grid > a.tw-block
div.tw-copyright > div.tw-mt-6 > center > a

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.

○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
●`[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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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.
○`[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
○`<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
○Form elements have associated labels
○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.
○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.
○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