Skip to content
https://www.nike.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <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.
C
Heading Hierarchy
Action
114 headings, 2 skip(s)
REVIEW
114 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Achamos que você está em Brasil. Deseja atualizar seu local?
  • H3 Men skipped
  • H3 Women
  • H3 Kids
  • H3 Jordan
  • H3 NikeSKIMS
  • H3 Sport
  • H3 Sale
  • H4 Become a Nike Member for the best products, inspiration and stories in sport. Learn more
  • H3 TEE IT HIGH. LET IT FLY.
  • H3 TRAIN RIGHT
  • H3 BUILT FOR THE MOMENT
  • H3 TEE IT HIGH. LET IT FLY.
  • H3 TRAIN RIGHT
  • H3 TEE IT HIGH. LET IT FLY.
  • H3 TRAIN RIGHT
  • H3 BUILT FOR THE MOMENT
  • H3 TEE IT HIGH. LET IT FLY.
  • H3 TRAIN RIGHT
  • H3 Full-Length, Curved Air Zoom
  • H3 Soccer cleats created by athletes. Built to be seen.
  • H2 SPOTLIGHT
  • H2 SPOTLIGHT
  • H1 (empty)
  • H4 Featured skipped
  • H4 Shoes
  • H4 Clothing
  • H4 Kids
  • H4 Egypt
  • H4 Morocco
  • H4 Maroc
  • H4 South Africa
  • H4 Argentina
  • H4 Brasil
  • H4 Canada
  • H4 Canada
  • H4 Chile
  • H4 Colombia
  • H4 México
  • H4 Peru
  • H4 Puerto Rico
  • H4 United States
  • H4 Estados Unidos
  • H4 Uruguay
  • H4 Latin America
  • H4 Australia
  • H4 中国大陆
  • H4 Hong Kong
  • H4 香港
  • H4 India
  • H4 Indonesia
  • H4 Japan
  • H4 日本
  • H4 대한민국
  • H4 Malaysia
  • H4 New Zealand
  • H4 Philippines
  • H4 Singapore
  • H4 台灣
  • H4 ไทย
  • H4 Vietnam
  • H4 Österreich
  • H4 Austria
  • H4 Belgien
  • H4 Belgium
  • H4 Belgique
  • H4 België
  • H4 Bulgaria
  • H4 Croatia
  • H4 Česká republika
  • H4 Czech Republic
  • H4 Danmark
  • H4 Denmark
  • H4 Finland
  • H4 France
  • H4 Deutschland
  • H4 Ελλάδα
  • H4 Hungary
  • H4 Magyarország
  • H4 Ireland
  • H4 Israel
  • H4 Italia
  • H4 Luxemburg
  • H4 Luxembourg
  • H4 Luxembourg
  • H4 Netherlands
  • H4 Nederland
  • H4 Norway
  • H4 Norge
  • H4 Polska
  • H4 Portugal
  • H4 Portugal
  • H4 Romania
  • H4 Россия
  • H4 Slovakia
  • H4 Slovenia
  • H4 Espanya
  • H4 España
  • H4 Sweden
  • H4 Sverige
  • H4 Schweiz
  • H4 Switzerland
  • H4 Suisse
  • H4 Svizzera
  • H4 Türkiye
  • H4 United Kingdom
  • H4 Saudi Arabia
  • H4 المملكة العربية السعودية
  • H4 United Arab Emirates
  • H4 الإمارات العربية المتحدة
  • H4 Qatar
  • H4 دولة قطر
  • H4 Kuwait
  • H4 الكويت

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

