Skip to content
https://skims.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Form Accessibility
Action
4 of 13 controls have issues
FIX
4 of 13 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="$fields">; <input type="text" name="captureLocation">; <input>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input id="autocomplete-0-input">
Info::
9 control(s) properly labeled
13 controls
9 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
emailemailEmail addressaria-label
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#autocomplete-0-inputinput(Search...)placeholder only
$fieldstext(none)none
captureLocationtext(none)none
inputinput(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="$fields">; <input type="text" name="captureLocation">; <input>

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input id="autocomplete-0-input">

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

D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark 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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title SKIMS Logo ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 passed
REVIEW
88

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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > input body > input

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.swiper-wrapper > div.swiper-slide > section.relative > a.select-none div.swiper-wrapper > div.swiper-slide > section.relative > a.select-none
div.swiper-wrapper > div.swiper-slide > section.relative > a.select-none div.swiper-wrapper > div.swiper-slide > section.relative > a.select-none
div.swiper-wrapper > div.swiper-slide > section.relative > a.select-none div.swiper-wrapper > div.swiper-slide > section.relative > a.select-none

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
Shop Now div.pointer-events-none > div.right-0 > div.flex > a.select-none
Sleep div.grid > a.select-none > div.relative > button.flex
Tops & Bodysuits div.grid > a.select-none > div.relative > button.flex
Skirts div.grid > a.select-none > div.relative > button.flex
Sets div.grid > a.select-none > div.relative > button.flex
Shop Now div.pointer-events-none > div.right-0 > div.flex > a.select-none
Bikinis div.grid > a.select-none > div.relative > button.flex
One Piece Swimsuits div.grid > a.select-none > div.relative > button.flex
Swim Cover-Ups div.grid > a.select-none > div.relative > button.flex
Swim Accessories div.grid > a.select-none > div.relative > button.flex
Shop Now div.pointer-events-none > div.right-0 > div.flex > a.select-none
Wishlist div.relative > div.flex > div.flex > button.mt-0.5
Wishlist div.relative > div.flex > div.flex > button.mt-0.5

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
BRL div.mx-auto > div.flex > div.mr-3 > button.flex
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●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
○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.
○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
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A
Heading Hierarchy
41 headings
PASS
41 headings
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 NOW OPEN: THE SPRING SHOP
  • H1 Swim duplicate H1
  • H1 NIKESKIMS SPRING ‘26 NEW ARRIVALS duplicate H1
  • H2 NEW ARRIVALS
  • H3 STRAIGHT LEG PANT
  • H3 TRIANGLE BIKINI TOP
  • H3 STRING THONG
  • H3 TUBE TOP
  • H3 T-SHIRT
  • H3 UNLINED SCOOP BRA
  • H3 BOXER
  • H3 DIPPED TIE BIKINI BOTTOM
  • H3 FOLDOVER PANT
  • H3 T-SHIRT
  • H2 SKIMS is a solutions oriented brand creating the next generation of underwear, clothing and shapewear.
  • H2 Help
  • H2 STAY IN THE KNOW
  • H2 More
  • H2 Are you looking for...
  • H2 My Bag
  • H1 Oops... duplicate H1
  • H2 EXPLORE MORE
  • H3 DIPPED THONG
  • H3 LONG SLEEVE T-SHIRT
  • H3 STRING THONG
  • H3 T-SHIRT
  • H3 LACE THONG
  • H3 PUSH-UP BRA
  • H3 MENS 3" BOXER BRIEF 3-PACK
  • H3 RIFT MESH
  • H3 CLASSIC HOODIE
  • H3 DIPPED THONG
  • H2 Help
  • H2 More
  • H2 Your Privacy Choices
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

A
Alt Text Quality
2 of 63 images have issues
PASS
2 of 63 images have issues
Warning::
2 image(s) with generic alt text
Info::
32 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
63 images 29 good alt text 32 decorative 2 generic
IssueCount
generic2 image(s)
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)
ElementRatioRequiredFGBGResult
h1 NOW OPEN:21.00:13.0:1
#000000
#FFFFFF
Pass
h1 THE SPRING SHOP21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Swim21.00:13.0:1
#000000
#FFFFFF
Pass
h1 NIKESKIMS21.00:13.0:1
#000000
#FFFFFF
Pass
h1 SPRING ‘26 NEW ARR…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Oops...21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NEW ARRIVALS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SKIMS is a solutions…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Help21.00:13.0:1
#000000
#FFFFFF
Pass
h2 STAY IN THE KNOW21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Are you looking for.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 My Bag21.00:13.0:1
#000000
#FFFFFF
Pass
h2 EXPLORE MORE21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Help21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Privacy Choices21.00:13.0:1
#000000
#FFFFFF
Pass
h3 STRAIGHT LEG PANT21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TRIANGLE BIKINI TOP21.00:13.0:1
#000000
#FFFFFF
Pass
h3 STRING THONG21.00:13.0: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.

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

Send Feedback