Skip to content
https://adac.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 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::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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::
3 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 3 <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
23 landmarks
REVIEW
23 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 "Top Themen" MAIN CONTENTINFO footer

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

B
Heading Hierarchy
13 headings
REVIEW
13 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Teurer Flop an der Tanke? Was das Österreich-Modell bisher gebracht hat
  • H3 Aktuelles
  • H2 Produkte
  • H3 Mit dem ADAC Newsletter immer top informiert!
  • H2 Aktuelle Videos
  • H2 Rund ums Fahrzeug
  • H2 Reise & Freizeit
  • H2 Gesundheit
  • H2 Sicher & Mobil
  • H2 Rund ums Haus
  • H2 Motorrad
  • H2 Veranstaltungen
  • H2 Neueste Artikel

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Fehlerseite 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Teurer Flop an der Tanke? Was das Öster…
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Produkte
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aktuelle Videos
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Rund ums Fahrzeug
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Reise & Freizeit
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Gesundheit
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sicher & Mobil
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Rund ums Haus
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Motorrad
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Veranstaltungen
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Neueste Artikel
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Aktuelles
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mit dem ADAC Newsletter immer top inform…
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
title ADAC: Allgemeiner Deutscher Automobil-Cl…
1.69:1
#000000
on
#403300
needs 4.5:1 (normal text)
16px · top of page (header area)
a Navigation
1.69:1
#000000
on
#403300
needs 4.5:1 (normal text)
16px · top of page (header area)
a Suche
1.36:1
#000000
on
#112637
needs 4.5:1 (normal text)
16px · top of page (header area)
a Seiteninhalt
1.21:1
#000000
on
#27151A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Fußzeile
1.23:1
#000000
on
#0C1B36
needs 4.5:1 (normal text)
16px · above the fold
span Top Themen
1.19:1
#000000
on
#0B1831
needs 4.5:1 (normal text)
16px · above the fold
a Mitglied werden
1.14:1
#000000
on
#0A132B
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Teurer Flop an der T…2.03:13.0:1
#000000
#404040
Fail
h2 Produkte2.03:13.0:1
#000000
#404040
Fail
h2 Aktuelle Videos2.03:13.0:1
#000000
#404040
Fail
h2 Rund ums Fahrzeug2.03:13.0:1
#000000
#404040
Fail
h2 Reise & Freizeit2.03:13.0:1
#000000
#404040
Fail
h2 Gesundheit2.03:13.0:1
#000000
#404040
Fail
h2 Sicher & Mobil2.03:13.0:1
#000000
#404040
Fail
h2 Rund ums Haus2.03:13.0:1
#000000
#404040
Fail
h2 Motorrad2.03:13.0:1
#000000
#404040
Fail
h2 Veranstaltungen2.03:13.0:1
#000000
#404040
Fail
h2 Neueste Artikel2.03:13.0:1
#000000
#404040
Fail
h3 Aktuelles2.03:13.0:1
#000000
#404040
Fail
h3 Mit dem ADAC Newslet…2.03:13.0:1
#000000
#404040
Fail
title ADAC: Allgemeiner De…1.69:14.5:1
#000000
#403300
Fail
a Navigation1.69:14.5:1
#000000
#403300
Fail
a Suche1.36:14.5:1
#000000
#112637
Fail
a Seiteninhalt1.21:14.5:1
#000000
#27151A
Fail
a Fußzeile1.23:14.5:1
#000000
#0C1B36
Fail
span Top Themen1.19:14.5:1
#000000
#0B1831
Fail
a Mitglied werden1.14:14.5:1
#000000
#0A132B
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.

A+
Alt Text Quality
All 62 images OK
PASS
All 62 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
17 decorative image(s) correctly marked
Info::
43 image(s) with good alt text
62 images 43 good alt text 17 decorative
IssueCount
too long2 image(s)
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
#newsletter-inputemailE-Mail-Adresse eingebenaria-label
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 28 passed
PASS
100

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.

○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 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.
●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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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