Skip to content
https://uniqlo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
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
Theme color only
FIX
Theme color only
Info::
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.
Got: #ffffff
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 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
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
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
C
Landmark Structure
Action
6 landmarks
REVIEW
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
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
BANNER header NAV "Category" MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h1 UNIQLO
2.57:1
#000000
on
#4C5051
needs 3.0:1 (large text)
32px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 UNIQLO2.57:13.0:1
#000000
#4C5051
Fail
h2 Search by category6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Information6.25:13.0:1
#000000
#8C8C8C
Pass
h2 LifeWear6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Sustainability6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Inspiration6.25:13.0:1
#000000
#8C8C8C
Pass
h2 News6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Special Collaboratio…6.25:13.0:1
#000000
#8C8C8C
Pass
h2 UT Collections6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Stores6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Information6.25:13.0:1
#000000
#8C8C8C
Pass
h2 LifeWear6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Sustainability6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Inspiration6.25:13.0:1
#000000
#8C8C8C
Pass
h2 News6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Special Collaboratio…6.25:13.0:1
#000000
#8C8C8C
Pass
h2 UT Collections6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Stores6.25:13.0:1
#000000
#8C8C8C
Pass
h2 Information6.25:13.0:1
#000000
#8C8C8C
Pass
h2 LifeWear6.25:13.0:1
#000000
#8C8C8C
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 5 failing, 26 passed
REVIEW
87

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tiered Maxi Skirt a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
Discover our Tiered Maxi Skirt and the rest of the skirt collection, including … a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
39,90 € div.media-banner > div.media-banner__text-wrapper > div.content-alignment > p.typography
T-Shirts for Everyone a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
T-shirt season is just around the corner. Discover a collection of easy-to-styl… a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
Shorts & Culottes Collection a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
Shop a line-up of elegant culottes in lightweight fabrics, perfect for warmer w… a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
Denim Collection a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
From must-have barrel cuts to timeless straight leg designs. a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
Dresses Collection a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
From fashion-forward drawstring styles to classic button-through designs, disco… a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
UNIQLO and Cecilie Bahnsen a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography
A new collaboration for women and girls, with Copenhagen-based designer Cecilie… a.fr-ec-link > div.media-banner > div.media-banner__text-wrapper > p.typography

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
Hello! div.fr-ec-header-overlay > div#country_selecor_title > div.fr-ec-header-overlay__title > h5.fr-ec-display

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
div.fr-ec-layout > div.content-alignment > div.image > img.image__img div.fr-ec-layout > div.content-alignment > div.image > img.image__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
Download the UNIQLO app to shop with Pick Up Today and collect your order in st… div.home-template > div > div > a.fr-ec-link

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.

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
Cookie policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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
●`[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.
●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
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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 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
○Form elements have associated labels
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○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
34 headings, 1 skip(s)
PASS
34 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 UNIQLO
  • H2 Search by category
  • H2 Information
  • H2 LifeWear
  • H2 Sustainability
  • H2 Inspiration
  • H2 News
  • H2 Special Collaborations
  • H2 UT Collections
  • H2 Stores
  • H2 Information
  • H2 LifeWear
  • H2 Sustainability
  • H2 Inspiration
  • H2 News
  • H2 Special Collaborations
  • H2 UT Collections
  • H2 Stores
  • H2 Information
  • H2 LifeWear
  • H2 Sustainability
  • H2 Inspiration
  • H2 News
  • H2 UT Collections
  • H3 Special Collaborations
  • H2 Stores
  • H2 Information
  • H2 LifeWear
  • H2 Sustainability
  • H2 Inspiration
  • H2 News
  • H2 UT Collections
  • H2 Stores
  • H5 Hello! skipped

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

A+
Alt Text Quality
All 295 images OK
PASS
All 295 images OK
Info::
295 image(s) with good alt text
295 images 295 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback