Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 20 -1-on-focusable

FIX

0 positive, 20 -1-on-focusable

tabindex="-1" on naturally-focusable <button id="drawer-nav-parent-tab-mens-2024-main-mens">

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 <button id="drawer-nav-parent-tab-womens-2024-main-womens">

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 <button id="drawer-nav-parent-tab-kids-2024-main-kids">

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 <button id="drawer-nav-parent-tab-hospitality-2025-hospitality-mobile">

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

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

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

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

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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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 <input>

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

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

F

404 Error Page

Action

HTTP 429, custom page

FIX

HTTP 429, custom page

Unexpected status code: HTTP 429

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

Got: HTTP 429

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

F

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

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

7 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

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

B

Heading Hierarchy

18 headings

REVIEW

18 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Your Cart (0)
H3 Recommended For You
H2 Shop the Look
H2 15 Years Together.
H2 Kith Fall 2026
H2 Kith Women | Hold the Line
H2 Kith Kids Fall 2026
H2 K-Tech Fall 2026
H2 Kith for the New York Yankees 2026
H2 Kith for BMW 2026
H2 Kith & Messi for adidas Football
H2 Kith for the New York Knicks 2026 Champions
H2 Kith for Taxi Driver & Tribeca Festival
H2 Join Our List
H2 Learn
H2 Kith
H2 Policies
H2 Follow Us

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C

Alt Text Quality

Action

2 of 383 images have issues

REVIEW

2 of 383 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

9 image(s) with alt text over 125 characters

13 decorative image(s) correctly marked

359 image(s) with good alt text

383 images 359 good alt text 13 decorative 2 missing

Issue	Count
missing	2 image(s)
too long	9 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

C

Mobile Keyboard & Autofill

Action

8/13 eligible field(s) missing autocomplete or inputmode

REVIEW

8/13 eligible field(s) missing autocomplete or inputmode

8 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, tel.

Got: <input type="search" name="q" id="searchInputDrawerMobile">, <input type="email" name="email" id="email_01JHV01EBJPZ6WAX3NW87F11ZE">, <input type="email" name="email" id="email_01JMFM3QYFWCAWA5NABHNJ6MQ8">, <input type="search" name="q" id="searchInputDrawerDesktop">, <input type="email" name="email" id="email_01JMFJREKGK0X99BM5D6GDM7P9">

C

Tap Target Adequacy

Action

5 tap target(s) too small or too close together

REVIEW

5 tap target(s) too small or too close together

5 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

h2 Shop the Look

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 15 Years Together.

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith Fall 2026

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith Women | Hold the Line

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith Kids Fall 2026

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 K-Tech Fall 2026

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith for the New York Yankees 2026

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith for BMW 2026

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith & Messi for adidas Football

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith for the New York Knicks 2026 Champi…

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith for Taxi Driver & Tribeca Festival

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join Our List

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Learn

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kith

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Policies

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Follow Us

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Your Cart (0)

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Recommended For You

1.20:1

#000000

on

#1F1812

needs 3.0:1 (large text)

19px · bottom of viewport

title Kith – Homepage

1.11:1

#000000

on

#10110C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.08:1

#000000

on

#0F0D0C

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Shop the Look	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 15 Years Together.	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith Fall 2026	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith Women \| Hold th…	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith Kids Fall 2026	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 K-Tech Fall 2026	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith for the New Yor…	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith for BMW 2026	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith & Messi for adi…	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith for the New Yor…	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith for Taxi Driver…	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Join Our List	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Learn	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Kith	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Policies	1.20:1	3.0:1	#000000	#1F1812	Fail
h2 Follow Us	1.20:1	3.0:1	#000000	#1F1812	Fail
h3 Your Cart (0)	1.20:1	3.0:1	#000000	#1F1812	Fail
h3 Recommended For You	1.20:1	3.0:1	#000000	#1F1812	Fail
title Kith – Homepage	1.11:1	4.5:1	#000000	#10110C	Fail
a Skip to content	1.08:1	4.5:1	#000000	#0F0D0C	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.

B

Lighthouse Accessibility Audits

Score 89/100 — 4 failing, 28 passed

REVIEW

89

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

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
Welcome to Kith We proudly offer the following: Shipping to your location fro… `body.template-index > welcome-mat#WelcomeMat`

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.

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
s-hero.hero > a.absolute > video.w-full > img `s-hero.hero > a.absolute > video.w-full > img`

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.

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
Go to slide 2 `s-carousel.hero-carousel > div#HeroCarousel-template--19376068624512__section_linked_carousel_collection_FkVA3r > div.hero-pagination > span.swiper-pagination-bullet`
Go to slide 3 `s-carousel.hero-carousel > div#HeroCarousel-template--19376068624512__section_linked_carousel_collection_FkVA3r > div.hero-pagination > span.swiper-pagination-bullet`
Go to slide 4 `s-carousel.hero-carousel > div#HeroCarousel-template--19376068624512__section_linked_carousel_collection_FkVA3r > div.hero-pagination > span.swiper-pagination-bullet`
Go to slide 5 `s-carousel.hero-carousel > div#HeroCarousel-template--19376068624512__section_linked_carousel_collection_FkVA3r > div.hero-pagination > span.swiper-pagination-bullet`
Go to slide 6 `s-carousel.hero-carousel > div#HeroCarousel-template--19376068624512__section_linked_carousel_collection_FkVA3r > div.hero-pagination > span.swiper-pagination-bullet`

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
0 `body.template-index > s-header#siteHeader > div.w-full > button.relative`
WATCH VIDEO `s-hero.hero > div.absolute > div.flex > a.btn`
LEARN MORE `s-hero.hero > div.absolute > div.flex > a.btn`
SHOP NOW `s-hero.hero > div.absolute > div.flex > a.btn`
SHOP NOW `s-hero.hero > div.absolute > div.flex > a.btn`
SHOP NOW `s-hero.hero > div.absolute > div.flex > a.btn`
SHOP NOW `s-hero.hero > div.absolute > div.flex > a.btn`

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

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

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●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"]`

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

○`<object>` elements have alternate text

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

○All heading elements contain content.

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

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

7 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

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

PASS

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

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

A+

Form Accessibility

All 29 controls labeled

PASS

All 29 controls labeled

29 control(s) properly labeled

29 controls

29 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#searchInputDrawerMobile	search	Search	for/id
#siteSwitch-nav-mobile	select	Website	aria-label
#currencySwitch-nav-mobile	select	Currency	aria-label
#gender__7__28	checkbox	Mens	aria-label
#gender__7__29	checkbox	Womens	aria-label
#gender__7__30	checkbox	Kids	aria-label
#email_01JHV01EBJPZ6WAX3NW87F11ZE	email	Email	for/id
#siteSwitch-nav-desktop	select	Website	aria-label
#currencySwitch-nav-desktop	select	Currency	aria-label
#gender__11__36	checkbox	Mens	aria-label
#gender__11__37	checkbox	Womens	aria-label
#gender__11__38	checkbox	Kids	aria-label
#email_01JMFM3QYFWCAWA5NABHNJ6MQ8	email	EMAIL	for/id
#searchInputDrawerDesktop	search	Search For...	for/id
#gender__9__32	checkbox	Mens	aria-label
#gender__9__33	checkbox	Womens	aria-label
#gender__9__34	checkbox	Kids	aria-label
#email_01JMFJREKGK0X99BM5D6GDM7P9	email	EMAIL	for/id
#Segment%20Prefrence__15__42	checkbox	Mens	aria-label
#Segment%20Prefrence__15__43	checkbox	Womens	aria-label
#Segment%20Prefrence__15__44	checkbox	Kids	aria-label
#phone_number_01K5EYGS2PCCK724Q01PS9YPA5	tel	Phone Number	aria-label
#email_01JY24FKQ3FHZ5SD89Z2Y53BG3	email	EMAIL	for/id
#email_01JXAZGZ0Z2V7B244CZMBJFZH6	email	EMAIL	for/id
#siteSwitch-footer	select	Website	aria-label
#currencySwitch-footer	select	Currency	aria-label
#siteSwitch-footer-desktop	select	Website	aria-label
#currencySwitch-footer-desktop	select	Currency	aria-label
input	input	ftr-tmp-input	aria-label

A

Link & Button Quality

1267 links, 254 buttons — all OK

PASS

1267 links, 254 buttons — all OK

11 link(s) open in new tab without warning

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

Got: https://www.instagram.com/kith/; https://x.com/kith; https://www.facebook.com/Kithnyc; https://vimeo.com/kithnyc; https://www.tiktok.com/@kith; https://www.instagram.com/kith/; https://x.com/kith; https://www.facebook.com/Kithnyc; https://vimeo.com/kithnyc; https://www.tiktok.com/@kith (+1 more)

1256 link(s) with descriptive text

1267 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/kith/	Instagram	new tab	Add '(opens in new tab)' to text
https://x.com/kith	X	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Kithnyc	Facebook	new tab	Add '(opens in new tab)' to text
https://vimeo.com/kithnyc	Vimeo	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@kith	TikTok	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/kith/	Instagram	new tab	Add '(opens in new tab)' to text
https://x.com/kith	X	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Kithnyc	Facebook	new tab	Add '(opens in new tab)' to text
https://vimeo.com/kithnyc	Vimeo	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@kith	TikTok	new tab	Add '(opens in new tab)' to text
/blogs/discover/15-years-together	15 Years Together. WATCH VIDEO	img no alt	Add alt attribute to the image
https://www.essentialaccessibility.com/k…	eSSENTIAL Accessibility (opens…	new tab	Add '(opens in new tab)' to text

1510 links and buttons have descriptive text

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

https://www.instagram.com/kith/; https://x.com/kith; https://www.facebook.com/Kithnyc; https://vimeo.com/kithnyc; https://www.tiktok.com/@kith; https://www.instagram.com/kith/; https://x.com/kith; https://www.facebook.com/Kithnyc; https://vimeo.com/kithnyc; https://www.tiktok.com/@kith (+1 more)

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

29 form control(s) checked, no type mismatches

PASS

29 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

29 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

Iframe Accessibility

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

PASS

1/6 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+

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

2 mobile-depth signal(s) detected

PASS

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

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.