Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 14 -1-on-focusable

FIX

0 positive, 14 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button id="search-mode-ai">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

D

Web Manifest

Action

Not found

FIX

Not found

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

Theme color only

FIX

Theme color only

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: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

7 navigation landmark(s) detected

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 7 <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

13 landmarks

REVIEW

13 landmarks

<main> landmark present

7 <nav> landmark(s) found

1 of 7 <nav> elements are unlabeled

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

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

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

Mobile Keyboard & Autofill

Action

4/7 eligible field(s) missing autocomplete or inputmode

REVIEW

4/7 eligible field(s) missing autocomplete or inputmode

4 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, search.

Got: <input type="email" name="email" id="lj-login-dialog-email">, <input type="search" id="ai-search-input">, <input type="search" name="job" id="job-input">, <input type="search" name="place" id="place-input">

B

Mobile-Readable Font Sizes

93% of visible text renders at >= 12 CSS px (5 below threshold)

REVIEW

93% of visible text renders at >= 12 CSS px (5 below threshold)

5 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <label> 10.4px ("Jobbezeichnung"); <label> 10.4px ("PLZ oder Ort"); <span> 10.4px ("Filter"); <p> 10.0px ("Technische Berufe Bauwesen"); <p> 10.0px ("Technische Berufe Bauwesen").

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Seite nicht gefunden ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H2 Anmelden
H1 Aktuelle Jobs, in die man sofort wechseln will
H2 Top Unternehmen
H2 Arbeitgeber stellen sich vor
H2 Aktuelle Premium Jobs
H2 Jobs nach Beruf
H2 Jobalarm
H2 Jobs nach Kanton
H2 Folgen Sie uns
H2 Cookies & Datenschutz

A+

Heading Text Quality

All 10 heading(s) have substantive, well-formed text

PASS

All 10 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A

Alt Text Quality

All 137 images OK

PASS

All 137 images OK

3 image(s) with alt text over 125 characters

6 decorative image(s) correctly marked

128 image(s) with good alt text

137 images 128 good alt text 6 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

All 38 controls labeled

PASS

All 38 controls labeled

38 control(s) properly labeled

38 controls

38 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#lj-login-dialog-email	email	E-Mail	for/id
#lj-login-dialog-password	password	Passwort	for/id
#lj-login-dialog-captcha	number	Rechenaufgabe	for/id
#ai-search-input	search	KI-Suche: Job, Ort oder Situation beschreiben	aria-label
#job-input	search	Was suchst du?	aria-label
#place-input	search	Wo suchst du?	aria-label
#place-range	range	Umkreis in Kilometern	aria-label
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
regionen[]	checkbox		none
#pensum-min	range	Von	for/id
#pensum-max	range	Bis	for/id
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
typ[]	checkbox		none
aktualitaet	radio		none
aktualitaet	radio		none
aktualitaet	radio		none
aktualitaet	radio		none
aktualitaet	radio		none
#sort-date	radio		none
#sort-distance	radio		none
#cookie-pref-analytics	checkbox	Statistik	for/id
#cookie-pref-social	checkbox	Social Media	for/id
#cookie-pref-listing_stats	checkbox	Inserat-Statistik	for/id

A

Link & Button Quality

174 links, 42 buttons — all OK

PASS

174 links, 42 buttons — all OK

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://facebook.com/localjobch; https://www.linkedin.com/company/98689972/; https://instagram.com/localjob_ch

171 link(s) with descriptive text

174 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://facebook.com/localjobch	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/9868997…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://instagram.com/localjob_ch	Instagram	new tab	Add '(opens in new tab)' to text

213 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://facebook.com/localjobch; https://www.linkedin.com/company/98689972/; https://instagram.com/localjob_ch

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

38 form control(s) checked, no type mismatches

PASS

38 form control(s) checked, no type mismatches

No input-type mismatches detected

A

Form Input Quality

1 input-semantic issue(s) across 38 form control(s)

PASS

1 input-semantic issue(s) across 38 form control(s)

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="number" name="captcha_answer">.

A+

Document Language

Lang attribute set to "de-CH"

PASS

Lang attribute set to "de-CH"

<html lang="de-CH"> is set and valid

Got: de-CH

A

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /css/print.css?v=1.1.05

Print Stylesheet ✓ Print Optimized

Print stylesheet /css/print.css?v=1.1.05 ✓Inline @media print Not detected ✗

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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)

Element	Ratio	Required	FG	BG	Result
h1 Aktuelle Jobs, in di…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Anmelden	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top Unternehmen	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Arbeitgeber stellen …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Aktuelle Premium Job…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Jobs nach Beruf	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Jobalarm	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Jobs nach Kanton	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Folgen Sie uns	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookies & Datenschut…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Jobs und Stellenange…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Loading	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Laden …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Suchen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Firmen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Regionen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Inserieren	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Ratgeber	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Berufsgruppen	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Orte	21.00:1	4.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 100/100 — 1 failing, 29 passed

PASS

100

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.

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
FILTER Alle Regionen `div.job-search-filter__search-shell > div.ratgeber-filter__bar > div.ratgeber-filter__field > button.job-search-filter__filter-hit`

○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

●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

●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.

●`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

●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

○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

○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.

○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.

○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.