Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 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

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (6 below threshold)

6 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: <span> 11.5px ("01"); <span> 11.5px ("02"); <span> 11.5px ("03"); <span> 11.5px ("04"); <span> 11.5px ("05").

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 Site not found · GitHub Pages ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

span Menü

4.29:1

#000000

#717264

needs 4.5:1 (normal text)

16px · top of page (header area)

a Meine Preise

1.83:1

#000000

#373B2F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Meine Services

1.91:1

#000000

#383E34

needs 4.5:1 (normal text)

16px · above the fold

a Kontakt

2.05:1

#000000

#3C4339

needs 4.5:1 (normal text)

16px · above the fold

p Atelier Haarkunst

2.01:1

#000000

#39423A

needs 4.5:1 (normal text)

16px · above the fold

span Dein

1.85:1

#000000

#313D36

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Hallo, ich bin Evi	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Das sagen meine Kund…	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Meine Services im Ü…	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Meine Preise im Übe…	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Inspiration für dei…	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Dein Spezialist für…	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Häufige Fragen	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h2 Sachsen – Anhalt	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h3 Damen	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h3 Herren & Kids	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h3 Farbe	18.44:1	3.0:1	#000000	#F3F0E8	Pass
h3 Beautys & Specials	18.44:1	3.0:1	#000000	#F3F0E8	Pass
title Friseur Magdeburg - …	18.44:1	4.5:1	#000000	#F3F0E8	Pass
a Zum Inhalt springen	18.44:1	4.5:1	#000000	#F3F0E8	Pass
span Menü	4.29:1	4.5:1	#000000	#717264	Fail
a Meine Preise	1.83:1	4.5:1	#000000	#373B2F	Fail
a Meine Services	1.91:1	4.5:1	#000000	#383E34	Fail
a Kontakt	2.05:1	4.5:1	#000000	#3C4339	Fail
p Atelier Haarkunst	2.01:1	4.5:1	#000000	#39423A	Fail
span Dein	1.85:1	4.5:1	#000000	#313D36	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.

Landmark Structure

22 landmarks

PASS

22 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 Dein Friseur im Süden von Magdeburg
H2 Hallo, ich bin Evi
H2 Das sagen meine Kundinnen
H2 Meine Services im Überblick
H2 Meine Preise im Überblick
H3 Damen
H3 Herren & Kids
H3 Farbe
H3 Beautys & Specials
H2 Inspiration für deinen neuen Look
H2 Dein Spezialist für Haarverlängerungen in Magdeburg.
H2 Häufige Fragen
H2 Sachsen – Anhalt

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 26 images OK

PASS

All 26 images OK

3 decorative image(s) correctly marked

23 image(s) with good alt text

26 images 23 good alt text 3 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

35 links, 37 buttons — all OK

PASS

35 links, 37 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://www.google.com/maps/place/Atelier+Haarkunst/@52.0738465,11.6697913,17…; https://www.google.com/maps/place/Atelier+Haarkunst/@52.0738465,11.6697913,17…; https://www.google.com/maps/place/Atelier+Haarkunst/@52.0738465,11.6697913,17…; https://r3webdesign.de/; https://www.instagram.com/atelierhaarkunst/; https://www.facebook.com/AtelierHaarkunst

29 link(s) with descriptive text

35 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.google.com/maps/place/Atelie…	Alle Bewertungen auf Google an…	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/place/Atelie…	Route in Google Maps öffnen	new tab	Add '(opens in new tab)' to text
/evi/	Atelier Haarkunst – Startsei…	img no alt	Add alt attribute to the image
https://www.google.com/maps/place/Atelie…	Route planen	new tab	Add '(opens in new tab)' to text
https://r3webdesign.de/	r³webdesign	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/atelierhaarkun…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/AtelierHaarkuns…	Facebook	new tab	Add '(opens in new tab)' to text

66 links and buttons have descriptive text

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

https://www.google.com/maps/place/Atelier+Haarkunst/@52.0738465,11.6697913,17…; https://www.google.com/maps/place/Atelier+Haarkunst/@52.0738465,11.6697913,17…; https://www.google.com/maps/place/Atelier+Haarkunst/@52.0738465,11.6697913,17…; https://r3webdesign.de/; https://www.instagram.com/atelierhaarkunst/; https://www.facebook.com/AtelierHaarkunst

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

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "de"

PASS

Lang attribute set to "de"

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

Got: de

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 29 passed

PASS

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.

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
Sa `div.footer__col > dl.hours > div.hours__row > dt`

These are opportunities to improve the legibility of your content.

○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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

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

○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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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