Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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

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

22 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 22 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

25 landmarks

REVIEW

25 landmarks

<main> landmark present

22 <nav> landmark(s) found

20 of 22 <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

Alt Text Quality

2 of 45 images have issues

REVIEW

2 of 45 images have issues

2 image(s) with generic alt text

5 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

37 image(s) with good alt text

45 images 37 good alt text 1 decorative 2 generic

Issue	Count
generic	2 image(s)
too long	5 image(s)

Link & Button Quality

Action

7 issue(s) across 219 links and 55 buttons

REVIEW

7 issue(s) across 219 links and 55 buttons

6 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /en-int/newsroom/press-releases/air-flow-ptc-air-heaters.html ("Read more"); /en-int/newsroom/press-releases/125-years-anniversary.html ("Read more"); /en-int/newsroom/press-releases/cool-top-120-e.html ("Read more"); /en-int/newsroom/press-releases/plant-india.html ("Read more"); /en-int/newsroom/press-releases/social-days-2025.html ("Read more"); /en-int/newsroom/press-releases/webasto-and-maccor-collaborate.html ("Read more")

8 link(s) open in new tab without warning

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

Got: https://my.webasto.net/en/sa/dealerlocator; https://my.webasto.net/; https://my.webasto.net/en/sa/dealerlocator; https://my.webasto.net/en/sa/dealerlocator; https://www.linkedin.com/company/webasto; https://www.facebook.com/WebastoGroup/; https://www.instagram.com/webasto_group/; https://www.youtube.com/channel/UCWfjnuz1Kp1VnOrWVMWFNzw

1 button(s) with no accessible text

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

Got: button.cmp-header__primary-link (#864 on page)

205 link(s) with descriptive text

219 links

0 empty

6 generic text

8 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://my.webasto.net/en/sa/dealerlocat…	Dealer Locator	new tab	Add '(opens in new tab)' to text
https://my.webasto.net/	Dealer Portal	new tab	Add '(opens in new tab)' to text
https://my.webasto.net/en/sa/dealerlocat…	Request your offer	new tab	Add '(opens in new tab)' to text
/en-int/newsroom/press-releases/air-flow…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Air Flow Ptc Air Heaters.Html
/en-int/newsroom/press-releases/125-year…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: 125 Years Anniversary.Html
/en-int/newsroom/press-releases/cool-top…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Cool Top 120 E.Html
/en-int/newsroom/press-releases/plant-in…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Plant India.Html
/en-int/newsroom/press-releases/social-d…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Social Days 2025.Html
/en-int/newsroom/press-releases/webasto-…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Webasto And Maccor Collaborate.Html
https://my.webasto.net/en/sa/dealerlocat…	Dealer Locator	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/webasto	Linkedin	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/WebastoGroup/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/webasto_group/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCWfjnuz…	Youtube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

259 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/en-int/newsroom/press-releases/air-flow-ptc-air-heaters.html ("Read more"); /en-int/newsroom/press-releases/125-years-anniversary.html ("Read more"); /en-int/newsroom/press-releases/cool-top-120-e.html ("Read more"); /en-int/newsroom/press-releases/plant-india.html ("Read more"); /en-int/newsroom/press-releases/social-days-2025.html ("Read more"); /en-int/newsroom/press-releases/webasto-and-maccor-collaborate.html ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://my.webasto.net/en/sa/dealerlocator; https://my.webasto.net/; https://my.webasto.net/en/sa/dealerlocator; https://my.webasto.net/en/sa/dealerlocator; https://www.linkedin.com/company/webasto; https://www.facebook.com/WebastoGroup/; https://www.instagram.com/webasto_group/; https://www.youtube.com/channel/UCWfjnuz1Kp1VnOrWVMWFNzw

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.cmp-header__primary-link (#864 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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="cmp-languagenavigation__selector--tab0">

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="cmp-languagenavigation__selector--tab1">

tabindex="-1" on naturally-focusable <button id="cmp-languagenavigation__selector--tab2">

tabindex="-1" on naturally-focusable <button id="cmp-languagenavigation__selector--tab3">

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 Webasto 404 Page Not Found – Return to Home and Explore Site ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 Webasto establishes third production sit…

1.96:1

#000000

#4F392E

needs 3.0:1 (large text)

24px · above the fold · over background image/gradient

h2 Webasto secures financing

2.57:1

#000000

#65493C

needs 3.0:1 (large text)

24px · above the fold

h2 Choose by vehicle solution

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready for camping season?

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sustainable innovation at Auto Shanghai …

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sustainable roof concept

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Stay ahead with our B2B newsletter

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Newsroom

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Quick Links

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Strategy

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Corporate culture

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How we work

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Roof, thermo and battery solutions for…

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Products & Solutions by Webasto

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Innovative roof systems

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Electrifying battery solutions

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Comfortable warmth

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Customized cooling

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Find your product

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Product finder

2.49:1

#000000

#004AA1

needs 3.0:1 (large text)

24px · bottom of viewport

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)

Element	Ratio	Required	FG	BG	Result
h2 Webasto establishes …	1.96:1	3.0:1	#000000	#4F392E	Fail
h2 Webasto secures fina…	2.57:1	3.0:1	#000000	#65493C	Fail
h2 Choose by vehicle so…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Ready for camping se…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Sustainable innovati…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Sustainable roof con…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Stay ahead with our …	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Newsroom	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Quick Links	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Strategy	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Corporate culture	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 How we work	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Roof, thermo and b…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Products & Solutions…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Innovative roof syst…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Electrifying battery…	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Comfortable warmth	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Customized cooling	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Find your product	2.49:1	3.0:1	#000000	#004AA1	Fail
h2 Product finder	2.49:1	3.0:1	#000000	#004AA1	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 Hierarchy

37 headings

PASS

37 headings

Single H1 present

H2 Webasto establishes third production site in India
H2 Webasto secures financing
H2 Choose by vehicle solution
H2 Ready for camping season?
H2 Sustainable innovation at Auto Shanghai 2025
H2 Sustainable roof concept
H2 Stay ahead with our B2B newsletter
H2 Newsroom
H2 Quick Links
H2 Strategy
H2 Corporate culture
H2 How we work
H1 Where Innovation drives mobility — since 1901
H2 Roof, thermo and battery solutions for vehicles worldwide
H2 Products & Solutions by Webasto
H2 Innovative roof systems
H2 Electrifying battery solutions
H2 Comfortable warmth
H2 Customized cooling
H2 Find your product
H2 Product finder
H2 Find your suitable product
H2 Car makers
H2 Innovate mobility
H2 End customers
H2 Find your dealer
H2 Latest news & press releases
H2 Air Flow: modular PTC air heaters
H2 125 years of Webasto
H2 Cool Top 120-e
H2 Webasto establishes third production site in India
H2 Webasto Foundation: Driving social commitment worldwide
H2 Webasto and Maccor collaborate for EV Battery & PTS
H2 Find your suitable product
H2 Products
H2 Solutions
H2 About Us

A+

Heading Text Quality

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

PASS

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

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" name="searchTerm">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
searchTerm	text	(We love the search for answers. Type in your search term here.)	placeholder only

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "searchTerm" should use type="search" (currently type="text")

Field name "searchTerm" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

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+

Mobile-Readable Font Sizes

No visible text nodes measured on the page

PASS

No visible text nodes measured on the page

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 100/100 — 0 failing, 29 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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○Form elements have associated labels

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

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

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