Skip to content
https://ridge.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
33
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 REVIEW 9 FIX
F
Heading Hierarchy
Action
52 headings, 6 skip(s)
FIX
52 headings, 6 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
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.
Warning::
8 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Your Cart is Empty
  • H4 LIMITED EDITION skipped
  • H1 Two Processes.SAME Obsession.
  • H4 LIMITED EDITION skipped
  • H1 Two Processes.SAME Obsession. duplicate H1
  • H4 LIMITED EDITION skipped
  • H1 Two Processes.SAME Obsession. duplicate H1
  • H2 SHOP BY CATEGORIES
  • H3 RIDGE WALLETS
  • H3 MEN'S RINGS
  • H3 HARDSHELL LUGGAGE
  • H3 CASES & POWER
  • H2 Small Bulge Club
  • H2 Small Bulge Club
  • H2 Small Bulge Club
  • H2 SHOP BY COLLECTION
  • H2 SHOP BY COLLECTION
  • H2 SHOP BY COLLECTION
  • H2 All-Day Power.Rugged Protection.
  • H2 All-Day Power.Rugged Protection.
  • H2 All-Day Power.Rugged Protection.
  • H2 SHOP BY PRODUCT
  • H5 WALLETS skipped
  • H5 FOLDERS
  • H5 POWER BANKS
  • H5 PHONE CASES
  • H5 WEDDING BANDS
  • H5 Hardshell Luggage
  • H5 KEYCASES & KEYCHAINS
  • H5 TRACKER CARD
  • H2 DESIGNED FOR EVERYDAY
  • H2 DESIGNED FOR EVERYDAY
  • H2 DESIGNED FOR EVERYDAY
  • H2 JOIN RIDGE
  • H6 Newsletter skipped
  • H6 Sign Up For Our Newsletter
  • H2 SELECT COUNTRY
  • H2 Shop
  • H2 EXPLORE
  • H2 Support
  • H2 SELECT COUNTRY
  • H4 Transfer History skipped
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H4 (empty)
  • H3 Collections
  • H3 All Favorites
  • H4 (empty)
  • H4 (empty)

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
9 of 160 images have issues
FIX
9 of 160 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
45 decorative image(s) correctly marked
Info::
106 image(s) with good alt text
160 images 106 good alt text 45 decorative 9 missing
IssueCount
missing9 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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
Theme color only
FIX
Theme color only
Info::
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: #ffffff
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 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.

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::
12 navigation landmark(s) detected
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 12 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
20 landmarks
REVIEW
20 landmarks
Info::
<main> landmark present
Info::
12 <nav> landmark(s) found
Warning::
12 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 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

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

C
Form Accessibility
Action
10 of 40 controls have issues
REVIEW
10 of 40 controls have issues
Critical::
10 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit" name="submit">; <input type="submit" name="submit">; <input type="email">; <input type="submit">; <input type="submit">; <input type="text" id="rivo_profile_first_name">; <input type="text" id="rivo_profile_last_name">; <input type="email" id="rivo_profile_email">; <input type="tel">
Info::
30 control(s) properly labeled
40 controls
30 labeled
0 placeholder only
10 unlabeled
ControlTypeLabelMethod
#Search-In-HeadersearchSearch Queryaria-label
#footer-email-fieldinputEmail Addressaria-label
#k_id_nametextNamefor/id
Birthday_dayselectBirthday Dayaria-label
Birthday_monthselectBirthday Montharia-label
Birthday_yearselectBirthday yeararia-label
GenderselectGenderaria-label
accepts_marketingcheckboxnone
#customer_loyalty_accepts_marketingcheckboxnone
customer[email]emailEnter your emailaria-label
accepts_marketingcheckboxnone
#customer_loyalty_accepts_marketingcheckboxnone
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextVerification code inputaria-label
inputtextGift card codearia-label
#rivo_transfer_credit_amountnumberAmountaria-label
#rivo_transfer_credit_messagetextareaMessage (optional)aria-label
inputtextGift URLaria-label
#rivo_claim_transfer_emailemailEmail addressaria-label
#show_gift_card_recipient_fieldscheckboxnone
#rivo_gift_card_variant_idselectGift Card Valuefor/id
#rivo_gift_card_recipient_nametextRecipient Namefor/id
#rivo_gift_card_recipient_emailemailRecipient Emailfor/id
#rivo_gift_card_delivery_datedateDelivery Datefor/id
#rivo_gift_card_messagetextareaMessagefor/id
inputtextReferral URLaria-label
#customer_accepts_marketingcheckboxnone
#customer_sms_accepts_marketingcheckboxnone
inputsubmit(none)none
inputsubmit(none)none
submitsubmit(none)none
inputemail(none)none
#rivo_profile_first_nametext(none)none
#rivo_profile_last_nametext(none)none
#rivo_profile_emailemail(none)none
submitsubmit(none)none
inputtel(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit" name="submit">; <input type="submit" name="submit">; <input type="email">; <input type="submit">; <input type="submit">; <input type="text" id="rivo_profile_first_name">; <input type="text" id="rivo_profile_last_name">; <input type="email" id="rivo_profile_email">; <input type="tel">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA
h1 Two Processes.
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
h1 SAME Obsession.
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Two Processes.
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
h1 SAME Obsession.
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Two Processes.
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
h1 SAME Obsession.
1.00:1
#FFFFFF
on
#FFFFFF
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Your Cart is Empty
1.02:1
#000000
on
#010305
needs 3.0:1 (large text)
24px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Two Processes.1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h1 SAME Obsession.1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h1 Two Processes.1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h1 SAME Obsession.1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h1 Two Processes.1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h1 SAME Obsession.1.00:13.0:1
#FFFFFF
#FFFFFF
Fail
h2 Your Cart is Empty1.02:13.0:1
#000000
#010305
Fail
h2 SHOP BY CATEGORIES21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Small Bulge Club21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Small Bulge Club21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Small Bulge Club21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SHOP BY COLLECTION21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SHOP BY COLLECTION21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SHOP BY COLLECTION21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All-Day Power.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rugged Protection.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All-Day Power.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rugged Protection.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All-Day Power.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rugged Protection.21.00:13.0: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.

A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 28 passed
PASS
90

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.mobile > div.tier2-content > div.tier2-items > button.slick-prev div.mobile > div.tier2-content > div.tier2-items > button.slick-prev
div.mobile > div.tier2-content > div.tier2-items > button.slick-next div.mobile > div.tier2-content > div.tier2-items > button.slick-next

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.

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
WALLETS div.row-collections > div.column-collection-grid > a.column-collection-25 > h5

These are opportunities to improve keyboard navigation in your application.

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 > meta head > meta

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
PREFERENCES div#pandectes-banner > div.pd-cookie-banner-window > div.cc-compliance > button.cc-btn
ACCEPT div#pandectes-banner > div.pd-cookie-banner-window > div.cc-compliance > button.cc-btn
○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
●Input buttons have discernible text.
●Form elements have associated labels
●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
●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
●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.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 type="image">` elements have `[alt]` text
○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.
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback