Skip to content
https://clubrideapparel.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
8
REVIEW
1
PASS
15
INFO
0
Checks
24
15 PASS 1 REVIEW 8 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 12 -1-on-focusable
FIX
0 positive, 12 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="accessiblyAppDialogButton">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
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 Verifying your connection... ✓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::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA 5 pass AA only
h2 Cookie consent
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 LEAN INTO IT
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FLANNEL SEASON IS HERE
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 IT STARTED WITH A SINGLE SPEED
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop by category
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Men's Shirts
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Men's Bottoms
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Women's Shirts
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Women's Bottoms
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FREE GROUND SHIPPING ON ORDERS OVER $125
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Men's Daniel Flannel
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Women's Liv'n Flannel
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Men's Griffin Flannel Shacket
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Women's Best Friend Flannel Shacket
1.27:1
#000000
on
#1F1F1F
needs 3.0:1 (large text)
19px · bottom of viewport
title Mountain Bike and Adventure Clothing | C…
4.45:1
#000000
on
#66767D
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Cookie consent1.27:13.0:1
#000000
#1F1F1F
Fail
h2 LEAN INTO IT1.27:13.0:1
#000000
#1F1F1F
Fail
h2 FLANNEL SEASON IS HE…1.27:13.0:1
#000000
#1F1F1F
Fail
h2 IT STARTED WITH A SI…1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Shop by category1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Men's Shirts1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Men's Bottoms1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Women's Shirts1.27:13.0:1
#000000
#1F1F1F
Fail
h2 Women's Bottoms1.27:13.0:1
#000000
#1F1F1F
Fail
h2 FREE GROUND SHIPPING…1.27:13.0:1
#000000
#1F1F1F
Fail
h3 Men's Daniel Flannel1.27:13.0:1
#000000
#1F1F1F
Fail
h3 Women's Liv'n Flanne…1.27:13.0:1
#000000
#1F1F1F
Fail
h3 Men's Griffin Flanne…1.27:13.0:1
#000000
#1F1F1F
Fail
h3 Women's Best Friend …1.27:13.0:1
#000000
#1F1F1F
Fail
title Mountain Bike and Ad…4.45:14.5:1
#000000
#66767D
Fail
span Back4.61:14.5:1
#000000
#6B787E
Pass
div Accessibility option…4.87:14.5:1
#000000
#6E7C82
Pass
p Are you sure you wan…5.22:14.5:1
#000000
#748184
Pass
button Cancel5.24:14.5:1
#000000
#768184
Pass
div Content5.32:14.5:1
#000000
#778285
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+
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN ASIDE "Accessibility Tools" CONTENTINFO (missing!)
A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Cookie consent
  • H1 (empty)
  • H2 LEAN INTO IT
  • H3 Men's Daniel Flannel
  • H3 Women's Liv'n Flannel
  • H3 Men's Griffin Flannel Shacket
  • H3 Women's Best Friend Flannel Shacket
  • H2 FLANNEL SEASON IS HERE
  • H2 IT STARTED WITH A SINGLE SPEED
  • H2 Shop by category
  • H2 Men's Shirts
  • H2 Men's Bottoms
  • H2 Women's Shirts
  • H2 Women's Bottoms
  • H2 FREE GROUND SHIPPING ON ORDERS OVER $125

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
4 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 4 all-caps heading(s)
A+
Alt Text Quality
All 96 images OK
PASS
All 96 images OK
Info::
19 decorative image(s) correctly marked
Info::
77 image(s) with good alt text
96 images 77 good alt text 19 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#accessibly-app-language-searchinputSearch languagearia-label
qtextSearcharia-label
contact[email]emailEmailaria-label
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "accessibly-app-language-search" should use type="search" (currently type="text")
Field name "accessibly-app-language-search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="javascript:false")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 20 visible text node(s) render at >= 12 CSS pixels
PASS
All 20 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 28 passed
PASS
97

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

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
div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link
div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link
div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link
div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link div#slider-template--20202423058503__gallery_gyhzy8 > div.slider__grid > div.slider__item > a.image-overlay__image-link

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-*]` 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
●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.
●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
●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.
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback