Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 5 REVIEW 8 FIX

Alt Text Quality

Action

2 of 116 images have issues

FIX

2 of 116 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

17 image(s) with alt text over 125 characters

9 decorative image(s) correctly marked

88 image(s) with good alt text

116 images 88 good alt text 9 decorative 2 missing

Issue	Count
missing	2 image(s)
too long	17 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

15 issue(s) across 451 links and 67 buttons

FIX

15 issue(s) across 451 links and 67 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; https://www.jennikayne.com/collections/clothing-womens-shop-all-bottoms; https://www.jennikayne.com/collections/clothing-womens-shop-all-sweaters

2 link(s) open in new tab without warning

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

Got: https://accessibe.com/blog/knowledgebase/screen-reader-guide; https://www.jennikayne.com/policies/privacy-policy

12 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#mobile__menu--back-drawer; button#mobile__menu--back-drawer-0; button#mobile__menu--back-drawer-1; button#mobile__menu--back-drawer-2; button#mobile__menu--back-drawer-3; button#mobile__menu--back-drawer-4; button#mobile__menu--back-drawer-5; button#mobile__menu--back-drawer-6; button#mobile__menu--back-drawer-7; button#mobile__menu--back-drawer-8 (+2 more)

446 link(s) with descriptive text

451 links

3 empty

0 generic text

2 new tab

12 empty buttons

Element	Text	Issue	Suggested Fix
https://accessibe.com/blog/knowledgebase…	Accessibility Screen-Reader Gu…	new tab	Add '(opens in new tab)' to text
https://www.jennikayne.com/policies/priv…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://www.jennikayne.com/pages/denim-f…	INTRODUCING JENNI KAYNE DENIM	img no alt	Add alt attribute to the image
https://www.jennikayne.com/pages/denim-f…	INTRODUCING JENNI KAYNE DENIM	img no alt	Add alt attribute to the image
https://www.jennikayne.com/collections/c…	(empty)	empty	Add link text or aria-label
https://www.jennikayne.com/collections/c…	(empty)	empty	Add link text or aria-label
https://www.jennikayne.com/collections/t…	ESSENTIALS YOU’LL ALWAYS COM…	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

501 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; https://www.jennikayne.com/collections/clothing-womens-shop-all-bottoms; https://www.jennikayne.com/collections/clothing-womens-shop-all-sweaters

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://accessibe.com/blog/knowledgebase/screen-reader-guide; https://www.jennikayne.com/policies/privacy-policy

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

Icon-only buttons need an aria-label so screen readers can announce them.

button#mobile__menu--back-drawer; button#mobile__menu--back-drawer-0; button#mobile__menu--back-drawer-1; button#mobile__menu--back-drawer-2; button#mobile__menu--back-drawer-3; button#mobile__menu--back-drawer-4; button#mobile__menu--back-drawer-5; button#mobile__menu--back-drawer-6; button#mobile__menu--back-drawer-7; button#mobile__menu--back-drawer-8 (+2 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile Keyboard & Autofill

Action

21/21 eligible field(s) missing autocomplete or inputmode

FIX

21/21 eligible field(s) missing autocomplete or inputmode

20 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: country-name, email.

Got: <input type="radio" name="country">, <input type="radio" name="country">, <input type="radio" name="country">, <input type="radio" name="country">, <input type="radio" name="country">

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" id="email">

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

15 landmarks

REVIEW

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

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

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

Iframe Accessibility

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

REVIEW

2/5 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

85% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (3 below threshold)

3 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> 11.0px ("Accept"); <button> 11.0px ("Deny Non-Essential"); <button> 11.0px ("Manage Preferences").

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Action

Score 71/100 — 8 failing, 22 passed

REVIEW

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Shop All `div#menu-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc > div.xl:col-span-24 > div.flex > div#mega-menu-AYW1TQ1o2SFNTNW03c__sub_item_hQQatN`
Sweaters `div#menu-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc > div.xl:col-span-24 > div.flex > div#mega-menu-AbGZrVGx0TjFTemJEQ__sub_item_QHVhC3`
Shoes `div#menu-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc > div.xl:col-span-24 > div.flex > div#mega-menu-AZS8zL3hGR0hvWlQ3S__sub_item_BFzVVH`
Featured `div#menu-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc > div.xl:col-span-24 > div.flex > div#mega-menu-Ab3BVeEdTNFR1L0oxV__sub_item_tMCKim`
Blog `div#menu-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc > div.xl:col-span-24 > div.flex > div#mega-menu-AYXo0T2QxbXQwVHN5S__sub_item_DD63VB`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
New Arrivals The Classics Shop All Sweaters Shoes Featured Blog `div.nav-mobile-menu > nav.nav-mobile > div#shopify-block-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc > div#menu-Aam1OclY0TmMwQWtwc__menu_item_qmGFWc`

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Account Welcome to Jenni Kayne My Account Rewards Become a JKH Member Store Loc… `div#shopify-section-redesign-header > sticky-header > div.account-drawer--wrapper > div.account-drawer`
Choose a country or region North America Europe Oceania Shop In United States `div#shopify-section-redesign-header > sticky-header > div.country-drawer--wrapper > div.country-selector-drawer`
Close cart drawer YOUR CART IS EMPTY. Shop New Arrivals Shop Best-Sellers OUR… `body#jenni-kayne-california-inspired-design-for-the-wardrobe-and-home > div.cart-drawer--wrapper > div#cartDrawer`

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
© JenniKayne 2026. All rights reserved. `div.mx-auto > div.lg:col-span-6 > div.mt-8 > span.redesign-body-8`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.video > a.lg:hidden > video#template--27997824057517__redesign_hero_EmMjym-mobile-video > img `div.video > a.lg:hidden > video#template--27997824057517__redesign_hero_EmMjym-mobile-video > img`

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.container > div.grid > div.lg:col-span-4 > a.flex `div.container > div.grid > div.lg:col-span-4 > a.flex`
div.flex > div.w-full > div.relative > a.block `div.flex > div.w-full > div.relative > a.block`
div.flex > div.w-full > div.relative > a.block `div.flex > div.w-full > div.relative > a.block`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
My Account Rewards Become a JKH Member Store Locations Start a Return Customer … `div.relative > div.flex > div.px-28 > ul.drawer-content`
North America Europe Oceania `div.relative > div.flex > div.px-28 > ul#country-selector-accordion`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Cart 0 `div.lg:col-span-4 > div.flex > div.header-utility > button#openDrawerBtn`

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

●Buttons have an accessible name

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●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

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

○Tables have different content in the summary attribute and `<caption>`.

○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

51 headings

PASS

51 headings

Single H1 present

1 empty heading(s)

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

H3 Shoes Shoes
H3 Featured Featured
H3 Blog Blog
H3 Rugs Rugs
H3 Kitchen & Dining Kitchen & Dining
H3 Clothing Clothing
H3 Shoes Shoes
H3 Accessories Accessories
H3 Sweaters Sweaters
H3 Shop By Style Shop By Style
H3 Shop by Material Shop by Material
H3 Jenni's Favorites Jenni's Favorites
H3 Shoes Shoes
H3 Featured Featured
H3 Blog Blog
H3 Shop By Type Shop By Type
H3 Shop By Room Shop By Room
H3 Decor Decor
H3 Textiles Textiles
H3 Rugs Rugs
H3 Kitchen & Dining Kitchen & Dining
H3 Featured Featured
H3 Shop By Type Shop By Type
H2 Search History
H2 Popular Search Terms
H2 Top Suggestions
H2 (empty)
H2 Our picks for you
H3 Pleated Skirt
H3 Cable Serena Crewneck
H3 Demi Pant
H3 Pleated Skirt
H1 INTRODUCING JENNI KAYNE DENIM
H2 New Arrivals
H3 Thatcher Crewneck Cardigan
H3 Flynn Cashmere Turtleneck
H3 Demi Pant
H3 Cable Serena Crewneck
H2 ESSENTIALS YOU’LL ALWAYS COME BACK TO
H2 The Classics
H3 Flynn Cashmere V-Neck
H3 Cropped Cashmere Cocoon Cardigan
H3 Pleated Skirt
H3 Cashmere Half Zip
H3 Company
H3 Support
H3 Shop
H3 Withdraw your Order (EU Only)
H3 Company
H3 Support
H3 Shop

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

2 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: 2 all-caps heading(s)

Form Accessibility

1 of 22 controls have issues

PASS

1 of 22 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="email" id="email">

21 control(s) properly labeled

22 controls

21 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
country	radio		none
input	input	ftr-tmp-input	aria-label
#email	email	(Your email)	placeholder only

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

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

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

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

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

PASS

22 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

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -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>

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

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 INTRODUCING JENNI KA…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 Search History	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 Popular Search Terms	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 Top Suggestions	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 Our picks for you	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 New Arrivals	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 ESSENTIALS YOU’LL …	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h2 The Classics	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Pleated Skirt	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Cable Serena Crewnec…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Demi Pant	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Pleated Skirt	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Thatcher Crewneck Ca…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Flynn Cashmere Turtl…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Demi Pant	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Cable Serena Crewnec…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Flynn Cashmere V-Nec…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Cropped Cashmere Coc…	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Pleated Skirt	20.43:1	3.0:1	#000000	#FCFCF9	Pass
h3 Cashmere Half Zip	20.43:1	3.0:1	#000000	#FCFCF9	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.