Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – The Loop ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

summary FOOTWEAR

4.14:1

#000000

#6B7067

needs 4.5:1 (normal text)

16px · top of page (header area)

button FOOTWEAR

4.30:1

#000000

#6F7361

needs 4.5:1 (normal text)

16px · above the fold

summary NIKE

1.59:1

#000000

#1E2F54

needs 4.5:1 (normal text)

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

button NIKE

1.52:1

#000000

#142865

needs 4.5:1 (normal text)

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

a DUNKS

1.46:1

#000000

#14265B

needs 4.5:1 (normal text)

16px · above the fold

a BASKETBALL

1.33:1

#000000

#0E1F4F

needs 4.5:1 (normal text)

16px · above the fold

a OFF-WHITE

1.32:1

#000000

#11223C

needs 4.5:1 (normal text)

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

a AIR FORCE 1

1.21:1

#000000

#141C17

needs 4.5:1 (normal text)

16px · above the fold

a AIR MAX

1.93:1

#000000

#52362F

needs 4.5:1 (normal text)

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

a NIKE OTHER

1.64:1

#000000

#313237

needs 4.5:1 (normal text)

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

summary JORDAN

2.82:1

#000000

#595547

needs 4.5:1 (normal text)

16px · mid-page

button JORDAN

3.46:1

#000000

#646357

needs 4.5:1 (normal text)

16px · mid-page

5 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
h2 Item added to your c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured products	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our ema…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The Loop	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a HOME	21.00:1	4.5:1	#000000	#FFFFFF	Pass
summary FOOTWEAR	4.14:1	4.5:1	#000000	#6B7067	Fail
button FOOTWEAR	4.30:1	4.5:1	#000000	#6F7361	Fail
summary NIKE	1.59:1	4.5:1	#000000	#1E2F54	Fail
button NIKE	1.52:1	4.5:1	#000000	#142865	Fail
a DUNKS	1.46:1	4.5:1	#000000	#14265B	Fail
a BASKETBALL	1.33:1	4.5:1	#000000	#0E1F4F	Fail
a OFF-WHITE	1.32:1	4.5:1	#000000	#11223C	Fail
a AIR FORCE 1	1.21:1	4.5:1	#000000	#141C17	Fail
a AIR MAX	1.93:1	4.5:1	#000000	#52362F	Fail
a NIKE OTHER	1.64:1	4.5:1	#000000	#313237	Fail
summary JORDAN	2.82:1	4.5:1	#000000	#595547	Fail
button JORDAN	3.46:1	4.5:1	#000000	#646357	Fail
a JORDAN 1	11.80:1	4.5:1	#000000	#C4C2BD	Pass
a JORDAN 2	21.00:1	4.5: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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

1 empty heading(s)

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

H1 (empty)
H2 Item added to your cart
H2 Featured products
H3 *Better With Age Teresa Double-Wide Denim Short Indigo
H3 *Better With Age Teresa Double-Wide Denim Short Indigo
H3 1017 ALYX 9SM Nylon Track Pants
H3 1017 ALYX 9SM Nylon Track Pants
H3 1017 Alyx 9SM Studios Holster Brown Nylon Cargo Pants
H3 1017 Alyx 9SM Studios Holster Brown Nylon Cargo Pants
H3 1017 Alyx 9SM Tactical Cargo Pants Olive
H3 1017 Alyx 9SM Tactical Cargo Pants Olive
H3 1998 Yankees World Series Champions Tee
H3 1998 Yankees World Series Champions Tee
H3 2025 Pokémon Azure Legends Dialga EX Tin
H3 2025 Pokémon Azure Legends Dialga EX Tin
H3 2025 Pokémon Azure Legends Kyogre EX Tin
H3 2025 Pokémon Azure Legends Kyogre EX Tin
H3 2025 Pokémon Prismatic Evolution Lugia ex & Latias ex Premium Collection Box
H3 2025 Pokémon Prismatic Evolution Lugia ex & Latias ex Premium Collection Box
H2 Subscribe to our emails

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

All 20 heading(s) have substantive, well-formed text

PASS

All 20 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

1 decorative image(s) correctly marked

7 image(s) with good alt text

8 images 7 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#Search-In-Modal	search	Search	for/id
#NewsletterForm--sections--21201428218133__footer	email	Email	for/id

A+

Link & Button Quality

289 links, 35 buttons — all OK

PASS

289 links, 35 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

288 link(s) with descriptive text

289 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text

323 links and buttons have descriptive text

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

https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

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

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

38 explicit tabindex attribute(s) checked, no anti-patterns

PASS

38 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 1 visible text node(s) render at >= 12 CSS pixels

PASS

All 1 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 26 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.

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
Subscribe to our emails `div.footer__content-top > div.footer-block--newsletter > div.footer-block__newsletter > h2.footer-block__heading`
form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--21201428218133__footer `form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--21201428218133__footer`
Email `form#ContactFooter > div.newsletter-form__field-wrapper > div.field > label.field__label`
Follow on `div.relative > button.group > span.cursor-pointer`
© 2026, The Loop `div.footer__content-bottom > div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content`
The Loop `div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content > a`
Powered by Shopify `div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content > a`
Refund policy `ul.policies > li > small.copyright__content > a`
Privacy policy `ul.policies > li > small.copyright__content > a`
Terms of service `ul.policies > li > small.copyright__content > a`
Shipping policy `ul.policies > li > small.copyright__content > a`
Contact information `ul.policies > li > small.copyright__content > a`

These are opportunities to improve the legibility of your content.

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

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

●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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

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

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

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