Skip to content
https://tuv.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 MAIN (missing!) CONTENTINFO footer

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

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
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
35 headings, 1 skip(s)
REVIEW
35 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 香港機電工程署(EMSD)委任電動車工場認證機構
  • H2 香港機電工程署(EMSD)委任電動車工場認證機構
  • H3 最新法規與標準
  • H3 展會與研討會
  • H3 線上證書查詢系統
  • H4 搜尋證書或產品
  • H2 服務特色
  • H3 功能安全性
  • H3 車輛檢驗
  • H3 車輛評估和中古車管理
  • H3 評估服務
  • H3 歐盟REACH法規
  • H3 中東驗證
  • H3 變壓器
  • H3 電線電纜
  • H3 焊接技術
  • H3 金屬材料測試和分析
  • H3 歐洲壓力容器法規：PED、TPED、SPVD、AD 2000
  • H3 防爆認證
  • H3 企業職業培訓
  • H3 TÜV Rheinland標準人員資格認可
  • H3 ISO 9001
  • H3 BSCI 審核
  • H3 ISO 14001
  • H3 FSC FM & COC
  • H2 (empty)
  • H3 ANSI/ESD S20.20靜電放電防護管理系統
  • H3 化學測試服務
  • H3 國際市場准入資訊更新
  • H3 UKCA認證 助您進入英國市場
  • H3 德國萊因TÜV 成功案例
  • H2 關於萊因
  • H4 德國萊因TÜV集團 skipped
  • H4 新聞室
  • H4 全球服務據點

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

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

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

B
Form Accessibility
7 of 7 controls have issues
REVIEW
7 of 7 controls have issues
Warning::
7 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text" name="search" id="search-terms-basic">; <input type="text">; <input type="text" name="search" id="search-terms-basic-mobile">; <input type="text" id="tuv-teaser-icon-input">; <input type="email" name="email_customer" id="email">; <input type="text">
7 controls
0 labeled
7 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Type location)placeholder only
#search-terms-basictext(搜索)placeholder only
inputtext(translation missing: core_search_location)placeholder only
#search-terms-basic-mobiletext(搜索)placeholder only
#tuv-teaser-icon-inputtext(輸入編號)placeholder only
#emailemail(輸入E-mail帳號)placeholder only
inputtext(Type location)placeholder only

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

<input type="text">; <input type="text" name="search" id="search-terms-basic">; <input type="text">; <input type="text" name="search" id="search-terms-basic-mobile">; <input type="text" id="tuv-teaser-icon-input">; <input type="email" name="email_customer" id="email">; <input type="text">

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title location_v2-no-padding ✓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 香港機電工程署(EMSD)委任電動…
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 香港機電工程署(EMSD)委任電動…
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 服務特色
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 關於萊因
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 最新法規與標準
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 展會與研討會
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 線上證書查詢系統
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 功能安全性
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 車輛檢驗
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 車輛評估和中古車管理
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 評估服務
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 歐盟REACH法規
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 中東驗證
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 變壓器
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 電線電纜
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 焊接技術
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 金屬材料測試和分析
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 歐洲壓力容器法規：PED、TPED、…
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 防爆認證
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 企業職業培訓
1.84:1
#000000
on
#393A3A
needs 3.0:1 (large text)
19px · bottom of viewport

