Skip to content
https://p.ideaworldweb.com/uimh/cranktest/

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
9
REVIEW
4
PASS
11
INFO
0
Checks
24
11 PASS 4 REVIEW 9 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email">
D
Mobile-Readable Font Sizes
Action
62% of visible text renders at >= 12 CSS px (43 below threshold)
FIX
62% of visible text renders at >= 12 CSS px (43 below threshold)
Warning::
43 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Rent a Bike"); <span> 11.0px ("Road · Gravel · MTB & More"); <span> 11.0px ("Shop Bikes"); <span> 11.0px ("Clothing · Shoes · Helmets"); <span> 11.0px ("Shop Apparel").
F
404 Error Page
Action
HTTP 400, bare page
FIX
HTTP 400, bare page
Warning::
Unexpected status code: HTTP 400
Expected HTTP 404 but received 400. This may confuse search engine crawlers.
Got: HTTP 400
Warning::
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 400 ✗Page Title Bad Request ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ 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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

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

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 OWN THE
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
32px · bottom of viewport
h1 BUILT FOR THE
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
32px · bottom of viewport
h1 TUNED BY
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Find What Fits Your Ride
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Premium Performance Inventory
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cranking Deals & Offers
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Beyond the sale
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to ride
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Jebel Hafeet?
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Elite
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Partners
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Bikes
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Apparel
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Accessories
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Component & Wheels
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Nutrition
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Summer Clearance
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Free Bike Fitting
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bike Rentals
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bike Fitting
1.01:1
#000000
on
#010101
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 OWN THE1.01:13.0:1
#000000
#010101
Fail
h1 BUILT FOR THE1.01:13.0:1
#000000
#010101
Fail
h1 TUNED BY1.01:13.0:1
#000000
#010101
Fail
h2 Find What Fits Your …1.01:13.0:1
#000000
#010101
Fail
h2 Premium Performance …1.01:13.0:1
#000000
#010101
Fail
h2 Cranking Deals & Off…1.01:13.0:1
#000000
#010101
Fail
h2 Beyond the sale1.01:13.0:1
#000000
#010101
Fail
h2 Ready to ride1.01:13.0:1
#000000
#010101
Fail
h2 Jebel Hafeet?1.01:13.0:1
#000000
#010101
Fail
h2 Our Elite1.01:13.0:1
#000000
#010101
Fail
h2 Partners1.01:13.0:1
#000000
#010101
Fail
h3 Bikes1.01:13.0:1
#000000
#010101
Fail
h3 Apparel1.01:13.0:1
#000000
#010101
Fail
h3 Accessories1.01:13.0:1
#000000
#010101
Fail
h3 Component & Wheels1.01:13.0:1
#000000
#010101
Fail
h3 Nutrition1.01:13.0:1
#000000
#010101
Fail
h3 Summer Clearance1.01:13.0:1
#000000
#010101
Fail
h3 Free Bike Fitting1.01:13.0:1
#000000
#010101
Fail
h3 Bike Rentals1.01:13.0:1
#000000
#010101
Fail
h3 Bike Fitting1.01:13.0:1
#000000
#010101
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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 17 passed
REVIEW
77

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#compareBar > div.compare-bar__inner > div.compare-bar__actions > button#compareBarCta div#compareBar > div.compare-bar__inner > div.compare-bar__actions > button#compareBarCta

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
body.cm-loaded > div.contact-action > a.item body.cm-loaded > div.contact-action > a.item
body.cm-loaded > div.contact-action > a.item body.cm-loaded > div.contact-action > a.item
body.cm-loaded > div.contact-action > a.item body.cm-loaded > div.contact-action > a.item

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.

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
APPAREL div#productTrack > article.product-card > div.product-card__body > span.product-card__cat
/unit div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > small
20+ units div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > em
HELMET div#productTrack > article.product-card > div.product-card__body > span.product-card__cat
/unit div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > small
15+ units div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > em
EYEWEAR div#productTrack > article.product-card > div.product-card__body > span.product-card__cat
/unit div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > small
10+ units div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > em
CYCLING GEAR div#productTrack > article.product-card > div.product-card__body > span.product-card__cat
/unit div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > small
50+ units div.product-card__price-row > div.product-card__price-left > span.product-card__bulk > em
AT THE BENCH section#services > div.section-head > div > span.section-eyebrow
01 section#services > div.services__rows > div.service-row > span.service-row__bgnum
02 section#services > div.services__rows > div.service-row > span.service-row__bgnum
03 section#services > div.services__rows > div.service-row > span.service-row__bgnum
04 section#services > div.services__rows > div.service-row > span.service-row__bgnum
Powered By: IDEA WEB GLOBAL TECHNOLOGY L.L.C body.cm-loaded > footer.footer > div.footer__bottom > span
IDEA WEB GLOBAL TECHNOLOGY L.L.C div.footer__bottom > span > a > span.text-primary
© 2026 Crank Masters Cycling Shop. All rights reserved. body.cm-loaded > footer.footer > div.footer__bottom > span
Pay with Tabby · Tamara · Card footer.footer > div.footer__bottom > div.footer__legal > span.footer__pay

