Skip to content
https://cuban-links-storefront.fitnessbuisnessgrift26.workers.dev/story

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
7
REVIEW
1
PASS
16
INFO
0
Checks
24
16 PASS 1 REVIEW 7 FIX
D
Mobile-Readable Font Sizes
Action
18% of visible text renders at >= 12 CSS px (75 below threshold)
FIX
18% of visible text renders at >= 12 CSS px (75 below threshold)
Warning::
75 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: <button> 8.0px ("ENQUIRY BAG"); <p> 9.0px ("ABOUT CUBAN LINKS"); <p> 9.0px ("THE DETAILS"); <a> 9.0px ("VIEW THE CATALOGUE"); <p> 8.0px ("CHAINS WITH").
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
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 404 ✓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
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: #111210
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
2 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 2 <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, 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 About Cuban Links
1.03:1
#000000
on
#060505
needs 3.0:1 (large text)
32px · bottom of viewport
h2 How chain styles differ
1.03:1
#000000
on
#060505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Check the
1.03:1
#000000
on
#060505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Technical
1.03:1
#000000
on
#060505
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Set the
1.03:1
#000000
on
#060505
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Find a link.
1.09:1
#000000
on
#0D0E0D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Look closer.
1.03:1
#000000
on
#060505
needs 3.0:1 (large text)
19px · bottom of viewport
title Our Story — Cuban Links
1.18:1
#000000
on
#171815
needs 4.5:1 (normal text)
16px · top of page (header area)
p Preview · Enquiries only
1.08:1
#000000
on
#0D0D0C
needs 4.5:1 (normal text)
16px · top of page (header area)
span CUBAN
1.09:1
#000000
on
#0D0E0C
needs 4.5:1 (normal text)
16px · top of page (header area)
b LINKS
1.24:1
#000000
on
#1F1C16
needs 3.0:1 (large text)
16px · top of page (header area)
a Home
1.25:1
#000000
on
#211D17
needs 4.5:1 (normal text)
16px · above the fold
button Shop
1.16:1
#000000
on
#18160F
needs 4.5:1 (normal text)
16px · above the fold
i ⌄
1.15:1
#000000
on
#171510
needs 4.5:1 (normal text)
16px · above the fold
button Studio
1.22:1
#000000
on
#1D1B18
needs 4.5:1 (normal text)
16px · above the fold
i ⌄
1.18:1
#000000
on
#191815
needs 4.5:1 (normal text)
16px · above the fold
a Wholesale
1.16:1
#000000
on
#181614
needs 4.5:1 (normal text)
16px · above the fold
a Bespoke
1.22:1
#000000
on
#1C1B18
needs 4.5:1 (normal text)
16px · above the fold
a Our story
1.13:1
#000000
on
#151312
needs 4.5:1 (normal text)
16px · above the fold
a Instagram
1.22:1
#000000
on
#1B1B19
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 About Cuban Links1.03:13.0:1
#000000
#060505
Fail
h2 How chain styles dif…1.03:13.0:1
#000000
#060505
Fail
h2 Check the1.03:13.0:1
#000000
#060505
Fail
h2 Technical1.03:13.0:1
#000000
#060505
Fail
h2 Set the1.03:13.0:1
#000000
#060505
Fail
h3 Find a link.1.09:13.0:1
#000000
#0D0E0D
Fail
h3 Look closer.1.03:13.0:1
#000000
#060505
Fail
title Our Story — Cuban …1.18:14.5:1
#000000
#171815
Fail
p Preview · Enquiries…1.08:14.5:1
#000000
#0D0D0C
Fail
span CUBAN1.09:14.5:1
#000000
#0D0E0C
Fail
b LINKS1.24:13.0:1
#000000
#1F1C16
Fail
a Home1.25:14.5:1
#000000
#211D17
Fail
button Shop1.16:14.5:1
#000000
#18160F
Fail
i ⌄1.15:14.5:1
#000000
#171510
Fail
button Studio1.22:14.5:1
#000000
#1D1B18
Fail
i ⌄1.18:14.5:1
#000000
#191815
Fail
a Wholesale1.16:14.5:1
#000000
#181614
Fail
a Bespoke1.22:14.5:1
#000000
#1C1B18
Fail
a Our story1.13:14.5:1
#000000
#151312
Fail
a Instagram1.22:14.5:1
#000000
#1B1B19
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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 navigation" MAIN ASIDE CONTENTINFO footer

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

A+
Heading Hierarchy
7 headings
PASS
7 headings
Info::
Single H1 present
  • H3 Find a link.
  • H3 Look closer.
  • H1 About Cuban Links
  • H2 How chain styles differ
  • H2 Check thesmall things.
  • H2 Technicaldetails.
  • H2 Set theatmosphere.
A+
Heading Text Quality
All 7 heading(s) have substantive, well-formed text
PASS
All 7 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
4 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
9 images 5 good alt text 4 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search">
Info::
8 control(s) properly labeled
9 controls
8 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectLANGnone
selectselectCURnone
selectselectLANGnone
selectselectCURnone
selectselectLANGnone
selectselectCURnone
inputrangeTrack positionaria-label
inputrangeVolumearia-label
inputsearch(Try Cuban, curb, silver, pendant…)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Form Input Types
9 form control(s) checked, no type mismatches
PASS
9 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
9 form control(s) checked, no input-semantic issues
PASS
9 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-GB"
PASS
Lang attribute set to "en-GB"
Info::
<html lang="en-GB"> is set and valid
Got: en-GB
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+
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+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 17 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
TECHNICAL DETAILS × PRODUCT DETAILS TECHNICAL DETAILS. PROFILE Cuban link WID… body#top > div.global-overlays > aside#specs-drawer
APPEARANCE × A LITTLE HIDDEN AWAY SET THE ATMOSPHERE. LANGUAGE & CURRENCY LAN… body#top > div.global-overlays > aside#theme-lab
ENQUIRY BAG 0 × Nothing in the bag yet. Pick a chain and add the options worth… body#top > div.global-overlays > aside#cart-drawer

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.

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
© 2026 CUBAN LINKS div#site-footer > footer.site-footer > div.footer-bottom > span
BUILT AROUND THE LINK. div#site-footer > footer.site-footer > div.footer-bottom > span
GBP / WORLDWIDE ENQUIRIES div#site-footer > footer.site-footer > div.footer-bottom > span
LANG aside#theme-lab > div.locale-controls > label > span
CUR aside#theme-lab > div.locale-controls > label > span

These are opportunities to improve the legibility of your content.

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
CUBAN LINKS body#top > div#site-header > header.masthead > a.brand
○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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 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
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○Form elements have associated labels
○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
○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.
○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