Skip to content
https://taobao.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
F
Alt Text Quality
Action
84 of 179 images have issues
FIX
84 of 179 images have issues
Critical::
83 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
48 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with generic alt text
Info::
13 decorative image(s) correctly marked
Info::
82 image(s) with good alt text
179 images 82 good alt text 13 decorative 1 generic 83 missing
IssueCount
missing83 image(s)
generic1 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-5nf03g
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
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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://taobao.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://taobao.com/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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 60/100 — 4 failing, 9 passed
FIX
60

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

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.sc-ifAKCX > div.topbar-wrapper > div.topbar-hd > img.logo div.sc-ifAKCX > div.topbar-wrapper > div.topbar-hd > img.logo
div.topbar-wrapper > div.topbar-ld > div > img.signIn div.topbar-wrapper > div.topbar-ld > div > img.signIn
body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img
body > div#tcodeSideBar > img body > div#tcodeSideBar > img
body > div#tcodeSideBar > img body > div#tcodeSideBar > img
body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img

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 > div.J_MIDDLEWARE_FRAME_WIDGET > iframe body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe
body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe
body > div.baxia-dialog > div.baxia-dialog-content > iframe#baxia-dialog-content body > div.baxia-dialog > div.baxia-dialog-content > iframe#baxia-dialog-content

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.

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>`
●Buttons have an accessible name
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●The page contains a heading, skip link, or landmark region
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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-hidden="true"]` elements do not contain focusable descendents
○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
○`<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
○Form elements have associated labels
○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.
○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
○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
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN ASIDE CONTENTINFO (missing!)

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
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title 淘宝21.00:14.5:1
#000000
#FFFFFF
Pass
span 中国大陆21.00:14.5:1
#000000
#FFFFFF
Pass
span 21.00:14.5:1
#000000
#FFFFFF
Pass
li 中国大陆21.00:14.5:1
#000000
#FFFFFF
Pass
li 中国香港21.00:14.5:1
#000000
#FFFFFF
Pass
li 中国台湾19.26:14.5:1
#000000
#F5F5F5
Pass
li 中国澳门21.00:14.5:1
#000000
#FFFFFF
Pass
li 韩国21.00:14.5:1
#000000
#FFFFFF
Pass
li 马来西亚19.81:14.5:1
#000000
#F9F8F8
Pass
li 澳大利亚6.08:14.5:1
#000000
#FF4400
Pass
li 全球12.24:14.5:1
#000000
#FFB499
Pass
li 新加坡21.00:14.5:1
#000000
#FFFFFF
Pass
li 新西兰21.00:14.5:1
#000000
#FFFFFF
Pass
li 加拿大21.00:14.5:1
#000000
#FFFFFF
Pass
li 日本21.00:14.5:1
#000000
#FFFFFF
Pass
li 越南21.00:14.5:1
#000000
#FFFFFF
Pass
li 泰国12.65:14.5:1
#000000
#FFB999
Pass
li 菲律宾12.02:14.5:1
#000000
#FAB494
Pass
li 柬埔寨21.00:14.5:1
#000000
#FFFFFF
Pass
a 亲，请登录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
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 淘宝网
  • H2 淘宝网
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file" id="image-search-custom-file-input">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#qinput请输入搜索文字aria-label
#image-search-custom-file-inputfile(none)none

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

<input type="file" id="image-search-custom-file-input">

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

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

Send Feedback