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

Accessibility

· 12 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
2
PASS
3
INFO
0
Checks
12
3 PASS 2 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ 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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 7 failing, 24 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 parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All Women Men Home Sports Jewelry Industrial Kids Electronics Bags Crafts Beaut… div.wrap-9Gulm > div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa

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
All div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Women div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Men div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Home div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Sports div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Jewelry div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Industrial div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Kids div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Electronics div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Bags div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Crafts div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Beauty div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Toy div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Automotive div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Office div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Baby div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Health div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Garden div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Household div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Pets div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Musical div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Appliances div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Food div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Books div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div

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
Privacy & cookie setting We use cookies and similar technologies to provide our… body.vgui-popup-fixed-lskQJ > div > div > div.box-3EXXP

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
GET div > div.downloadsWrapper-RLshn > div.downloadUI-1EdpI > button.button-3Io9M
Women div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Men div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0 > div
Sign in div.root-h11gn > div.container-3zpvw > div.wrap-6ZxH0 > div.guideButton-2mmoR
See more div.content-20u_c > div.privacyDesWrap-3vDRA > div.seeMore-23W5_ > span.moreText-3t2hO

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.vgui-popup-fixed-lskQJ > div > iframe.iframe-8Vtge body.vgui-popup-fixed-lskQJ > div > iframe.iframe-8Vtge

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 require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
All div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Women div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Men div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Home div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Sports div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Jewelry div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Industrial div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Kids div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Electronics div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Bags div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Crafts div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Beauty div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Toy div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Automotive div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Office div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Baby div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Health div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Garden div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Household div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Pets div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Musical div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Appliances div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Food div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0
Books div.fixAndroid-13mpW > div.wrap-1057f > ul.ul-q7VYa > li.li-17qz0

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
GET div > div.downloadsWrapper-RLshn > div.downloadUI-1EdpI > button.button-3Io9M
○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.
●`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
●Elements with the `role=text` attribute do not have 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>`).
●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
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○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+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
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