Skip to content
https://tdsolarenergy.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO (missing!)

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

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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'>.
favicon.ico Missing
PNG Icons Present
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
Theme color only
FIX
Theme color only
Info::
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: #000014
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 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.

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::
2 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 2 <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
Heading Hierarchy
33 headings, 2 skip(s)
REVIEW
33 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Professionelle DC-Montage für Photovoltaikanlagen in ganz Deutschland
  • H2 Ein eingespieltes Montageteam für Photovoltaik in ganz Deutschland.
  • H2 Ein vollständiges Leistungsspektrum für die DC-Seite.
  • H3 DC-Montage von Solarmodulen
  • H3 Montage von Unterkonstruktionen
  • H3 Verlegung von DC-Kabeln
  • H3 Erdung der PV-Anlage
  • H3 Montage von Kabelkanälen
  • H3 Vogelschutz für Solaranlagen
  • H3 Foto-Dokumentation & Prüfung
  • H3 Deutschlandweiter Einsatz
  • H2 So läuft die Zusammenarbeit ab.
  • H5 Anfrage & Beratung skipped
  • H5 Kostenschätzung
  • H5 Montageplanung
  • H5 Durchführung der Montage
  • H5 Qualitätskontrolle
  • H5 Übergabe & Foto-Dokumentation
  • H2 Ausrüstung & Qualität nach deutschen Standards.
  • H2 Projektbeispiele aus unserem Montagealltag.
  • H3 Private PV-Anlagen
  • H3 Gewerbliche Dächer
  • H3 Industrielle PV-Projekte
  • H3 B2B / Subunternehmer
  • H2 PV-Montage anfragen.
  • H2 Häufige Fragen.
  • H2 Bereit für Ihre PV-Montage?
  • H4 Navigation skipped
  • H4 Kontakt
  • H4 Adresse
  • H4 Öffnungszeiten
  • H4 Standort
  • H2 Projekt anfragen

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

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

C
Mobile Keyboard & Autofill
Action
4/8 eligible field(s) missing autocomplete or inputmode
REVIEW
4/8 eligible field(s) missing autocomplete or inputmode
Warning::
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: tel, email.
Got: <input type="tel" name="telefon" id="f-phone">, <input type="email" name="email" id="f-email">, <input type="tel" name="telefon" id="m-phone">, <input type="email" name="email" id="m-email">
B
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (4 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (4 below threshold)
Info::
4 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: <small> 11.0px ("DC Montage"); <a> 11.0px ("Impressum"); <a> 11.0px ("Datenschutzerklärung"); <a> 11.0px ("Cookie-Richtlinie").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title This Page Does Not Exist 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
h1 Professionelle
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
32px · bottom of viewport
h1 für
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Photovoltaikanlagen in ganz Deutschland
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Ein eingespieltes Montageteam für Photo…
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ein vollständiges Leistungsspektrum
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 für die DC-Seite.
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 So läuft die Zusammenarbeit ab.
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ausrüstung & Qualität nach deutschen S…
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Projektbeispiele aus unserem
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Montagealltag.
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PV-Montage anfragen.
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Häufige Fragen.
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Bereit für Ihre PV-Montage?
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Projekt anfragen
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
24px · bottom of viewport
h3 DC-Montage von Solarmodulen
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Montage von Unterkonstruktionen
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Verlegung von DC-Kabeln
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Erdung der PV-Anlage
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Montage von Kabelkanälen
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Vogelschutz für Solaranlagen
2.40:1
#000000
on
#474B52
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Professionelle2.40:13.0:1
#000000
#474B52
Fail
h1 für2.40:13.0:1
#000000
#474B52
Fail
h1 Photovoltaikanlagen …2.40:13.0:1
#000000
#474B52
Fail
h2 Ein eingespieltes Mo…2.40:13.0:1
#000000
#474B52
Fail
h2 Ein vollständiges L…2.40:13.0:1
#000000
#474B52
Fail
h2 für die DC-Seite.2.40:13.0:1
#000000
#474B52
Fail
h2 So läuft die Zusamm…2.40:13.0:1
#000000
#474B52
Fail
h2 Ausrüstung & Qualit…2.40:13.0:1
#000000
#474B52
Fail
h2 Projektbeispiele aus…2.40:13.0:1
#000000
#474B52
Fail
h2 Montagealltag.2.40:13.0:1
#000000
#474B52
Fail
h2 PV-Montage anfragen.2.40:13.0:1
#000000
#474B52
Fail
h2 Häufige Fragen.2.40:13.0:1
#000000
#474B52
Fail
h2 Bereit für Ihre PV-…2.40:13.0:1
#000000
#474B52
Fail
h2 Projekt anfragen2.40:13.0:1
#000000
#474B52
Fail
h3 DC-Montage von Solar…2.40:13.0:1
#000000
#474B52
Fail
h3 Montage von Unterkon…2.40:13.0:1
#000000
#474B52
Fail
h3 Verlegung von DC-Kab…2.40:13.0:1
#000000
#474B52
Fail
h3 Erdung der PV-Anlage2.40:13.0:1
#000000
#474B52
Fail
h3 Montage von Kabelkan…2.40:13.0:1
#000000
#474B52
Fail
h3 Vogelschutz für Sol…2.40:13.0:1
#000000
#474B52
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+
Heading Text Quality
All 33 heading(s) have substantive, well-formed text
PASS
All 33 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
9 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
24 images 15 good alt text 9 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 12 controls labeled
PASS
All 12 controls labeled
Info::
12 control(s) properly labeled
12 controls
12 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#f-nametextName *for/id
#f-phonetelTelefon *for/id
#f-emailemailE-Mail *for/id
#f-serviceselectGewünschte Leistungfor/id
#f-messagetextareaKommentarfor/id
#f-consentcheckboxnone
#m-nametextName *for/id
#m-phonetelTelefon *for/id
#m-emailemailE-Mail *for/id
#m-serviceselectGewünschte Leistungfor/id
#m-messagetextareaKommentarfor/id
#m-consentcheckboxnone
A+
Form Input Types
12 form control(s) checked, no type mismatches
PASS
12 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
12 form control(s) checked, no input-semantic issues
PASS
12 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "de"
PASS
Lang attribute set to "de"
Info::
<html lang="de"> is set and valid
Got: de
A
Tabindex Anti-Patterns
0 positive, 2 -1-on-focusable
PASS
0 positive, 2 -1-on-focusable
Info::
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.)
Info::
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.)
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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
Lighthouse Accessibility Audits
Score 94/100 — 4 failing, 24 passed
PASS
94

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
WhatsApp Anfrage Senden div.td-formrow > div.td-formactions > a.primary-button > div.primary-button-text-block
© 2026 TD-SOLAR / DC Montage. Alle Rechte vorbehalten. div.td-foot > div.td-foot-row > div.td-foot-right > div.td-foot-copy
2026 div.td-foot-row > div.td-foot-right > div.td-foot-copy > span#year

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
Anfrage & Beratung div.td-proc-grid > article.td-proc-card > div.td-proc-body > h5.woking-process-name
Navigation div.footer-content > div.td-ftop > div.td-ftop-col > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.anim html.anim

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
TD-SOLAR DC MONTAGE div.navbar-container > div.navbar-content > div.navbar-left-content > a.td-brand
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.
Select elements have associated label elements.
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
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Touch targets have sufficient size and spacing.
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 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
`<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
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback