Skip to content
https://www.garmin.com

Accessibility

· 7 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
31
GRADE
F
FIX
5
REVIEW
2
PASS
0
INFO
0
Checks
7
2 REVIEW 5 FIX
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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.
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 Garmin | Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 79/100 — 7 failing, 24 passed
REVIEW
79

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Popup CTA body.bg-base > div#hs-web-interactives-bottom-anchor > div#hs-overlay-cta-195465621689

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linha de sessão div.render-provider > div.vtex-store__template > div.flex > div.vtex-flex-layout-0-x-flexRow

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.vtex-login-2-x-container > div.relative > div.vtex-login-2-x-buttonLink > button.vtex-button div.vtex-login-2-x-container > div.relative > div.vtex-login-2-x-buttonLink > button.vtex-button
div.absolute > div.vtex-search-2-x-biggy-autocomplete-wrapper > section.vtex-search-2-x-biggy-autocomplete > button.vtex-search-2-x-close-btn div.absolute > div.vtex-search-2-x-biggy-autocomplete-wrapper > section.vtex-search-2-x-biggy-autocomplete > button.vtex-search-2-x-close-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.vtex-slider-layout-0-x-sliderTrack > div.vtex-slider-layout-0-x-slide > div.vtex-slider-layout-0-x-slideChildrenContainer > a.vtex-slider-layout-0-x-imageElementLink div.vtex-slider-layout-0-x-sliderTrack > div.vtex-slider-layout-0-x-slide > div.vtex-slider-layout-0-x-slideChildrenContainer > a.vtex-slider-layout-0-x-imageElementLink

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
COMPRAR button.vtex-button > div.vtex-button__label > div.vtex-add-to-cart-button-0-x-buttonDataContainer > span.vtex-add-to-cart-button-0-x-buttonText

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Dot 1 of 5 div.pr0-ns > section#slider-items-lfco4u2 > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 2 of 5 div.pr0-ns > section#slider-items-lfco4u2 > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 3 of 5 div.pr0-ns > section#slider-items-lfco4u2 > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 4 of 5 div.pr0-ns > section#slider-items-lfco4u2 > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 5 of 5 div.pr0-ns > section#slider-items-lfco4u2 > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 1 of 4 div.pr0-ns > section#slider-items-f6s50su > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 2 of 4 div.pr0-ns > section#slider-items-f6s50su > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 3 of 4 div.pr0-ns > section#slider-items-f6s50su > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot
Dot 4 of 4 div.pr0-ns > section#slider-items-f6s50su > div.vtex-slider-layout-0-x-paginationDotsContainer > div.vtex-slider-layout-0-x-paginationDot

These items highlight common accessibility best practices.

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
COMPRE EM 8X S/ JUROS OU EM ATÉ 18X NO CARTÃO div.vtex-slider-layout-0-x-sliderTrack > div.vtex-slider-layout-0-x-slide > div.vtex-slider-layout-0-x-slideChildrenContainer > div.vtex-modal-layout-0-x-triggerContainer
Forerunner Relógio Garmin Forerunner 55 com Monitor Cardíaco de Pulso e GPS R$ … div.vtex-slider-layout-0-x-slide > div.vtex-slider-layout-0-x-slideChildrenContainer > section.vtex-product-summary-2-x-container > a.vtex-product-summary-2-x-clearLink
○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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
○`[accesskey]` values are unique
○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
○`<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.
○`[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