These are opportunities to improve the legibility of your content.

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
BIKES footer.footer > div.footer__top > div.footer__col > h4

These are opportunities to improve keyboard navigation in your application.

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
→ footer.footer > div.footer__newsletter-row > form.footer__form > button

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
RENT A BIKE header#siteHeader > div.site-header__inner > div.header-actions > a#reserveBtn
2 header#siteHeader > div.site-header__inner > div.header-actions > button#wishBtn
2 header#siteHeader > div.site-header__inner > div.header-actions > button#cartBtn
○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>`
●`[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.
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○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.
○No element has a `[tabindex]` value greater than 0
○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.
A
Heading Hierarchy
42 headings
PASS
42 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 OWN THE CLIMB
  • H1 BUILT FOR THE DUNES duplicate H1
  • H1 TUNED BY MASTERS duplicate H1
  • H2 Find What Fits Your Ride
  • H3 Bikes
  • H3 Apparel
  • H3 Accessories
  • H3 Component & Wheels
  • H3 Nutrition
  • H2 Premium Performance Inventory
  • H3 FALCO Aero Carbon Road Bike – Tropical Purple Edition
  • H3 NEON Nova X21 Premium Cycling Sunglasses
  • H3 UKE Pro Aero Cycling Jersey Series
  • H3 ANGLER Aero-Stream Cycling Helmet
  • H3 NEON Air Pro X21 Photochromic Sports Eyewear
  • H3 UKE Aero-Knit Performance Cycling Socks
  • H2 Cranking Deals & Offers
  • H3 Summer Clearance
  • H3 Free Bike Fitting
  • H2 Beyond the sale
  • H3 Bike Rentals
  • H3 Bike Fitting
  • H3 Service & Repair
  • H3 B2B Wholesale
  • H2 Ready to rideJebel Hafeet?
  • H2 Our ElitePartners
  • H3 Shopping Cart 2
  • H4 FALCO Aero Carbon Road Bike
  • H4 NEON Nova X21 Sunglasses
  • H3 Wishlist 2
  • H4 UKE Pro Aero Cycling Jersey
  • H4 ANGLER Aero-Stream Helmet
  • H4 Bikes
  • H4 Apparel
  • H4 Accessories
  • H4 Components & Wheels
  • H4 Nutrition
  • H4 Services
  • H4 Company
  • H4 Visit Us
  • H4 Stay Geared Up
  • H3 Compare Products

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 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: 3 all-caps heading(s)
A+
Alt Text Quality
All 31 images OK
PASS
All 31 images OK
Info::
31 image(s) with good alt text
31 images 31 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextSearcharia-label
inputemailEmail addressaria-label
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "Search" should use type="search" (currently type="text")
Field name "Search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback