Skip to content
https://alibaba.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
F
Alt Text Quality
Action
65 of 209 images have issues
FIX
65 of 209 images have issues
Critical::
56 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
55 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
9 image(s) with generic alt text
Info::
8 decorative image(s) correctly marked
Info::
136 image(s) with good alt text
209 images 136 good alt text 8 decorative 9 generic 56 missing
IssueCount
missing56 image(s)
generic9 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-n8reni
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.

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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 Present
✗ Multiple Sizes Missing
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::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
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.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Search tabs" SEARCH MAIN ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

B
Heading Hierarchy
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Enjoy protection from payment to delivery.
  • H3 Safe & easy payments
  • H3 Money-back policy
  • H3 Shipping & logistics services
  • H3 After-sales protections
  • H3 Your Al business team 7/24
  • H3 Alibaba.com Tax Exemption Program
  • H3 Discover manufacturers
  • H3 Welcome to Alibaba.com
  • H3 Get support
  • H3 Payments and protections
  • H3 Source on Alibaba.com
  • H3 Sell on Alibaba.com
  • H3 Get to know us
  • H3 Stay Connected

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Alibaba.com - B2B marketplace
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Alibaba.com - B2B marketplace ✓192×192 icon ✗512×512 icon ✓Start URL https://www.alibaba.com?src=microsoftpwa ✓Display Mode standalone ✓
Name Alibaba.com - B2B marketplace Display Mode standalone Theme Color #fff Background Color #fff Icons 1 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h3 Enjoy protection from payment to deliver…
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Safe & easy payments
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Money-back policy
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Shipping & logistics services
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 After-sales protections
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Alibaba.com Tax Exemption Program
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Discover manufacturers
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Welcome to Alibaba.com
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get support
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Payments and protections
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Source on Alibaba.com
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sell on Alibaba.com
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get to know us
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Stay Connected
2.37:1
#000000
on
#4A4A4A
needs 3.0:1 (large text)
19px · bottom of viewport
title Alibaba.com: Manufacturers, Suppliers, E…
2.21:1
#000000
on
#304B43
needs 4.5:1 (normal text)
16px · top of page (header area)
div Deliver to:
2.35:1
#000000
on
#404C48
needs 4.5:1 (normal text)
16px · top of page (header area)
div English-USD
2.43:1
#000000
on
#4A4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Sign in
2.39:1
#000000
on
#494B4B
needs 4.5:1 (normal text)
16px · top of page (header area)
div Create account
2.39:1
#000000
on
#494B4B
needs 4.5:1 (normal text)
16px · above the fold
div All categories
2.39:1
#000000
on
#494B4B
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Enjoy protection fro…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Safe & easy payments2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Money-back policy2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Shipping & logistics…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 After-sales protecti…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Alibaba.com Tax Exem…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Discover manufacture…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Welcome to Alibaba.c…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Get support2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Payments and protect…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Source on Alibaba.co…2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Sell on Alibaba.com2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Get to know us2.37:13.0:1
#000000
#4A4A4A
Fail
h3 Stay Connected2.37:13.0:1
#000000
#4A4A4A
Fail
title Alibaba.com: Manufac…2.21:14.5:1
#000000
#304B43
Fail
div Deliver to:2.35:14.5:1
#000000
#404C48
Fail
div English-USD2.43:14.5:1
#000000
#4A4C4C
Fail
span Sign in2.39:14.5:1
#000000
#494B4B
Fail
div Create account2.39:14.5:1
#000000
#494B4B
Fail
div All categories2.39:14.5:1
#000000
#494B4B
Fail

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 88/100 — 3 failing, 24 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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.index_module_searchWrapper__4f1e4d62 > div.index_module_searchBar__4f1e4d62 > form#headerSearchForm > button.index_module_searchButton__79a8d9e7 div.index_module_searchWrapper__4f1e4d62 > div.index_module_searchBar__4f1e4d62 > form#headerSearchForm > button.index_module_searchButton__79a8d9e7

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
label.index_module_label__79a8d9e7 > div.index_module_inputActions__79a8d9e7 > div.index_module_imageSearchContainer__ced052ca > a label.index_module_label__79a8d9e7 > div.index_module_inputActions__79a8d9e7 > div.index_module_imageSearchContainer__ced052ca > a

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.

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
iphones 15 pro max label.index_module_label__79a8d9e7 > div.index_module_inputWrapper__79a8d9e7 > div.index_module_shadeQuery__f7095e7f > span.index_module_queryText__f7095e7f
40 pieces (MOQ) div.MlcPi > a.iYcwx > div.product-image > div.JcwOU
1 piece (MOQ) div.MlcPi > a.iYcwx > div.product-image > div.JcwOU
1 pack (MOQ) div.MlcPi > a.iYcwx > div.product-image > div.JcwOU
1 pack (MOQ) div.MlcPi > a.iYcwx > div.product-image > div.JcwOU
1 pack (MOQ) div.MlcPi > a.iYcwx > div.product-image > div.JcwOU
1 pack (MOQ) div.MlcPi > a.iYcwx > div.product-image > div.JcwOU
Home div.bottomNavbar__0VHw5G > div.navbar-container__0VHw5G > div.navbar-item__0VHw5G > span.navbar-item-text__0VHw5G
Open div > div#call-app-dialog > div.call-app-dialog-main > div#call-app-dialog-open

These are opportunities to improve the legibility of your content.

○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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●The page contains a heading, skip link, or landmark region
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○`<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
○Heading elements appear in a sequentially-descending order
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
textareatextareaSearch Alibabaaria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback