Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 4 REVIEW 8 FIX

Mobile Keyboard & Autofill

Action

3/4 eligible field(s) missing autocomplete or inputmode

FIX

3/4 eligible field(s) missing autocomplete or inputmode

3 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: search, email.

Got: <input type="search" name="q" id="Search-In-Modal-1">, <input type="search" name="q" id="Search-In-Modal">, <input type="email" name="email" id="email_016JB91TTR00000000002GQ7Q3">

Tabindex Anti-Patterns

Action

0 positive, 51 -1-on-focusable

FIX

0 positive, 51 -1-on-focusable

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

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <input>

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

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

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 ✗

Link & Button Quality

2 issue(s) across 267 links and 7 buttons

REVIEW

2 issue(s) across 267 links and 7 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: # ("More"); # ("More")

2 link(s) open in new tab without warning

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

Got: https://ilovecreatives.studio/; https://favsolution.com/

263 link(s) with descriptive text

267 links

0 empty

2 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	More	generic text	Replace with descriptive text
Before: More Suggested: #
/collections/hemp-denim	Hemp Denim	img no alt	Add alt attribute to the image
/collections/womens-shorts-pants-2	Pants & Shorts	img no alt	Add alt attribute to the image
#	More	generic text	Replace with descriptive text
Before: More Suggested: #
/collections/men-hemp-shirts-core-styles	Core Tees	img no alt	Add alt attribute to the image
/collections/hemp-shirts-jackets-mens	Shirts & Jackets	img no alt	Add alt attribute to the image
/collections/womens-hemp-clothing	Women’s Styles	img no alt	Add alt attribute to the image
https://jungmaven.com/collections/men-he…	Men’s Styles	img no alt	Add alt attribute to the image
/collections/best-sellers	Best Sellers	img no alt	Add alt attribute to the image
/pages/about-us	Our Story	img no alt	Add alt attribute to the image
/collections/intimates-activewear-more	Intimates & Activewear …	img no alt	Add alt attribute to the image
/collections/hemp-shirts-core-styles	Core Styles …	img no alt	Add alt attribute to the image
/collections/hemp-mesh	Hemp Mesh …	img no alt	Add alt attribute to the image
/collections/hemp-denim	Hemp Denim …	img no alt	Add alt attribute to the image
https://ilovecreatives.studio/	Opens link in a new tab for il…	new tab	Add '(opens in new tab)' to text
https://favsolution.com/	Opens link in a new tab for Fa…	new tab	Add '(opens in new tab)' to text

270 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

# ("More"); # ("More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://ilovecreatives.studio/; https://favsolution.com/

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

Iframe Accessibility

2/3 iframe(s) missing title; 0 placeholder(s)

REVIEW

2/3 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.

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.

Mobile-Readable Font Sizes

Action

82% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

82% of visible text renders at >= 12 CSS px (6 below threshold)

6 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> 10.0px ("11 COLORS"); <span> 10.0px ("Back in stock"); <span> 10.0px ("11 COLORS"); <span> 10.0px ("New Colors"); <span> 10.0px ("5 COLORS").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 5 pass AA only

a Buy 3+ & Save 15%

1.64:1

#000000

#31341C

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Your cart is empty	6.64:1	3.0:1	#000000	#4D96D5	Pass
h2 From Seed	16.43:1	3.0:1	#000000	#E3E4DF	Pass
h2 To Shirt	16.43:1	3.0:1	#000000	#E3E4DF	Pass
h2 New Arrivals	16.43:1	3.0:1	#000000	#E3E4DF	Pass
h2 Our Story	16.43:1	3.0:1	#000000	#E3E4DF	Pass
h2 in the press	16.43:1	3.0:1	#000000	#E3E4DF	Pass
h2 Collections	16.43:1	3.0:1	#000000	#E3E4DF	Pass
title Jungmaven \| High Qua…	5.28:1	4.5:1	#000000	#2F84CB	Pass
a Skip to content	5.88:1	4.5:1	#000000	#3E8CD1	Pass
a Continue shopping	7.83:1	4.5:1	#000000	#65A3DC	Pass
p Have an account?	8.20:1	4.5:1	#000000	#6DA7DB	Pass
a Log in	9.26:1	4.5:1	#000000	#80B1DE	Pass
p to check out faster.	9.62:1	4.5:1	#000000	#89B4DB	Pass
div Made in the USA	10.83:1	4.5:1	#000000	#9ABEE1	Pass
a Buy 3+ & Save 15%	1.64:1	4.5:1	#000000	#31341C	Fail
a The Hemp Exchange: B…	6.29:1	4.5:1	#000000	#9C8C53	Pass
a Free Shipping & Easy…	7.00:1	4.5:1	#000000	#A59460	Pass
span Cart	5.21:1	4.5:1	#000000	#8D7E46	Pass
a New	5.35:1	4.5:1	#000000	#8F804A	Pass
summary Women	7.43:1	4.5:1	#000000	#AB986A	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

6 landmarks

PASS

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <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

Heading Hierarchy

9 headings

PASS

9 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

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

H2 Your cart is empty
H1 (empty)
H1 That HempFeeling duplicate H1
H2 From Seed
H2 To Shirt
H2 New Arrivals
H2 Our Story
H2 in the press
H2 Collections

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

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 9 heading(s) have substantive, well-formed text

PASS

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

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

A+

Alt Text Quality

All 143 images OK

PASS

All 143 images OK

38 decorative image(s) correctly marked

105 image(s) with good alt text

143 images 105 good alt text 38 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#Search-In-Modal-1	search	Search	for/id
#Search-In-Modal	search	Search our store	for/id
#email_016JB91TTR00000000002GQ7Q3	email	Email	aria-label

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

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+

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, 27 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
New Arrivals `section#shopify-section-template--15578917372102__6026ae36-9429-4975-8885-fa01e560f2ca > div.wrapper > div.content > h2.h1`
Montego Open Knit Vest — Link to product `product-card.product__list-item > a.product__item > div > p.product__item-heading`
Makena 100% Hemp Short — Link to product `product-card.product__list-item > a.product__item > div > p.product__item-heading`
Shop Now `section#shopify-section-template--15578917372102__6026ae36-9429-4975-8885-fa01e560f2ca > div.wrapper > div.content > a.button-wave-cream`

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

●`[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 are distinguishable without relying on color.

●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

●Skip links are focusable.

●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

○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

○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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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