Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 REVIEW 6 FIX

Alt Text Quality

Action

2 of 47 images have issues

FIX

2 of 47 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

42 decorative image(s) correctly marked

3 image(s) with good alt text

47 images 3 good alt text 42 decorative 2 missing

Issue	Count
missing	2 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

Link & Button Quality

Action

6 issue(s) across 121 links and 30 buttons

FIX

6 issue(s) across 121 links and 30 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.wbs.legal/kontakt/; #; a.nav-link (#209 on page); #

3 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.youtube.com/watch?v=l8CWwdsZ5b8"]; a[href="https://www.youtube.com/watch?v=wRfTKBECDNA"]; a[href="https://www.youtube.com/watch?v=DDZmE5Wjv9g"]

10 link(s) open in new tab without warning

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

Got: https://www.youtube.com/c/KanzleiWBS; https://www.wbs.legal/?utm_source=mybusiness&utm_medium=organic&utm_campaign=…; /datenschutzerklaerung/#newsletter; https://www.youtube.com/KanzleiWBS; https://wbs.law/46svMfO; https://wbs.law/4fvVBQy; https://twitter.com/solmecke; https://www.linkedin.com/company/wilde-beuger-solmecke-rechtsanw%C3%A4lte/; https://discordapp.com/invite/vcCCvdz; https://www.wbs.legal/feed

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#472 on page); button (#474 on page)

104 link(s) with descriptive text

121 links

4 empty

0 generic text

10 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.wbs.legal/kontakt/	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.youtube.com/watch?v=l8CWwdsZ…	<img decoding="async" width="1…	img no alt	Add alt attribute to the image
https://www.youtube.com/c/KanzleiWBS	Zum WBS YouTube Kanal	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=wRfTKBEC…	<img decoding="async" src="htt…	img no alt	Add alt attribute to the image
https://www.youtube.com/watch?v=DDZmE5Wj…	<img decoding="async" src="htt…	img no alt	Add alt attribute to the image
https://www.wbs.legal/?utm_source=mybusi…	WBS.LEGAL - summary business	new tab	Add '(opens in new tab)' to text
/datenschutzerklaerung/#newsletter	WBS.LEGAL-Datenschutzerklärun…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/KanzleiWBS	YouTube	new tab	Add '(opens in new tab)' to text
https://wbs.law/46svMfO	Instagram	new tab	Add '(opens in new tab)' to text
https://wbs.law/4fvVBQy	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/solmecke	Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/wilde-b…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://discordapp.com/invite/vcCCvdz	Discord	new tab	Add '(opens in new tab)' to text
https://www.wbs.legal/feed	RSS	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

132 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.wbs.legal/kontakt/; #; a.nav-link (#209 on page); #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.youtube.com/watch?v=l8CWwdsZ5b8"]; a[href="https://www.youtube.com/watch?v=wRfTKBECDNA"]; a[href="https://www.youtube.com/watch?v=DDZmE5Wjv9g"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.youtube.com/c/KanzleiWBS; https://www.wbs.legal/?utm_source=mybusiness&utm_medium=organic&utm_campaign=…; /datenschutzerklaerung/#newsletter; https://www.youtube.com/KanzleiWBS; https://wbs.law/46svMfO; https://wbs.law/4fvVBQy; https://twitter.com/solmecke; https://www.linkedin.com/company/wilde-beuger-solmecke-rechtsanw%C3%A4lte/; https://discordapp.com/invite/vcCCvdz; https://www.wbs.legal/feed

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

Icon-only buttons need an aria-label so screen readers can announce them.

button (#472 on page); button (#474 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

8 landmarks

REVIEW

8 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

Action

22 headings, 2 skip(s)

REVIEW

22 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

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

H1 WBS.LEGAL
H2 Seit über 30 Jahren im Medien- und Urheberrecht zu Hause
H4 Bundesweit aktiv skipped
H4 Hochqualifizierte Anwälte
H4 Stets für Sie erreichbar
H2 Aktuelle Themen im Schnellcheck
H3 Soforthilfe vom Anwalt
H2 Unsere Tätigkeitsgebiete
H2 Die Kanzlei WBS.LEGAL
H2 Rundgang durch die Kanzlei
H2 Wir versorgen Sie mit den aktuellsten News und Urteilen
H3 US-Kartellverfahren: Gericht stellt illegales Google-Monopol bei Onlinewerbung fest
H3 Regulierungen im E-Commerce: Bürokratie bremst Online-Handel massiv aus
H3 Kinderschutz im Netz: Griechenland fordert Social-Media-Verbot für Unter-15-Jährige
H3 Unternehmensgründung in 24 Stunden: Auf dem Weg zur vollautomatisierten Verwaltung?
H3 Auslandsaufenthalt über drei Monate: Wehrpflichtgesetz verhängt Meldepflicht für Männer
H3 Legal Tech NRW Meetup: Austausch, Innovation und KI im Fokus
H2 Sehen Sie sich unsere neuesten YouTube-Videos an
H2 Das sagen unsere Mandanten über uns
H2 Bleiben Sie mit uns in Kontakt – mit unserem kostenlosen Newsletter!
H2 Newsletter (kurz)
H5 (empty)

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 ▾

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

Form Accessibility

Action

3 of 6 controls have issues

REVIEW

3 of 6 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit" id="gform_submit_button_8">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="s">; <input type="search" name="s">

3 control(s) properly labeled

6 controls

3 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
#input_8_10	text	Instagram	for/id
#input_8_3	email	E-Mail(erforderlich)	for/id
#choice_8_4_1	checkbox	Ich möchte den kostenlosen WBS.LEGAL-Newsletter abonnieren und wöchentlich über wichtige juristische News und meine Rechte informiert werden & stimme der Verarbeitung meiner Daten gemäß der WBS.LEGAL-Datenschutzerklärung zu.	for/id
s	search	(Was suchen Sie?)	placeholder only
s	search	(Was suchen Sie?)	placeholder only
#gform_submit_button_8	submit	(none)	none

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

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.

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

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Seite wurde nicht gefunden. - WBS.LEGAL ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Favicon & Branding

11 icon(s) detected

REVIEW

11 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

h2 Bleiben Sie mit uns in Kontakt – mit u…

1.00:1

#FBEDEA

needs 3.0:1 (large text)

24px · bottom of viewport

a Skip to main content

2.08:1

#000000

#3B424E

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 WBS.LEGAL	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Seit über 30 Jahren…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Aktuelle Themen im S…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Unsere Tätigkeitsge…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Die Kanzlei WBS.LEGA…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Rundgang durch die K…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Wir versorgen Sie mi…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Sehen Sie sich unser…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Das sagen unsere Man…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h2 Bleiben Sie mit uns …	1.00:1	3.0:1	#FBEDEA	#FBEDEA	Fail
h2 Newsletter (kurz)	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 Soforthilfe vom Anwa…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 US-Kartellverfahren:…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 Regulierungen im E-C…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 Kinderschutz im Netz…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 Unternehmensgründun…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 Auslandsaufenthalt �…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
h3 Legal Tech NRW Meetu…	18.40:1	3.0:1	#000000	#FBEDEA	Pass
title WBS.LEGAL \| Rechtsan…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	2.08:1	4.5:1	#000000	#3B424E	Fail

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.

Lighthouse Accessibility Audits

Score 82/100 — 6 failing, 25 passed

REVIEW

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Auch wir benötigen die Zustimmung zu Cookies und Technologien, um Inhalte und A… `div#app-focus-lock > div#center-layer-focus-lock > div.sc-cwHptR > div#uc-center-container`

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.