Skip to content
https://lazada.co.id

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
37
GRADE
F
FIX
10
REVIEW
2
PASS
1
INFO
0
Checks
13
1 PASS 2 REVIEW 10 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
Alt Text Quality
Action
79 of 130 images have issues
FIX
79 of 130 images have issues
Critical::
79 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
74 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
130 images 50 good alt text 1 decorative 79 missing
IssueCount
missing79 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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-ofy7ve
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
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'>.
favicon.ico Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://lazada.co.id/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://lazada.co.id/manifest.json

Manifest contains invalid JSON.

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.
F
Lighthouse Accessibility Audits
Action
Score 41/100 — 7 failing, 7 passed
FIX
41

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
top up dana bayar cicil div.swiper > div.swiper-wrapper > div.swiper-slide > div.search-diwen-wrap-text
17 : div.swiper-slide > div.timer-wrap > div.fs-time > span.white-span
07 : div.swiper-slide > div.timer-wrap > div.fs-time > span.white-span
09 div.swiper-slide > div.timer-wrap > div.fs-time > span.white-span

These are opportunities to improve the legibility of your content.

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.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
div.link-ripple-container > div.common-img > picture > img div.link-ripple-container > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img
li.link-ripple-container > div.common-img > picture > img li.link-ripple-container > div.common-img > picture > img
div.jfy-card-tit > div.common-img > picture > img div.jfy-card-tit > div.common-img > picture > img

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
div#search > div.search-inner-box > div.search-inner-content > input.search-inner-input div#search > div.search-inner-box > div.search-inner-content > input.search-inner-input

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.gcp-lazada-page > div#web-popup-container > div#web-popup-container-iframe-container > iframe#web-pop-instance-0 body.gcp-lazada-page > div#web-popup-container > div#web-popup-container-iframe-container > iframe#web-pop-instance-0

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hanya Untukmu div.jfy > div.jfy-header > div.jfy-header-wrap > ul.jfy-header

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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-hidden="true"]` is not present on the document `<body>`
`[aria-hidden="true"]` elements do not contain focusable descendents
Document has a `<title>` element
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
The page contains a heading, skip link, or landmark region
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`<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
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`<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
Links are distinguishable without relying on color.
Links have a discernible name
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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.
Elements with visible text labels have matching accessible names.
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.
B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input id="topActionDownloadInput">; <input type="search" name="q" id="q">
Info::
2 control(s) properly labeled
4 controls
2 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#topActionTrackEmailinputEmail:for/id
#topActionTrackOrderNumberinputNomor pesanan:for/id
#topActionDownloadInputinput(eg. 0123456789)placeholder only
#qsearch(Cari di Lazada)placeholder only

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

<input id="topActionDownloadInput">; <input type="search" name="q" id="q">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Lazada Indonesia | Toko Online, Diskon T…
2.97:1
#000000
on
#753EA2
needs 4.5:1 (normal text)
16px · top of page (header area)
a INTERNAL FEEDBACK
2.88:1
#000000
on
#6F409A
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Nyaman Belanja Onlin…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Layanan Pelanggan21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Jelajahi Lazada21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Metode Pembayaran21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Jasa Pengiriman21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Verified by21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Terpercaya Se-Asia T…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Promo Belanja Online…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 LazMall 100% Origina…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Review Asli, Pembaya…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pilihan Produk Terle…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TOP CATEGORIES & BRA…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lazada Southeast Asi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Follow Us21.00:13.0:1
#000000
#FFFFFF
Pass
title Lazada Indonesia | T…2.97:14.5:1
#000000
#753EA2
Fail
a INTERNAL FEEDBACK2.88:14.5:1
#000000
#6F409A
Fail
a Masukan7.18:14.5:1
#000000
#AE89C4
Pass
span LEBIH MURAH DI APP20.47:14.5:1
#000000
#FCFCFC
Pass
div Download Aplikasinya…18.45:14.5:1
#000000
#EFF0F5
Pass
p Belanja di App banya…21.00:14.5: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.

A
Heading Hierarchy
34 headings, 1 skip(s)
PASS
34 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Layanan Pelanggan
  • H3 Jelajahi Lazada
  • H3 Metode Pembayaran
  • H3 Jasa Pengiriman
  • H3 Verified by
  • H1 Nyaman Belanja Online
  • H3 Terpercaya Se-Asia Tenggara skipped
  • H3 Promo Belanja Online Terbaik
  • H3 LazMall 100% Original dan Lengkap
  • H3 Review Asli, Pembayaran Aman Terpercaya!
  • H3 Pilihan Produk Terlengkap Banyak Kategori di Lazada 12.12
  • H3 TOP CATEGORIES & BRANDS
  • H4 AUTOMOTIVE & GADGETS
  • H4 BABY & TODDLER
  • H4 CAMERAS
  • H4 COMPUTERS & LAPTOPS
  • H4 FASHION
  • H4 GROCERIES
  • H4 HEALTH & BEAUTY
  • H4 HOME & LIVING
  • H4 Belanja di seluruh dunia dengan AliExpress
  • H4 Belanja di seluruh dunia dengan Daraz
  • H4 MEDIA, MUSIC & BOOKS
  • H4 MOBILES & TABLETS
  • H4 SPORTS & OUTDOORS
  • H4 TOYS & GAMES
  • H4 TRAVEL & LUGGAGE
  • H4 TV, AUDIO / VIDEO, GAMING, GADGETS
  • H4 VOUCHERS AND SERVICES
  • H4 WATCHES SUNGLASSES JEWELLERY
  • H4 HOME APPLIANCES
  • H4 PROMO SPESIAL
  • H3 Lazada Southeast Asia
  • H3 Follow Us

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

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

Send Feedback