Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

Link & Button Quality

Action

25 issue(s) across 113 links and 2 buttons

FIX

25 issue(s) across 113 links and 2 buttons

21 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /customers/microsoft-azure-maps/; /customers/; /customers/groupe-psa/; /customers/ptv-group/; /customers/jeep-avenger/; /customers/advanced-driver-assistance-tech-for-nissan-qashqai/; /customers/cariad-and-tomtom-redefining-driving-experience/; /customers/microsoft-azure-maps/; /customers/; /customers/groupe-psa/ (+11 more)

4 link(s) with generic text

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

Got: https://www.tomtom.com/newsroom/press-releases/general/29451/tomtom-announces… ("Read more"); https://www.tomtom.com/newsroom/press-releases/general/29456/tomtom-co-founde… ("Read more"); /newsroom/explainers-and-insights/tomtom-automated-driving-needs-a-map-cariad… ("Read more"); /newsroom/explainers-and-insights/tomtom-traffic-index-2026-headline-numbers/ ("Read more")

5 link(s) open in new tab without warning

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

Got: https://www.facebook.com/TomTom; https://twitter.com/tomtom; https://www.youtube.com/user/TomTomOfficial; https://www.linkedin.com/company/tomtom; https://www.instagram.com/tomtomglobal

83 link(s) with descriptive text

113 links

21 empty

4 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/customers/microsoft-azure-maps/	(empty)	empty	Add link text or aria-label
/customers/	(empty)	empty	Add link text or aria-label
/customers/groupe-psa/	(empty)	empty	Add link text or aria-label
/customers/ptv-group/	(empty)	empty	Add link text or aria-label
/customers/jeep-avenger/	(empty)	empty	Add link text or aria-label
/customers/advanced-driver-assistance-te…	(empty)	empty	Add link text or aria-label
/customers/cariad-and-tomtom-redefining-…	(empty)	empty	Add link text or aria-label
/customers/microsoft-azure-maps/	(empty)	empty	Add link text or aria-label
/customers/	(empty)	empty	Add link text or aria-label
/customers/groupe-psa/	(empty)	empty	Add link text or aria-label
/customers/ptv-group/	(empty)	empty	Add link text or aria-label
/customers/jeep-avenger/	(empty)	empty	Add link text or aria-label
/customers/advanced-driver-assistance-te…	(empty)	empty	Add link text or aria-label
/customers/cariad-and-tomtom-redefining-…	(empty)	empty	Add link text or aria-label
/customers/microsoft-azure-maps/	(empty)	empty	Add link text or aria-label
/customers/	(empty)	empty	Add link text or aria-label
/customers/groupe-psa/	(empty)	empty	Add link text or aria-label
/customers/ptv-group/	(empty)	empty	Add link text or aria-label
/customers/jeep-avenger/	(empty)	empty	Add link text or aria-label
/customers/advanced-driver-assistance-te…	(empty)	empty	Add link text or aria-label
/customers/cariad-and-tomtom-redefining-…	(empty)	empty	Add link text or aria-label
https://www.tomtom.com/newsroom/press-re…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Tomtom Announces Leadership Transition Co Founder Harold Goddijn And Alain De Taeye To Step Down Long Serving Chief Revenue Officer Mike Schoofs Nominated As Chief Executive Officer
https://www.tomtom.com/newsroom/press-re…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Tomtom Co Founder And Cmo Corinne Vigreux Steps Down After 35 Years Of Leadership
/newsroom/explainers-and-insights/tomtom…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Tomtom Automated Driving Needs A Map Cariad Is Proof
/newsroom/explainers-and-insights/tomtom…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Tomtom Traffic Index 2026 Headline Numbers
https://www.facebook.com/TomTom	Visit our facebook page	new tab	Add '(opens in new tab)' to text
https://twitter.com/tomtom	Visit our twitter page	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/TomTomOffic…	Visit our youtube page	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/tomtom	Visit our linkedin page	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/tomtomglobal	Visit our instagram page	new tab	Add '(opens in new tab)' to text

