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 1 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

404 Error Page

Action

HTTP 500, bare page

FIX

HTTP 500, bare page

Unexpected status code: HTTP 500

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

Got: HTTP 500

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 500 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

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

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 ✗

Lighthouse Accessibility Audits

Score 85/100 — 4 failing, 28 passed

REVIEW

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

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
Search `ul.nav > li > div#search-trigger-settings > a.search-trigger`

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.

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
OUR BRANDS `div.container-fluid > div.row > article.col-xs-12 > h4`
ABOUT US `div.container-fluid > div.row > article.col-xs-12 > h4`
MORE TO EXPLORE `div.container-fluid > div.row > article.col-xs-12 > h4`
RACING `div.container-fluid > div.row > article.col-xs-12 > h4`
RECALLS `div.container-fluid > div.row > article.col-xs-12 > h4`
SERVICES `div.container-fluid > div.row > article.col-xs-12 > h4`
Privacy Notice `div.row > div.col-md-10 > p.terms > a#footer-privacy-policy`
Vehicle Data Privacy `div.row > div.col-md-10 > p.terms > a.footer-settings`
Legal Terms and Conditions `div.row > div.col-md-10 > p.terms > a.footer-settings`
SMS Terms and Conditions `div.row > div.col-md-10 > p.terms > a.footer-settings`
Your Privacy Choices `div.row > div.col-md-10 > p.terms > a#footer-do-no-sell`
Prop 65 Info `div.row > div.col-md-10 > p.terms > a.footer-settings`
HOW TO DISCONNECT REMOTE VEHICLE ACCESS `div.row > div.col-md-10 > p.terms > a.footer-settings`
Cookies section `div.col-md-10 > p > a > strong`
click here. `div.col-md-10 > p > strong > a.ot-sdk-show-settings`
Site Map `div.row > ul.final-links > li > a.footer-settings`
Honda Licensing `div.row > ul.final-links > li > a.footer-settings`
Contact Us `div.row > ul.final-links > li > a.footer-settings`
Privacy Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`
California Privacy Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`
Terms and Conditions `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`
Manage Preferences `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler`

These are opportunities to improve the legibility of your content.

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
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > img`
a.wrapper-link > div.col-xs-4 > div.text > img `a.wrapper-link > div.col-xs-4 > div.text > 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.

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
Go to slide 1 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div.wrapper > section#home-hero-swiper > div.swiper-pagination > span.swiper-pagination-bullet`

These items highlight common accessibility best practices.

○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

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

○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

○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

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Access Denied

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

A+

Color Contrast (Screenshot)

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

5 pass

Show all checked elements (5)

Element	Ratio	Required	FG	BG	Result
h1 Access Denied	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Access Denied	21.00:1	4.5:1	#000000	#FFFFFF	Pass
body You don't have permi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Reference #18.d46b10…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p https://errors.edges…	20.65:1	4.5:1	#000000	#FDFDFD	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.

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