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 3 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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

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.

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #000000

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 ModePartial Dark Mode

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 ✗

Link & Button Quality

1 issue(s) across 88 links and 20 buttons

REVIEW

1 issue(s) across 88 links and 20 buttons

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://stories.rivian.com; https://www.linkedin.com/company/rivian; https://www.instagram.com/rivianofficial; https://x.com/rivian; https://www.youtube.com/channel/UCPMdVVKDEUrbp3nH46sTZmg

1 button(s) with no accessible text

83 link(s) with descriptive text

88 links

0 empty

0 generic text

5 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://stories.rivian.com	Stories	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/rivian	Linked-In SVG	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/rivianofficial	Instagram SVG	new tab	Add '(opens in new tab)' to text
https://x.com/rivian	Rivian X Page – X Icon	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCPMdVVK…	YoutTube SVG	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

102 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://stories.rivian.com; https://www.linkedin.com/company/rivian; https://www.instagram.com/rivianofficial; https://x.com/rivian; https://www.youtube.com/channel/UCPMdVVKDEUrbp3nH46sTZmg

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

13 icon(s) detected

REVIEW

13 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA 1 pass AA only

h1 Meet R2

1.96:1

#000000

#403D40

needs 3.0:1 (large text)

32px · mid-page

h2 Choose your own savings

2.18:1

#000000

#4F441E

needs 3.0:1 (large text)

24px · above the fold · over background image/gradient

h2 2026 builds,

1.51:1

#000000

#2D2C30

needs 3.0:1 (large text)

24px · mid-page

h2 starting at

1.45:1

#000000

#2A292D

needs 3.0:1 (large text)

24px · mid-page

h2 1.99% APR³

1.43:1

#000000

#28282B

needs 3.0:1 (large text)

24px · bottom of viewport

a Skip To Main

3.31:1

#000000

#616055

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Meet R2	1.96:1	3.0:1	#000000	#403D40	Fail
h2 Choose your own savi…	2.18:1	3.0:1	#000000	#4F441E	Fail
h2 2026 builds,	1.51:1	3.0:1	#000000	#2D2C30	Fail
h2 starting at	1.45:1	3.0:1	#000000	#2A292D	Fail
h2 1.99% APR³	1.43:1	3.0:1	#000000	#28282B	Fail
h2 r1s	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 r1t	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Electric vehicles de…	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Award-winning safety	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Brooklyn, NY	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Ready for electric e…	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Designed to get bett…	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Keep exploring	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h2 Keep the world adven…	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h3 Shop	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h3 Get updates	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h3 Trade in	6.49:1	3.0:1	#000000	#8F8F8F	Pass
h3 Service	6.49:1	3.0:1	#000000	#8F8F8F	Pass
title Rivian: Electric Veh…	5.76:1	4.5:1	#000000	#89867B	Pass
a Skip To Main	3.31:1	4.5:1	#000000	#616055	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.

A+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H2 Choose your own savings
H1 Meet R2
H2 2026 builds, starting at 1.99% APR³
H2 r1s
H2 r2
H2 r1t
H2 Electric vehicles designed for adventure
H2 Award-winning safety
H2 Brooklyn, NY
H2 Ready for electric exploration
H2 Designed to get better with time
H2 Keep exploring
H3 Shop
H3 Get updates
H3 Trade in
H3 Service
H2 Keep the world adventurous forever

A+

Alt Text Quality

All 35 images OK

PASS

All 35 images OK

1 image(s) with alt text over 125 characters

34 image(s) with good alt text

35 images 34 good alt text

Issue	Count
too long	1 image(s)

Form Accessibility

1 of 6 controls have issues

PASS

1 of 6 controls have issues

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

5 control(s) properly labeled

6 controls

5 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#email	email	Email	aria-label
#zipCodeNoCountry	text	Zip code	aria-label
input	text	First Name	aria-label
input	text	Last Name	aria-label
input	text	Email	aria-label
#g-recaptcha-response-100000	textarea	(none)	none

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

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

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 31 passed

PASS

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
Nous pensons que vous êtes en France. Mettre à jour votre région? `body.x-small > div#radix-:rf:`
Sélectionnez votre emplacement North America Europe `body.x-small > div > div#radix-:rk:`

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.flex > div.pointer-events-auto > div.flex > button.rounded-xxl `div.flex > div.pointer-events-auto > div.flex > button.rounded-xxl`

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.

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
US `div > div.relative > div > button#locale-picker`

○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

●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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

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

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

●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"]`

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

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

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

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