Skip to content
https://teamviewer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
6 landmarks
REVIEW
6 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 "Wereldwijde navigatie" 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
65 headings, 2 skip(s)
REVIEW
65 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
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.
  • H2 Persoonlijk gebruik en SMB TeamViewer Remote
  • H2 Enterprise TeamViewer Tensor
  • H2 Realtime probleemoplossing TeamViewer DEX
  • H2 Verbonden werknemer TeamViewer Frontline
  • H2 Bespaar tot 25% op TeamViewer
  • H2 Belangrijke integraties
  • H2 TeamViewer ONE-platform
  • H2 Kernmogelijkheden
  • H2 Gartner Report 2025
  • H3 TeamViewer uitgeroepen tot leider in DEX
  • H2 Belangrijke integraties
  • H2 Populaire gebruiksscenario’s
  • H2 Andere gebruiksscenario’s
  • H2 Op behoefte Populaire oplossingen voor verschillende teams
  • H2 Per branches Populaire oplossingen gesorteerd per branche
  • H2 Praat met ons verkoopteam
  • H2 Meer informatie over TeamViewer
  • H2 Bronnen
  • H2 Partner
  • H2 Ondersteuning
  • H2 Bedrijf
  • H1 Bespaar tot 25% op TeamViewer
  • H3 TeamViewer ONE skipped
  • H3 IT-ondersteuning
  • H3 DEX en AEM
  • H3 Controle op afstand
  • H3 Frontline-werkstromen
  • H2 Het toppunt van proactieve IT
  • H3 Real-time zichtbaarheid
  • H3 Nuttige inzichten
  • H3 Geautomatiseerd herstel
  • H2 Brancheleiders winnen met TeamViewer
  • H3 Howe Tech scales IT services with TeamViewer’s remote monitoring and security solutions.
  • H3 Liu Jo is disrupting the retail industry with TeamViewer’s augmented reality solutions.
  • H3 Brack.Alltron uses TeamViewer’s Pick-by-Vision solution: 30% higher efficiency and fewer errors.
  • H3 Geïntegreerd in uw systemen
  • H2 Ontdek wat TeamViewer onderscheidt
  • H3 TeamViewer Germany GmbH
  • H3 BitSight Security Rating zet TeamViewer als top 1 % in de ranglijst van de tech-industrie
  • H2 Beter samen
  • H3 Apparaatbeheer
  • H3 Beheer mobiele apparaten
  • H3 Apparaatbewaking
  • H3 Eindpuntbeveiliging
  • H4 TeamViewer voor non-profitorganisaties en onderwijs
  • H3 Ondersteuning op afstand voor apparaten met groot bereik
  • H3 Ondersteund leren—altijd, overal
  • H3 Een digitale werkplek die tijd en geld bespaart
  • H2 Laten we de juiste oplossing voor uw bedrijf vinden
  • H2 Selecteer uw regio
  • H3 AANBEVOLEN REGIO
  • H3 Americas
  • H3 Asia Pacific
  • H3 Commonwealth of Independent States
  • H3 Europe
  • H3 Middle East Africa
  • H2 Consent Banner
  • H4 Imprint skipped
  • H2 Privacy-voorkeurscentrum
  • H3 Cookievoorkeuren beheren
  • H4 Strikt noodzakelijke cookies
  • H4 Prestatiecookies
  • H4 Functionele cookies
  • H4 Marketing en gerichte cookies
  • H3 Cookielijst

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

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 404 Pagina niet gevonden | TeamViewer ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
A+
Alt Text Quality
All 127 images OK
PASS
All 127 images OK
Info::
85 decorative image(s) correctly marked
Info::
42 image(s) with good alt text
127 images 42 good alt text 85 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ot-group-id-2checkboxPrestatiecookiesfor/id
#ot-group-id-3checkboxFunctionele cookiesfor/id
#ot-group-id-4checkboxMarketing en gerichte cookiesfor/id
#vendor-search-handlertextZoeken in cookielijstenaria-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Bespaar tot 25% op T…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bespaar tot 25% op T…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Praat met ons verkoo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meer informatie over…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Het toppunt van proa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Brancheleiders winne…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ontdek wat TeamViewe…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Beter samen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Laten we de juiste o…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Selecteer uw regio21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Consent Banner21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy-voorkeurscen…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TeamViewer uitgeroep…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 IT-ondersteuning21.00:13.0:1
#000000
#FFFFFF
Pass
h3 DEX en AEM21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Controle op afstand21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Frontline-werkstrome…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Real-time zichtbaarh…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nuttige inzichten21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Geautomatiseerd hers…21.00:13.0:1
#000000
#FFFFFF
Pass

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
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 28 passed
PASS
91

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

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
Toonaangevende veiligheid div.cmp-tabcomponent > div#tabcomponent-17ee0ba6b5 > ol.cmp-tabs__tablist > li#security

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.

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
Learn about Bitsight Security Rating article.sc-bjEuFB > div.sc-idysxy > p.sc-hLcnCW > a.sc-gKHVrV

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
TeamViewer ONE div.cards > div.cmp-cards > div.cmp-cards__list-highlight > h3.cmp-cards__list-headline

These are opportunities to improve keyboard navigation in your application.

○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 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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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
○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.
○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.
○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.

Send Feedback