Skip to content
https://hyundai.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-bgxakk
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Da el salto a la etiqueta Cero.
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Hyundai IONIQ 3
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 TUCSON Híbrido eléctrico
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Suscríbete al i20 con MOCEAN.
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Promociones destacadas
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Modelos destacados
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nuestro blog de ZonaEco
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ¿Con qué frecuencia necesitas recargar…
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 TUCSON Híbrido eléctrico
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 INSTER
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 i20
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 INSTER
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 i20
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 KONA
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Súbete a tus decisiones
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Da el salto a la etiqueta Cero.
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Nuevo IONIQ 6 N
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 KONA
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Suscríbete a tu Hyundai con MOCEAN.
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Gama SUV Híbrida y Eléctrica de Hyunda…
1.53:1
#000000
on
#002C5F
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Da el salto a la eti…1.53:13.0:1
#000000
#002C5F
Fail
h2 Hyundai IONIQ 31.53:13.0:1
#000000
#002C5F
Fail
h2 TUCSON Híbrido elé…1.53:13.0:1
#000000
#002C5F
Fail
h2 Suscríbete al i20 c…1.53:13.0:1
#000000
#002C5F
Fail
h2 Promociones destacad…1.53:13.0:1
#000000
#002C5F
Fail
h2 Modelos destacados1.53:13.0:1
#000000
#002C5F
Fail
h2 Nuestro blog de Zona…1.53:13.0:1
#000000
#002C5F
Fail
h2 ¿Con qué frecuenci…1.53:13.0:1
#000000
#002C5F
Fail
h3 TUCSON Híbrido elé…1.53:13.0:1
#000000
#002C5F
Fail
h3 INSTER1.53:13.0:1
#000000
#002C5F
Fail
h3 i201.53:13.0:1
#000000
#002C5F
Fail
h3 INSTER1.53:13.0:1
#000000
#002C5F
Fail
h3 i201.53:13.0:1
#000000
#002C5F
Fail
h3 KONA1.53:13.0:1
#000000
#002C5F
Fail
h3 Súbete a tus decisi…1.53:13.0:1
#000000
#002C5F
Fail
h3 Da el salto a la eti…1.53:13.0:1
#000000
#002C5F
Fail
h3 Nuevo IONIQ 6 N1.53:13.0:1
#000000
#002C5F
Fail
h3 KONA1.53:13.0:1
#000000
#002C5F
Fail
h3 Suscríbete a tu Hyu…1.53:13.0:1
#000000
#002C5F
Fail
h3 Gama SUV Híbrida y …1.53:13.0:1
#000000
#002C5F
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 7 failing, 28 passed
REVIEW
78

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.c-slider--stage > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
2 div.c-slider--stage > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
3 div.c-slider--stage > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
4 div.c-slider--stage > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
1 div.c-slider--default > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
2 div.c-slider--default > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
3 div.c-slider--default > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
1 div.c-slider--default > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
2 div.c-slider--default > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
3 div.c-slider--default > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
1 div.c-slider--teaser-list > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
2 div.c-slider--teaser-list > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item
3 div.c-slider--teaser-list > div.slider__pagination-wrapper > ol.slider__pagination-list > li.slider__pagination-list-item

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Compra Todos los modelos Promociones Ventajas para eléctricos Buscar concesiona… div.footer__linklist > div#footer-linklist > div.footer-linklist__accordion > div.c-accordion--footer

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.u-grid-col > div.c-video--default > div.video__container > div.video-controls div.u-grid-col > div.c-video--default > div.video__container > div.video-controls
div.u-grid-col > div.c-video--default > div.video__container > div.video-controls div.u-grid-col > div.c-video--default > div.video__container > div.video-controls

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hme-commute-calculator__controls-slider > div.hme-slider > div.hme-slider__rail > div.hme-slider__thumb div.hme-commute-calculator__controls-slider > div.hme-slider > div.hme-slider__rail > div.hme-slider__thumb

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.u-grid-col > div.c-video--default > div.video__container > progress.video-progress div.u-grid-col > div.c-video--default > div.video__container > progress.video-progress
div.u-grid-col > div.c-video--default > div.video__container > progress.video-progress div.u-grid-col > div.c-video--default > div.video__container > progress.video-progress

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.

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
120 km div.hme-commute-calculator__controls-slider > div.hme-slider > div.hme-slider__rail > h4.hme-slider__thumb-info

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.countries-input-container > div > input.links-search-input div > div.countries-input-container > div > input.links-search-input

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` 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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○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
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV 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

A
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 headings, 1 skip(s)
Info::
Single H1 present
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 Hyundai IONIQ 3
  • H2 TUCSON Híbrido eléctrico
  • H1 Da el salto a la etiqueta Cero.
  • H2 Suscríbete al i20 con MOCEAN.
  • H2 Promociones destacadas
  • H3 TUCSON Híbrido eléctrico
  • H3 INSTER
  • H3 i20
  • H2 Modelos destacados
  • H3 INSTER
  • H3 i20
  • H3 KONA
  • H3 Súbete a tus decisiones
  • H3 Da el salto a la etiqueta Cero.
  • H3 Nuevo IONIQ 6 N
  • H3 KONA
  • H3 Suscríbete a tu Hyundai con MOCEAN.
  • H3 Gama SUV Híbrida y Eléctrica de Hyundai
  • H3 Promociones Hyundai
  • H2 Nuestro blog de ZonaEco
  • H3 ¿Cuánto cuesta un coche eléctrico?
  • H3 Qué es y cómo funciona un coche eléctrico.
  • H3 ¿Qué es y cómo funciona un coche híbrido?
  • H2 ¿Con qué frecuencia necesitas recargar tu coche?
  • H4 120 km skipped

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
2 of 36 images have issues
PASS
2 of 36 images have issues
Warning::
1 image(s) with filename as alt text
Warning::
1 image(s) with generic alt text
Info::
13 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
36 images 21 good alt text 13 decorative 2 generic
IssueCount
filename1 image(s)
generic1 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputtext(none)none

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

<input type="text">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback