Skip to content
https://trimble.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
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: #ffffff
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
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
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Trimble Inc
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Trimble Inc ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Trimble Inc Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
Landmark Structure
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer
A
Heading Hierarchy
41 headings, 1 skip(s)
PASS
41 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Confidence at every turn™
  • H2 Accelerating the pace of work across the world's essential industries
  • H3 Government
  • H3 Natural Resources
  • H3 Construction
  • H3 Geospatial
  • H3 Transportation
  • H3 Government
  • H3 Natural Resources
  • H3 Construction
  • H3 Geospatial
  • H3 Transportation
  • H3 Government
  • H3 Natural Resources
  • H2 Trimble technology in action
  • H3 BUILDING THE WORLD
  • H3 SHAPING THE WORLD
  • H3 MOVING THE WORLD
  • H2 Ready. Set. Turn!
  • H2 Where technology and teamwork connect
  • H2 Our customers are powered by confidence that rises to the challenge
  • H3 The JE Dunn Way
  • H3 Bristol Motor Speedway
  • H3 jorge chAvez intl. airport
  • H3 evans distribution systems
  • H3 Randselva Bridge
  • H2 Turning ideas into improvements
  • H3 From silver screen to job site: OpenUSD is rewriting the rules of 3D collaboration
  • H3 A construction company under construction
  • H3 Hardworking AI for hardworking people
  • H2 The company we keep
  • H2 Looking for answers to product, order or billing questions?
  • H6 Attention skipped
  • H6 Cart Updated
  • H6 Attention
  • H6 Cart Updated
  • H6 Cart Updated
  • H6 Cart Updated
  • H6 Cart Updated
  • H6 Cart Updated
  • H6 Cart Updated

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

A
Alt Text Quality
All 31 images OK
PASS
All 31 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
28 image(s) with good alt text
31 images 28 good alt text
IssueCount
too long3 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(What can we help you find?)placeholder only

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

<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

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 Confidence at every …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Accelerating the pac…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trimble technology i…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Ready. Set. Turn!17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Where technology and…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Our customers are po…17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Turning ideas into …17.62:13.0:1
#000000
#EBEBEB
Pass
h2 The company we keep17.62:13.0:1
#000000
#EBEBEB
Pass
h2 Looking for answers …17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Government21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Natural Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Construction18.43:13.0:1
#000000
#F0F0F0
Pass
h3 Geospatial17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Transportation17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Government17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Natural Resources17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Construction17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Geospatial17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Transportation17.62:13.0:1
#000000
#EBEBEB
Pass
h3 Government17.62:13.0:1
#000000
#EBEBEB
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 90/100 — 3 failing, 20 passed
PASS
90

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > img body > img

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.

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
Privacy Notice div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●`[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.
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
●The page contains a heading, skip link, or landmark region
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<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
○Heading elements appear in a sequentially-descending order
○`<html>` element has a valid value for its `[lang]` attribute
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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