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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
B
Heading Hierarchy
20 headings
REVIEW
20 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 2026 C-HR
  • H2 2026 Sienna
  • H2 2026 RAV4 Plug-in Hybrid
  • H2 2026 Toyota Crown Signia
  • H2 2026 bZ Woodland
  • H2 2026 C-HR
  • H2 2026 Sienna
  • H3 pick up where you left off
  • H3 pick up where you left off
  • H2 Explore All Vehicles
  • H2 Shopping Tools
  • H3 A lineup generating more possibilites.
  • H4 People are the destination.
  • H2 Discover Toyota
  • H2 SHOPPING TOOLS
  • H2 VEHICLES
  • H2 HELPFUL LINKS
  • H2 OWNERS
  • H2 ABOUT TOYOTA
  • H3 External Site Modal

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

19 pass 1 fail WCAG AA 1 pass AA only
h2 2026 RAV4 Plug-in Hybrid
2.80:1
#000000
on
#59544E
needs 3.0:1 (large text)
24px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 2026 C-HR12.36:13.0:1
#000000
#C9C6C4
Pass
h2 2026 Sienna3.55:13.0:1
#000000
#67645B
Pass
h2 2026 RAV4 Plug-in Hy…2.80:13.0:1
#000000
#59544E
Fail
h2 2026 Toyota Crown Si…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2026 bZ Woodland21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2026 C-HR21.00:13.0:1
#000000
#FFFFFF
Pass
h2 2026 Sienna21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore All Vehicles21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shopping Tools21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover Toyota21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SHOPPING TOOLS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 VEHICLES21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HELPFUL LINKS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 OWNERS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ABOUT TOYOTA21.00:13.0:1
#000000
#FFFFFF
Pass
h3 pick up where you le…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 pick up where you le…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A lineup generating …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 External Site Modal21.00:13.0:1
#000000
#FFFFFF
Pass
title New Cars, Trucks, SU…21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 28 passed
REVIEW
87

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.

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.marquee-slide-wrapper > a.assets-wrapper > div.action-control-wrapper > button.video-control div.marquee-slide-wrapper > a.assets-wrapper > div.action-control-wrapper > button.video-control
li.cmp-carousel__item > div.small-image-feature-slide > div.wrapper > button.play-cta li.cmp-carousel__item > div.small-image-feature-slide > div.wrapper > button.play-cta

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
nav.container > ul.cta-container > li > a.mobile-logo nav.container > ul.cta-container > li > a.mobile-logo
Learn More div.marquee-slide-v2 > div.marquee-slide-wrapper > div.cta-wrapper > a.secondary
Explore div.wrapper > div.slide-panel > div.slide-ctas > a.slide-cta
Build div.wrapper > div.slide-panel > div.slide-ctas > a.slide-cta
RAV4 Model image div.vehicle-selector-slide > div.wrapper > div.slide-panel > a.slide-img-link
Explore div.wrapper > div.slide-panel > div.slide-ctas > a.slide-cta
Build div.wrapper > div.slide-panel > div.slide-ctas > a.slide-cta
Explore All Vehicles div.vehicle-selector-container > div.wrapper > div.cta > a.slide-cta
Search Inventory div.vehicle-selector-container > div.wrapper > div.cta > a.slide-cta
Explore Electrified Vehicles div.hero-container > div.hero-content > div.copy-wrap > a.button
Schedule Now div.content-container > div.content-wrapper > div.cta-wrapper > a.button
Shop Now div.content-container > div.content-wrapper > div.cta-wrapper > a.button
Learn More div.content-container > div.content-wrapper > div.cta-wrapper > a.dark
Learn More div.content-container > div.content-wrapper > div.cta-wrapper > a.dark

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head.at-element-marker > meta head.at-element-marker > meta

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
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
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
`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
ARIA input fields have accessible names
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
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.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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
ARIA `progressbar` 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
Form elements have associated labels
Links are distinguishable without relying on color.
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.
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.
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
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::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main-navigation-bar" 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+
Alt Text Quality
All 80 images OK
PASS
All 80 images OK
Info::
1 decorative image(s) correctly marked
Info::
79 image(s) with good alt text
80 images 79 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#togglefolding-panel-4checkboxSHOPPING TOOLSfor/id
#togglefolding-panel-1checkboxVEHICLESfor/id
#togglefolding-panel-2checkboxHELPFUL LINKSfor/id
#togglefolding-panel-3checkboxOWNERSfor/id
#togglefolding-panel-5checkboxABOUT TOYOTAfor/id
#EssentialCookiesSlidecheckboxEssential Cookiesnone
#FunctionalCookiesSlidecheckboxFunctional and Performance Cookiesnone
#TargetingCookiesSlidecheckboxTargeting Cookies and Session Replay Technologynone
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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