85 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/customers/microsoft-azure-maps/; /customers/; /customers/groupe-psa/; /customers/ptv-group/; /customers/jeep-avenger/; /customers/advanced-driver-assistance-tech-for-nissan-qashqai/; /customers/cariad-and-tomtom-redefining-driving-experience/; /customers/microsoft-azure-maps/; /customers/; /customers/groupe-psa/ (+11 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.tomtom.com/newsroom/press-releases/general/29451/tomtom-announces… ("Read more"); https://www.tomtom.com/newsroom/press-releases/general/29456/tomtom-co-founde… ("Read more"); /newsroom/explainers-and-insights/tomtom-automated-driving-needs-a-map-cariad… ("Read more"); /newsroom/explainers-and-insights/tomtom-traffic-index-2026-headline-numbers/ ("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://www.facebook.com/TomTom; https://twitter.com/tomtom; https://www.youtube.com/user/TomTomOfficial; https://www.linkedin.com/company/tomtom; https://www.instagram.com/tomtomglobal

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

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

1 navigation landmark(s) detected

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

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.

Alt Text Quality

1 of 60 images have issues

REVIEW

1 of 60 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image(s) with alt text over 125 characters

54 image(s) with good alt text

60 images 54 good alt text 1 missing

Issue	Count
missing	1 image(s)
too long	5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

25 headings

PASS

25 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 For businesses and developers
H3 For businesses and developers
H3 For drivers
H3 For drivers
H1 Maps and location technology to keep the world moving
H2 Why TomTom
H3 Collaboration comes first
H3 We put you in charge
H3 We move with the world
H3 We’re built for business
H2 Explore products
H3 Orbis Maps for Automated Driving
H3 Navigation SDK for mobile
H3 Traffic
H2 Explore solutions
H3 Public Sector
H3 Automated Driving
H3 Fleet Management and Logistics
H1 (empty)
H2 Next steps?
H2 Latest news and more
H3 TomTom announces leadership transition: Co-Founder Harold Goddijn and Alain De Taeye to step down; Long-serving Chief Revenue Officer Mike Schoofs nominated as Chief Executive Officer
H3 TomTom Co-founder and CMO Corinne Vigreux steps down after 35 years of leadership
H3 Map-powered automated driving is winning the industry over
H3 The global traffic challenge in numbers: What the TomTom Traffic Index data tells us

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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)

Element	Ratio	Required	FG	BG	Result
h3 For businesses and d…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 For businesses and d…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 For drivers	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 For drivers	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Orbis Maps for Autom…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Navigation SDK for m…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Traffic	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Public Sector	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Automated Driving	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h3 Fleet Management and…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
title TomTom — Maps and …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
summary Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Business	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Solutions, APIs and …	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Consumer	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Apps and sat navs wi…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Documentation	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Find API and SDK doc…	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Careers	18.76:1	4.5:1	#000000	#F2F2F2	Pass
div Check out our vacanc…	18.76:1	4.5:1	#000000	#F2F2F2	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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 passed

PASS

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
Read more `div.article-group-list > span.article-item > a.cta > span.cta__wrapped-label`
Read more `div.article-group-list > span.article-item > a.cta > span.cta__wrapped-label`
Read more `div.article-group-list > span.article-item > a.cta > span.cta__wrapped-label`
Read more `div.article-group-list > span.article-item > a.cta > span.cta__wrapped-label`

These are opportunities to improve the legibility of your content.

Names and labels

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.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`
div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link `div.reel-items > div.reel-items__visual > div.reel-visual > a.reel-visual__hidden-link`

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.

○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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

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

●Heading elements appear in a sequentially-descending order

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

●Identical links have the same purpose.

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

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

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

○Uses ARIA roles only on compatible elements

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