Skip to content
https://kununu.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
404 Error Page
Action
HTTP 202, bare page
FIX
HTTP 202, bare page
Warning::
Unexpected status code: HTTP 202
Expected HTTP 404 but received 202. This may confuse search engine crawlers.
Got: HTTP 202
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 202 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Alt Text Quality
2 of 3 images have issues
REVIEW
2 of 3 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with good alt text
3 images 1 good alt text 2 missing
IssueCount
missing2 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

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Let's confirm you ar…3.40:13.0:1
#DD6B10
#FFFFFF
Pass
title Human Verification21.00:14.5:1
#000000
#FFFFFF
Pass
p Temporary error. Ple…21.00:14.5:1
#000000
#FFFFFF
Pass
p Before proceeding to…21.00:14.5:1
#000000
#FFFFFF
Pass
p Complete the securit…21.00:14.5:1
#000000
#FFFFFF
Pass
button Begin21.00:14.5:1
#000000
#FFFFFF
Pass
option العربية21.00:14.5:1
#000000
#FFFFFF
Pass
option Čeština21.00:14.5:1
#000000
#FFFFFF
Pass
option Dansk21.00:14.5:1
#000000
#FFFFFF
Pass
option Deutsch21.00:14.5:1
#000000
#FFFFFF
Pass
option English21.00:14.5:1
#000000
#FFFFFF
Pass
option Español21.00:14.5:1
#000000
#FFFFFF
Pass
option Français21.00:14.5:1
#000000
#FFFFFF
Pass
option Bahasa Indonesia21.00:14.5:1
#000000
#FFFFFF
Pass
option Italiano21.00:14.5:1
#000000
#FFFFFF
Pass
option 日本語21.00:14.5:1
#000000
#FFFFFF
Pass
option 한국어21.00:14.5:1
#000000
#FFFFFF
Pass
option Nederlands21.00:14.5:1
#000000
#FFFFFF
Pass
option Polski21.00:14.5:1
#000000
#FFFFFF
Pass
option Português21.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.

B
Lighthouse Accessibility Audits
Score 82/100 — 7 failing, 27 passed
REVIEW
82

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
kununu auf TikTok div._socialMediaWrapper_1h3x9_315 > ul._socialMediaList_1h3x9_329 > li > div._linkWrapper_ljmkx_5
kununu auf Instagram div._socialMediaWrapper_1h3x9_315 > ul._socialMediaList_1h3x9_329 > li > div._linkWrapper_ljmkx_5
kununu auf LinkedIn div._socialMediaWrapper_1h3x9_315 > ul._socialMediaList_1h3x9_329 > li > div._linkWrapper_ljmkx_5
kununu auf YouTube div._socialMediaWrapper_1h3x9_315 > ul._socialMediaList_1h3x9_329 > li > div._linkWrapper_ljmkx_5
kununu auf WhatsApp div._socialMediaWrapper_1h3x9_315 > ul._socialMediaList_1h3x9_329 > li > div._linkWrapper_ljmkx_5
kununu auf Facebook div._socialMediaWrapper_1h3x9_315 > ul._socialMediaList_1h3x9_329 > li > div._linkWrapper_ljmkx_5

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div._fieldButtonContainer_1cux3_212 > div._fieldButtonIconsContainer_1cux3_261 > button div > div._fieldButtonContainer_1cux3_212 > div._fieldButtonIconsContainer_1cux3_261 > button
div._content_lgule_239 > div._panelHeader_lgule_248 > div._actionHeaderButtons_lgule_272 > button._button_dt5k7_213 div._content_lgule_239 > div._panelHeader_lgule_248 > div._actionHeaderButtons_lgule_272 > button._button_dt5k7_213

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.

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
Arbeitgeber bewerten div.general-spacing > div._ctaWrapper_1uu80_257 > div._linkWrapper_ljmkx_5 > a#sh-review-button
Arbeitgeber eingeben div > div._fieldButtonContainer_1cux3_212 > button#search-field-button > span._fieldButtonContent_1cux3_253
in deiner Nähe suchen div.LocalRecommendations_container__16Hg2 > div.LocalRecommendations_titleContainer__ZUUet > button#local-recommendations-location-filter > span
MatchMe Test starten div._content_uweqj_268 > div._contentButton_prtcq_33 > button#matchmetest-button > span
Zur Arbeitgebersuche div.Card_contentContainer__99fOO > div.Card_buttonContainer__AaEpc > div._linkWrapper_ljmkx_5 > a#Zur Arbeitgebersuche
Zum Gehaltscheck div.Card_contentContainer__99fOO > div.Card_buttonContainer__AaEpc > div._linkWrapper_ljmkx_5 > a#Zum Gehaltscheck
Zur Jobsuche div.Card_contentContainer__99fOO > div.Card_buttonContainer__AaEpc > div._linkWrapper_ljmkx_5 > a#Zur Jobsuche
Bewertung abgeben div._content_uweqj_268 > div._contentButton_prtcq_33 > div._linkWrapper_ljmkx_5 > a#secondary-content-button
Zum großen Report div._content_uweqj_268 > div._contentButton_prtcq_33 > div._linkWrapper_ljmkx_5 > a#featured-content-kununu-gehaltscheck-2026
Zu den Top Companys 2026 div._content_uweqj_268 > div._contentButton_prtcq_33 > div._linkWrapper_ljmkx_5 > a#tertiary-content-button

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
hier div#newsletter-sign-up-submission-state > form > p#newsletter-sign-up-legal-text > a

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
Weitere Empfehlungen für dich? ul._carouselList_12kc8_244 > li._carouselListSlide_12kc8_258 > div.ShowMoreCard_showMoreCard__F2ce1 > h4.h4-semibold
Weitere Empfehlungen für dich? ul._carouselList_12kc8_244 > li._carouselListSlide_12kc8_258 > div.ShowMoreCard_showMoreCard__F2ce1 > h4.h4-semibold
Über kununu button._header_hr65k_226 > div._headerContent_hr65k_244 > div._headerText_hr65k_235 > div._title_hr65k_220
Deutsch button._header_hr65k_226 > div._headerContent_hr65k_244 > div._headerText_hr65k_235 > div._title_hr65k_220

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
See MRL Consulting GmbH reviews div._clickableArea_1f9if_241 > div._mainContent_1f9if_300 > div._kununuScore_1f9if_309 > a._link_zh33g_1
See VESTIGA Consulting GmbH reviews div._clickableArea_1f9if_241 > div._mainContent_1f9if_300 > div._kununuScore_1f9if_309 > a._link_zh33g_1

These items highlight common accessibility best practices.

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
Arbeitgeber eingeben div > div > div._fieldButtonContainer_1cux3_212 > button#search-field-button
in deiner Nähe suchen div.Hero_localRecommendationsContainer__EfsV0 > div.LocalRecommendations_container__16Hg2 > div.LocalRecommendations_titleContainer__ZUUet > button#local-recommendations-location-filter
Herrmann Personal Heute Elektroniker (m/w/d) Hürth Vollzeit 4.5 kununu Score Ar… li._carouselListSlide_12kc8_258 > section.JobsCardWrapper_jobSectionCard__A8ddv > article._card_idx6v_222 > a.CardLink_cardLink__eQkqa
○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Let's confirm you are human
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectSelect languagearia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback