Skip to content
https://target.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
D
Heading Hierarchy
Action
51 headings, 4 skip(s)
FIX
51 headings, 4 skip(s)
Info::
Single H1 present
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::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Ideen teilen und umsetzen. Gemeinsam Innovation voranbringen. Jederzeit und überall verfügbar.
  • H2 Weltweit einzigartig: Software für Ideen- und Innovationsmanagement mit SAP-Technologie
  • H4 target Idea Management skipped
  • H4 target Campaign Management
  • H2 Software und Services für Ihre Ziele und Aufgaben
  • H4 Wettbewerbsstark und zukunftsfähig bleiben skipped
  • H4 Mitarbeiter für Veränderungen gewinnen
  • H4 Ideen- und Innovationsprozesse effektiv managen
  • H4 Zur IT-Strategie passende Lösung implementieren
  • H2 Best Practice: So bringen andere Unternehmen ihr Ideen- und Innovationsmanagement voran.
  • H2 Ideen sammeln, Innovationen erfolgreich managen - target-Software im Praxis-Check
  • H3 Fraport AG
  • H3 Diebold Nixdorf
  • H3 Das neue Ideen- und Innovationsmanagement des VBS
  • H3 Der Kontinuierliche Verbesserungsprozess
  • H2 Best Practice: So bringen andere Unternehmen ihr Ideen- und Innovationsmanagement voran.
  • H4 Ideen sammeln, Innovationen erfolgreich managen - target-Software im Praxis-Check skipped
  • H3 Erfolgreiche Unternehmen im Ideen- und Innovationsmanagement
  • H3 Ein Kontinuierliche Verbesserungsprozess
  • H3 Neues Ideen- und Innovationsmanagement für den VBS
  • H3 Runderneuerung für das Ideenmanagement von Diebold Nixdorf
  • H3 Modernes User Interface und Zugang mit mobilen Endgeräten
  • H2 Unsere Beratungskompetenz für Ihren Projekterfolg
  • H2 Lernen Sie uns kennen!
  • H2 target Software live erleben
  • H3 Target Fachtagung für Ideen- und Kampagnenmanagement
  • H2 Interesse mit uns zu arbeiten?
  • H2 Werden Sie Teil eines Netzwerks von Ideen- und Innovationsmanagern und profitieren Sie von dem Austausch mit anderen!
  • H2 Das sagen unsere Kunden
  • H4 Wir danken Konzernen und mittelständischen Unternehmen für ihr Vertrauen skipped
  • H4 Aktuelles und Wissen
  • H3 Software für Ideen und Innovationen in SAP-Technologie
  • H3 Target Fachtagung für Ideen- und Kampagnenmanagement
  • H3 target Ideenmanagement-Software einführen
  • H3 Software-Service Ideen- und Innovationsmanagement
  • H3 Kampagnenmanagement-Software für die Anwendung in der Cloud
  • H3 Unternehmensberatung Ideen- und Innovationsmanagement
  • H3 target Idea Management Release SVP 11 ist jetzt verfügbar
  • H3 Ideenmanagement-Software für die Cloud
  • H3 Erfolgreiche Unternehmen im Ideen- und Innovationsmanagement
  • H3 Neues Ideen- und Innovationsmanagement für den VBS
  • H3 Interesse an Ideen- und Innovationsmanagement Themen?
  • H3 target Idea Management Release SVP 9 ist jetzt verfügbar
  • H3 Schulungen zum Einsatz von target-Software
  • H3 Ein Kontinuierliche Verbesserungsprozess
  • H3 target Software Solution verschmilzt mit Walldorf Consulting
  • H3 Neue Gesellschafterstruktur bei target
  • H3 target-Fachtagung 2023
  • H3 target-Fachtagung 2022
  • H3 target-Fachtagung 2019
  • H3 Erneutes Audit der Datensicherheit bei target (2020)

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 ▾

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 ▾

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 ▾

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

D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
1 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 1 <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.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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

A+
Alt Text Quality
All 77 images OK
PASS
All 77 images OK
Info::
70 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
77 images 7 good alt text 70 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#toggle-essentialcheckboxNotwendige Cookiesfor/id
#toggle-mediacheckboxMedia Cookies (YouTube, Vimeo)for/id
#toggle-analyticscheckboxAnalytics (Google Analytics)for/id
#toggle-marketingcheckboxMarketing (MS Clarity)for/id
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
h1 Ideen teilen und ums…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Weltweit einzigartig…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Software und Service…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Best Practice: So br…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ideen sammeln, Innov…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Best Practice: So br…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unsere Beratungskomp…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Lernen Sie uns kenne…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 target Software live…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Interesse mit uns zu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Werden Sie Teil eine…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Das sagen unsere Kun…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fraport AG21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Diebold Nixdorf21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Das neue Ideen- und …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Der Kontinuierliche …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Erfolgreiche Unterne…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ein Kontinuierliche …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Neues Ideen- und Inn…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Runderneuerung für …21.00:13.0: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 90/100 — 3 failing, 23 passed
PASS
90

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next slide section.section20 > article.section20__article > div.slider20 > button.slider20__button
Next slide section.section20 > article.section20__article > div.slider20 > button.slider20__button

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Jetzt Software-Lösungen ansehen div.header20 > div.header20__content-wrap > div.button20 > a.button20__button
target Idea Management (On-Premise) section.section20 > article.section20__article > div.button20 > a.button20__button
target Idea Management (Cloud) section.section20 > article.section20__article > div.button20 > a.button20__button
target Campaign Management (Cloud) section.section20 > article.section20__article > div.button20 > a.button20__button
Zu den Beratungsangeboten div.flex-card > div.content-card > div.button20 > a.button20__button
Zum Kontakformular div.flex-card > div.content-card > div.button20 > a.button20__button
Demo anfordern div.flex-card > div.content-card > div.button20 > a.button20__button
Zu den Stellenangeboten div.grid > div.grid-card > div.button20 > a.button20__button
Nur notwendige Cookies div.privacy-notice > div#notice-content > div#buttonContainer > button#btnAcceptNecessary
Ich akzeptiere div.privacy-notice > div#notice-content > div#buttonContainer > button#btnAcceptAll

These are opportunities to improve the legibility of your content.

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
target Idea Management article#top > section.section20 > article.section20__article > h4.headline20
Wettbewerbsstark und zukunftsfähig bleiben article.section20__article > div.grid > div.grid-card > h4.icon-card__title
Ideen sammeln, Innovationen erfolgreich managen - target-Software im Praxis-Che… article#top > section.section20 > article.section20__article > h4.headline20
Wir danken Konzernen und mittelständischen Unternehmen für ihr Vertrauen article#top > section.section20 > article.section20__article > h4.headline20

These are opportunities to improve keyboard navigation in your application.

○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 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 use only permitted ARIA attributes
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○`[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