C
Form Accessibility
Action
18 of 23 controls have issues
REVIEW
18 of 23 controls have issues
Critical::
18 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+8 more)
Info::
5 control(s) properly labeled
23 controls
5 labeled
0 placeholder only
18 unlabeled
ControlTypeLabelMethod
#gn-search-inputsearchSearch Productsaria-label
#toggle-aeb66aeb-b1a2-4c07-9be0-b207400fa7b7checkboxFeaturedfor/id
#toggle-82b3c01a-7dc2-4019-b741-8b27d4675ae4checkboxShoesfor/id
#toggle-d9108de0-960c-4840-90f6-2d8e7453d79echeckboxClothingfor/id
#toggle-cd9e9e18-e773-47ae-bcf3-db90dc5facbccheckboxKidsfor/id
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

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

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+8 more)

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found. Nike.com ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 79/100 — 7 failing, 26 passed
REVIEW
79

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Guides li > div.nav-css-s8yvqs > details.nav-css-1qehhq > summary.drop-down-accessibility-button

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Nike AI body.nav-scrollable > div#footer-wrapper > div#gen-nav-footer > div.nav-css-1sf9wd7

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
Only in the Nike App body.nav-scrollable > div#singular-banner > div.singular-banner-content > span.singular-banner-title
Get exclusive access, member rewards, and more. body.nav-scrollable > div#singular-banner > div.singular-banner-content > span.singular-banner-subtitle
OPEN body.nav-scrollable > div#singular-banner > div.singular-banner-download-button

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TEE IT HIGH. LET IT FLY. figure.image-card > figcaption._13xDDA0A > div._3T7SP3hk > h3#a11y_react-aria-:R8u5pl6:-title
Featured div#d5d48201-75f8-4fa5-942d-6c05ed94265b > div#123e7f31-636e-4819-a8a4-60d9346d30de > div.merchMenuWrapper > h4.merch-menu-heading

These are opportunities to improve keyboard navigation in your application.

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
body.nav-scrollable > div#singular-banner > img.singular-banner-background-image body.nav-scrollable > div#singular-banner > img.singular-banner-background-image
body.nav-scrollable > div#singular-banner > img.singular-banner-logo body.nav-scrollable > div#singular-banner > img.singular-banner-logo

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
Current slide, Go to slide 3 of 3 div#1a73c582-b70e-4103-8c9d-775a302e49fd > div#carousel-a9424745-c262-43cb-8c2a-97dddf494c77 > div.S2QRw7W4 > button.TYczRBi0

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
See All div > div._3PJUZAN0 > div.Yjk73vve > button.nds-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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●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.
○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
○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
○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
○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>`.
○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
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Global Navigation" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 53 images OK
PASS
All 53 images OK
Info::
33 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
53 images 20 good alt text 33 decorative
All images have appropriate alt text.
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 Achamos que você es…20.29:13.0:1
#000000
#FBFBFB
Pass
h2 SPOTLIGHT5.25:13.0:1
#000000
#FD0E11
Pass
h2 SPOTLIGHT5.25:13.0:1
#000000
#FD0E11
Pass
h3 Men5.25:13.0:1
#000000
#FD0E11
Pass
h3 Women5.25:13.0:1
#000000
#FD0E11
Pass
h3 Kids5.25:13.0:1
#000000
#FD0E11
Pass
h3 Jordan5.25:13.0:1
#000000
#FD0E11
Pass
h3 NikeSKIMS5.25:13.0:1
#000000
#FD0E11
Pass
h3 Sport5.25:13.0:1
#000000
#FD0E11
Pass
h3 Sale5.25:13.0:1
#000000
#FD0E11
Pass
h3 TEE IT HIGH. LET IT …5.25:13.0:1
#000000
#FD0E11
Pass
h3 TRAIN RIGHT5.25:13.0:1
#000000
#FD0E11
Pass
h3 BUILT FOR THE MOMENT5.25:13.0:1
#000000
#FD0E11
Pass
h3 TEE IT HIGH. LET IT …5.25:13.0:1
#000000
#FD0E11
Pass
h3 TRAIN RIGHT5.25:13.0:1
#000000
#FD0E11
Pass
h3 TEE IT HIGH. LET IT …5.25:13.0:1
#000000
#FD0E11
Pass
h3 TRAIN RIGHT5.25:13.0:1
#000000
#FD0E11
Pass
h3 BUILT FOR THE MOMENT5.25:13.0:1
#000000
#FD0E11
Pass
h3 TEE IT HIGH. LET IT …5.25:13.0:1
#000000
#FD0E11
Pass
h3 TRAIN RIGHT5.25:13.0:1
#000000
#FD0E11
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