2 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 香港機電工程…1.84:13.0:1
#000000
#393A3A
Fail
h2 香港機電工程…1.84:13.0:1
#000000
#393A3A
Fail
h2 服務特色1.84:13.0:1
#000000
#393A3A
Fail
h2 關於萊因1.84:13.0:1
#000000
#393A3A
Fail
h3 最新法規與標…1.84:13.0:1
#000000
#393A3A
Fail
h3 展會與研討會1.84:13.0:1
#000000
#393A3A
Fail
h3 線上證書查詢…1.84:13.0:1
#000000
#393A3A
Fail
h3 功能安全性1.84:13.0:1
#000000
#393A3A
Fail
h3 車輛檢驗1.84:13.0:1
#000000
#393A3A
Fail
h3 車輛評估和中…1.84:13.0:1
#000000
#393A3A
Fail
h3 評估服務1.84:13.0:1
#000000
#393A3A
Fail
h3 歐盟REACH法規1.84:13.0:1
#000000
#393A3A
Fail
h3 中東驗證1.84:13.0:1
#000000
#393A3A
Fail
h3 變壓器1.84:13.0:1
#000000
#393A3A
Fail
h3 電線電纜1.84:13.0:1
#000000
#393A3A
Fail
h3 焊接技術1.84:13.0:1
#000000
#393A3A
Fail
h3 金屬材料測試…1.84:13.0:1
#000000
#393A3A
Fail
h3 歐洲壓力容器…1.84:13.0:1
#000000
#393A3A
Fail
h3 防爆認證1.84:13.0:1
#000000
#393A3A
Fail
h3 企業職業培訓1.84:13.0:1
#000000
#393A3A
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.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 9 failing, 25 passed
REVIEW
70

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#main_content > div.tuv-slider > ul.slick-dots > li#slick-slide00 div#main_content > div.tuv-slider > ul.slick-dots > li#slick-slide00
div.break-in > div.tuv-teaser-container > ul.slick-dots > li#slick-slide10 div.break-in > div.tuv-teaser-container > ul.slick-dots > li#slick-slide10

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tuv-containers > div#main_content > div.tuv-slider > ul.slick-dots div.tuv-containers > div#main_content > div.tuv-slider > ul.slick-dots
div.break-out > div.break-in > div.tuv-teaser-container > ul.slick-dots div.break-out > div.break-in > div.tuv-teaser-container > ul.slick-dots

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#main_content > div.tuv-slider > ul.slick-dots > li#slick-slide00 div#main_content > div.tuv-slider > ul.slick-dots > li#slick-slide00
div.break-in > div.tuv-teaser-container > ul.slick-dots > li#slick-slide10 div.break-in > div.tuv-teaser-container > ul.slick-dots > li#slick-slide10

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
香港機電工程署(EMSD)委任電動車工場認證機構 div#main_content > div.tuv-slider > div.slick-list > div.slick-track
主題 ANSI/ESD S20.20靜電放電防護管理系統 ESD靜電防護認證服務致力於確保您的產品在任何情況下都能保持最佳性能。 主題 化學測試服務 提… div.break-in > div.tuv-teaser-container > div.slick-list > div.slick-track

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.newsletter-box > form > div.tuv-input-group > button.tuv-btn div.newsletter-box > form > div.tuv-input-group > button.tuv-btn

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.CybotCookiebotScrollContainer > div#CybotCookiebotDialogBodyContent > div#CybotCookiebotDialogBodyContentText > a div.CybotCookiebotScrollContainer > div#CybotCookiebotDialogBodyContent > div#CybotCookiebotDialogBodyContentText > a
div.header__inner > div.logo_wrapper > div.logo > a div.header__inner > div.logo_wrapper > div.logo > a
body#body > div.component > a.sticky-cta-wrapper body#body > div.component > a.sticky-cta-wrapper
div.social-box > ul > li.component > a.tuv-social-share__link div.social-box > ul > li.component > a.tuv-social-share__link
div.social-box > ul > li.component > a.tuv-social-share__link div.social-box > ul > li.component > a.tuv-social-share__link
div.social-box > ul > li.component > a.tuv-social-share__link div.social-box > ul > li.component > a.tuv-social-share__link
div.social-box > ul > li.component > a.tuv-social-share__link div.social-box > ul > li.component > a.tuv-social-share__link
div.social-box > ul > li.component > a.tuv-social-share__link div.social-box > ul > li.component > a.tuv-social-share__link
div.social-box > ul > li.component > a.tuv-social-share__link div.social-box > ul > li.component > a.tuv-social-share__link
div.footer-top > div.footer-inner > div.back-top-box > a.back-top-btn div.footer-top > div.footer-inner > div.back-top-box > a.back-top-btn

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
主題 a > div.tuv-teaser__content > div.tuv-text > span.tuv-text--meta__title

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
德國萊因TÜV集團 div.component > a > div.tuv-teaser__content > h4.heading--v2

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●ARIA toggle fields have accessible names
●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.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 `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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○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.
A+
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
11 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
29 images 18 good alt text 11 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback