Skip to content
https://harley-davidson.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
Info::
No banner (header) landmark
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 (missing!) NAV "Main Navigation" 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

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

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.
C
Heading Hierarchy
Action
25 headings, 2 skip(s)
REVIEW
25 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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.
  • H1 POR ESTO VAMOS EN MOTO.
  • H2 OSCURA O BRILLANTE. IGUAL DE RADICAL
  • H3 NIGHTSTER™ 2026 — NUEVA DECORACIÓN INSPIRADA EN LA XR750
  • H2 LIGHTNING BOTTLED IN BLOOD ORANGE.
  • H2 ROAD GLIDE™ 2026
  • H1 NUNCA HABÍA HABIDO UN LUGAR TAN BONITO. duplicate H1
  • H3 NUEVA STREET GLIDE™ 3 LIMITED 2026 skipped
  • H2 CABALLETE LATERAL NO INCLUIDO.
  • H4 CVO™ Street Glide™ Limited skipped
  • H4 CVO™ Street Glide™
  • H4 Street Glide™
  • H4 Road Glide™
  • H4 Street Glide™ Limited
  • H4 Road Glide™ Limited
  • H4 CVO™ Street Glide™ ST
  • H4 CVO™ Road Glide™ ST
  • H2 Herramientas de compra
  • H2 TU MOTO. TUS REGLAS.
  • H3 Comprar por categorías
  • H2 Aprende a montar
  • H2 Atención al cliente
  • H2 Financiación
  • H2 Mantenimiento de Motocicletas
  • H2 Seguros
  • H2 Acerca de nuestra empresa

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

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: This page could not be found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
14 icon(s) detected
REVIEW
14 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only
title Tienda Online Oficial Harley-Davidson | …
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button España - Español
2.05:1
#000000
on
#41413C
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 POR ESTO VAMOS EN MO…17.83:13.0:1
#000000
#EEECEB
Pass
h1 NUNCA HABÍA HABIDO …17.83:13.0:1
#000000
#EEECEB
Pass
h2 OSCURA O BRILLANTE. …17.83:13.0:1
#000000
#EEECEB
Pass
h2 LIGHTNING BOTTLED IN…17.83:13.0:1
#000000
#EEECEB
Pass
h2 ROAD GLIDE17.83:13.0:1
#000000
#EEECEB
Pass
h2 202617.83:13.0:1
#000000
#EEECEB
Pass
h2 CABALLETE LATERAL NO…17.83:13.0:1
#000000
#EEECEB
Pass
h2 Herramientas de comp…17.83:13.0:1
#000000
#EEECEB
Pass
h2 TU MOTO. TUS REGLAS.17.83:13.0:1
#000000
#EEECEB
Pass
h3 NIGHTSTER17.83:13.0:1
#000000
#EEECEB
Pass
h3 2026 — NUEVA DECOR…17.83:13.0:1
#000000
#EEECEB
Pass
h3 NUEVA STREET GLIDE17.83:13.0:1
#000000
#EEECEB
Pass
h3 3 LIMITED 202617.83:13.0:1
#000000
#EEECEB
Pass
h3 Comprar por categor…17.83:13.0:1
#000000
#EEECEB
Pass
title Tienda Online Oficia…1.00:14.5:1
#000000
#000000
Fail
a Aprende a montar21.00:14.5:1
#000000
#FFFFFF
Pass
a Prueba de conducció…21.00:14.5:1
#000000
#FFFFFF
Pass
a Localizador6.97:14.5:1
#000000
#FA6600
Pass
button Seguimiento del Pedi…6.97:14.5:1
#000000
#FA6600
Pass
button España - Español2.05:14.5:1
#000000
#41413C
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 22 passed
REVIEW
83

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
CUSTOMIZE div.osano-cm-window > div#4127191b-01e6-464e-9d01-2041f147f49c > div.osano-cm-dialog__buttons > button.osano-cm-manage
ACCEPT ALL div.osano-cm-window > div#4127191b-01e6-464e-9d01-2041f147f49c > div.osano-cm-dialog__buttons > button.osano-cm-accept-all
REJECT NON-ESSENTIAL div.osano-cm-window > div#4127191b-01e6-464e-9d01-2041f147f49c > div.osano-cm-dialog__buttons > button.osano-cm-denyAll
Envío gratis a partir de 50€ y devoluciones gratis - div.swiper-wrapper > div.swiper-slide > p > b
Comprar Ahora div.swiper-slide > p > a.banner-entry-hyperlink > b
ÚLTIMA NOVEDAD div.swiper-slide > article.ig-flex > div.ig-flex > strong.ig-text-[0.875rem]
ÚLTIMA NOVEDAD div.swiper-slide > article.ig-flex > div.ig-flex > strong.ig-text-[0.875rem]
Buscar un concesionario div.ig-h-[64px] > a > button.ig-flex > span
REGÍSTRATE POR CORREO ELECTRÓNICO div.newsletter-signup-body > button.ig-group > div.ig-flex > span.ig-transition-all

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
NUEVA STREET GLIDE™ 3 LIMITED 2026 div.swiper-slide > div.ig-absolute > div.ig-space-y-2 > h3.ig-text-[1.5rem]
CVO™ STREET GLIDE™ LIMITED div.swiper-slide > article.BikeCard > a.!ig-no-underline > h4.ig-text-[0.875rem]

These are opportunities to improve keyboard navigation in your application.

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

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mapa del sitio web Aviso legalTérminos y condiciones de ventaPolítica de privac… footer.footer > div.footer-container > div.section-container > ul.mobile-legal-links

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Teal Thunder/Vivid Black div.swiper-wrapper > div.swiper-slide > div.ig-flex > button.ig-w-5
chevron-icon-right div.swiper-slide > article.BikeCard > div#colorSwatchGroup > button.disabled:ig-opacity-50

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
España - Español div.bottom-section-container > div.bottom-section-sub-container > div.gc-relative > button.gc-flex
○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.
●`[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.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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>`.
○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.
A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
2 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
19 images 17 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback